• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 99 subscribers
  • Views 2437 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM3352: UniFlash on Windows 10

CCS/AM3358: USB boot - RNDIS/Ethernet over USB

Joni 14324
Prodigy 220 points
Part Number: AM3358
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hi

We are trying to burn the emmc for production , using USB boot option - RNDIS/Ethernet over USB -

and (CCS UniFlash  Version: 3.4.1.00012 ) runnig over Windows 10.

The problem is the the ROM boot is able to tftp get the SPL/MLO loader butthe SPL fails to connect to uniflash

and tftp get the uboot ,You advice is needed!

See log below, Thanks.

==Log==

U-Boot SPL 2018.01-00444-g96cdbef-dirty (Feb 14 2019 - 23:19:25)
Trying to boot from USB eth
** Bad device mmc 0 **
Using default environment

<ethaddr> not set. Validating first E-fuse MAC
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Error: usb_ether address not set.

using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 38:d2:69:5e:0e:63
HOST MAC de:ad:be:ef:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
Problem booting with BOOTP
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

.

  • 0
    TI__Mastermind 30506 points
    Joni,

    Have you set up the second USB interface as required? SPL will set up a different interface from ROM and it needs to be configured as the same way.

    Thanks for the post.
  • 0 in reply to RonB
    Prodigy 220 points

    Hi Ron,

    The second USB is detected by WIN 10 as USB serial device , I couldn't able to update the driver to RNDIS.

    I saw that each device has different PID:

    ROM: USB\VID_0451&PID_6141&REV_0000

    SPL: USB\VID_0451&PID_D022&REV_0315

    So my workaround was to change in the config file of uboot the PID from D022 to 6141 and to build uboot.

    Thanks

  • 0 in reply to Joni 14324
    TI__Mastermind 30506 points
    Joni,

    So, you are unblocked and able to use Uniflash on Win10? I just want to confirm.
  • 0 in reply to RonB
    Prodigy 220 points
    Yes, After changing the USB PID in uboot config file and building uboot with new config ,
    Win10 detect the Am335x as USB RNDIS device.
  • 0 in reply to Joni 14324
    Intellectual 265 points

    Hi Joni,

    I'm trying to do the same thing as you, setting up the eMMC on our board with a AM352 using Windows 10 and Uniflash 3.4.

    However, I'm not even able to get the ASM3352 ROM boot to setup as a RNDIS device on Windows 10. It only comes up as a USB Serial Port.

    How were you able to get Windows 10 to recognize the ROM as RNDIS? Any special drivers you used?

    Thanks in advance!

    Regards,
    Jonas

  • 0 in reply to Jonas Lorander
    Prodigy 220 points

    Hi

    1)The boot sequence is : (1) ROM (2) uboot spl (3) uboot. Just to make sure, your issue is in step (1) ,right?

    2) If you have EVM board, check how windows detect it.


    3)Please check the HW ids : In windows open device manger , right click on USB serial, select properties, select Details tab, and in the drop down menu select hardware Ids.

    windows 10 should setup usb device with USB\VID_0451&PID_6141 Or USB\VID_0525&PID_A4A2 as RNDIS device.

    Regards,

  • 0 in reply to Joni 14324
    Intellectual 265 points

    Hi Joni,

    1. Yes, my issue are in step (1), ROM boot.

    2. I have no EVM, I have BBB, i shall try that today.

    3. the USB hardware ID is USB\VID_0451&PID_6141&REV_0000 and USB\VID_0451&PID_6141. But still, Windows 10 is setting it up as "Serial USB Device (COMx)". I have tried this on two different Windows 10 machine, one of which was a completelly frech Windows 10 installation.

    Sorry to hijack your thread!

  • 0 in reply to Jonas Lorander
    TI__Mastermind 30506 points
    Jonas,

    I wanted to check in with you to see if you were able to make any progress on this. I tried as well, but I'm afraid I could not get past the ROM section either. My research seems to indicate a possible speciific problem with RNDIS with the Fall 2017 Build 1709 version of Win10. Unfortunately, this is all I have access to at this time.
  • 0 in reply to RonB
    Intellectual 265 points

    Hi Ron,

    I was unable to get it working. I have tried it on two different computers with Win10 Build 1809.

    If I rebooted the computer and turned off driver signing, I could install a modified version of the RNDIS driver, but UniFlash did not want to stat the flashing process.

    At the moment we are sticking to the Raspberry Pi solution. I have looked in to using Windows Subsystem for Linux on Win10, but there is a problem that Windows are only letting in COM-ports and Mass Storage Devices in to WSL at the moment. When, and if, they add libusb support I hope to test that out again.

    I'm still curious to know what Joni did to get it flashing in the first place.