Differences

This shows you the differences between two versions of the page.

Link to this comparison view

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:
 {{ :devices:muxbox_development.png?400 |}} {{ :devices:muxbox_development.png?400 |}}
  
-Sometimes device we develop does not support booting from net and only can be booted from SD card. To remove neccessity of juggling SD card back and forth from PC to device we can use MuxBox in configuration shown above. +Sometimes device we develop does not support booting from net and only can be booted from SD card. To remove necessity of juggling SD card back and forth from PC to device we can use MuxBox in configuration shown above. 
-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 following commands without the need to plug/unplug cables or reinserting SD card:
     $ 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:
  
 {{ :devices:muxbox_usecase.png?400 |}} {{ :devices:muxbox_usecase.png?400 |}}
-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 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.
  
 {{ :devices:muxbox_usecase_flow.png?500 |}} {{ :devices:muxbox_usecase_flow.png?500 |}}
 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, kernel module, etc.) is compiling without problems, but also if there are no runtime errors.  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, kernel module, etc.) is compiling without problems, but also if there are no runtime errors. 
  
  • devices/muxbox.1551445684.txt.gz
  • Last modified: 2019/03/01 13:08
  • by m.sloniewski