This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3352: UniFlash on Windows 10

Part Number: AM3352
Other Parts Discussed in Thread: UNIFLASH,

Hi,

We are developing a board with the AM3352 CPU. For programming we are hoping to use the USB0 boot-mode and then UniFlash to program over "Ethernet over USB"/RNDIS. To test this out before sending the final PCBA for production we are using a Beaglebone Black.

Our production programming and test environment use Windows 10 as OS. 

When we connect the BBB over USB to our computer (pressing button S2 on the BBB board and have no SD-card attached) W10 enumerates the CPU as a serial device and we get a COM-port. I have seen others with this issue while searching the Internet (but no solution). On an old Windows 7 somputer I found stored away it works. W7 enumerates the CPU as "other device" and I can install the correct driver. And later on UniFlash will recognize the CPU and we are able to program it.

Is it possible to get this working on Windows 10? Have anyone made it work? Should we rethink our programming strategy and program the eMMC onboard some other way? In worst case we could use UART0, but that would take for ever to program the board.

Thanks in advance!

Regards,

Jonas

  • Jonas,

    I"m sorry, but Uniflash has not been validated on Windows 10. I've heard that MS made some changes to the RNDIS drivers that may impact how Uniflash might work, but I'm not sure if these can be overcome easily or not.

    Windows 7 and Linux (Ubuntu) were used to validate Uniflash and should both function properly.

  • Hi Ron,

    I thought that since Windows 10 has been around for a few years no TI would have looked in to this issue and offered a solution. But I guess we are stuck with Windows 7 on our test machine for now.

    Regarding Linux support, is there a specific version of Ubuntu that must be used here as well? Or do you validate agains all version of Ubuntu?
  • Jonas, sorry I missed your last query here. We typically test/support the LTS versions, so 14.04 and 16.04 currently.