I am evaluating the use of a Netduino Plus 2 for testing of another device (DUT) which has a USB port. I would communicate to the Netduino on the Ethernet port and then control the DUT via USB commands. There are a lot of details to work out, but, the obvious concern I have with this approach is that the USB port is needed for debugging. I certainly cannot debug while simultaneously using the USB for controlling the DUT.
Here are some ideas I have to work around this:
- Develop what I could using Visual Studio and use a JTAG debugger for the full end-to-end solution (I saw another post that suggested a different board that could support JTAG)
- Modify the core code on the Netduino and use a couple of the digital IO as a serial port for debugging (ala WinDbg)
- Use a different device (ideally in the Netduino family) better suited for this task
I am also wondering if, assuming that I can work out the debug issues, the .NET CF has good support for using the USB as something other than a debug port.
I have done a modest amount of kernel/OAL/boot loader development and would prefer something like #2 if that were possible. It lets me stay in the Visual Studio environment rather than going to a JTAG debug environment.
Any thoughts on this or other ideas are welcome.