|
|
(33 intermediate revisions by 4 users not shown) |
Line 1: |
Line 1: |
− | = How to boot your IGEPv2 board<br> =
| + | #REDIRECT:[[What can I do with IGEPv2]] |
− | | |
− | First of all, you may want to boot your board. IGEP0020 can boot from the next devices (listed by priority):
| |
− | | |
− | *from a MMC/microSD card ([[How to boot from MicroSD Card|here]] is a complete tutorial about how to set it up)<br>
| |
− | *from OneNAND memory.
| |
− | | |
− | <br>
| |
− | | |
− | The IGEPv2 board boot process is divided in '''3 booting phases''':<br>
| |
− | | |
− | #[[The bootloader X-loader|xloader]] boot process (It's not possible to interact with the board).
| |
− | #[[The bootloader U-Boot|uboot boot]] process (It's possible to interact with the board using the console).
| |
− | #[[The Linux kernel|Linux Kernel]] starting process (It's possible to interact with the board using the console when the kernel has already started).<br>
| |
− | | |
− | = How to set up and log in<br> =
| |
− | | |
− | IGEPv2 board uses the serial debug for output all debug information and the users can interact with the board.
| |
− | | |
− | The IGEPv2 Serial debug console can be accessed on [http://www.igep.es/index.php?option=com_content&view=article&id=99&Itemid=112&dir=%2Fvar%2Fwww%2Fvhosts%2Figep.es%2Fhttpdocs%2Fdownloads%2F01-ISEE_Products%2FIGEPv2%2FHW_User_Manuals&download_file=%2Fvar%2Fwww%2Fvhosts%2Figep.es%2Fhttpdocs%2Fdownloads%2F01-ISEE_Products%2FIGEPv2%2FHW_User_Manuals%2FMAN-PR-IGEP.0020-001.21.HW_Manual_RC_v1.21.pdf J960 connector] and you should use a [http://igep-platform.com/shop/index.php?main_page=product_info&cPath=1&products_id=8&zenid=701aa01925001b84ed070559d8ac0851 DBM9 to IDC-10 adapter] for connecting it to the host PC.<br> Read [[How to setup the IDC10 cable|how to setup IDC-10 adapter]].
| |
− | | |
− | Now you are ready to login. You can do it via:
| |
− | | |
− | *'''Serial Console''': [[Using serial debug port to communicate|here]] is a short explanation about how to correctly configure your Serial Console<br>
| |
− | *'''SSH'''
| |
− | | |
− | The default login user is: '''root'''
| |
− | | |
− | There is '''no password''' for this user.
| |
− | | |
− | = How to handle the LED's<br> =
| |
− | | |
− | This is probably the most simple feature in the board, but sometimes LED's may be the only way of checking the status of some of your applications.
| |
− | | |
− | IGEP0020 has 4 LED's which you can control, for example, using 'echo'. Here is an example of turning LED's On:
| |
− | <pre>echo 1 > /sys/devices/platform/leds-gpio/leds/d240\:green/brightness
| |
− | echo 1 > /sys/devices/platform/leds-gpio/leds/d240\:red/brightness
| |
− | echo 1 > /sys/devices/platform/leds-gpio/leds/d440\:green/brightness
| |
− | echo 1 > /sys/devices/platform/leds-gpio/leds/d440\:red/brightness
| |
− | </pre>
| |
− | You can turn them down using the same command and write '0' instead of '1'.
| |
− | | |
− | If you want to trigger the leds you can enable this mode and select the trigger source (none by default) to: mmc0, mmc1, timer, heartbeat and default-on.<br>
| |
− | | |
− | To enable any of this modes you just have to change a parameter in the directory of the led you want to control. You can see all the possibilities using 'cat':<br>
| |
− | <pre>$ cat /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
| |
− | | |
− | [none] mmc0 mmc1 timer heartbeat default-on
| |
− | </pre>
| |
− | In the example above, we have checked the status of the trigger in led D240:green. Mode 'none' is selected.
| |
− | | |
− | To change it, for example, to the timer mode you can use 'echo':<br>
| |
− | <pre>echo timer > /sys/devices/platform/leds-gpio/leds/d240\:green/trigger
| |
− | </pre>
| |
− | In this case, we have set the trigger to the 'timer' mode. Now you can set the time for what the led is ON and the time it is OFF using:<br>
| |
− | <pre>echo 250 > /sys/devices/platform/leds-gpio/leds/d240\:green/delay_on
| |
− | echo 750 > /sys/devices/platform/leds-gpio/leds/d240\:green/delay_off
| |
− | </pre>
| |
− | Now the selected led is configured with a timer consisting of 250 miliseconds ON and 750 miliseconds OFF.<br>
| |
− | | |
− | <br>
| |
− | | |
− | <br>
| |