Differences
This shows you the differences between two versions of the page.
devices:muxbox [2019/03/01 13:08] m.sloniewski created |
devices:muxbox [2019/03/01 13:57] (current) m.sloniewski fixing typos |
||
---|---|---|---|
Line 89: | Line 89: | ||
{{ : | {{ : | ||
- | Sometimes device we develop does not support booting from net and only can be booted from SD card. To remove | + | Sometimes device we develop does not support booting from net and only can be booted from SD card. To remove |
- | With this setup when we compile new version of firmware all we have to do to test is run following commands without the need to plug/unplug cables or reinserting SD card: | + | With this setup when we compile new version of firmware all we have to do to test it is running |
$ gmux sd host | $ gmux sd host | ||
$ dd if=new_firmware.img of=/dev/sdX bs=1M | $ dd if=new_firmware.img of=/dev/sdX bs=1M | ||
Line 100: | Line 100: | ||
{{ : | {{ : | ||
- | Diagram above shows physical setup of a testing rig for liteSOM. MuxBox is connected to PC via USB cable, SD card is present in MuxBox and device under test is connected to MuxBox with cable provided for MMC interface, UART cable and reset cable hooked up to reset pin of the device. | + | Diagram above shows physical setup of a testing rig for a liteSOM. MuxBox is connected to PC via USB cable, SD card is present in MuxBox and device under test is connected to MuxBox with cable provided for MMC interface, UART cable and reset cable hooked up to reset pin of the device. |
{{ : | {{ : | ||
Flow chart above shows typical CI workflow incorporating previously shown MuxBox setup for running automatic tests on physical device. Those tests can check not only if developed code (application, | Flow chart above shows typical CI workflow incorporating previously shown MuxBox setup for running automatic tests on physical device. Those tests can check not only if developed code (application, | ||