[Ericj92]

Fixed it! Windows firewall was bothering me.

[Ericj92]

I got the device in the USB bootloader mode, by performing the following steps:

1. Connect FTDI cable on UART0, Hold done boot button, Connect AC adapter and check for a series of C characters on the terminal: device must be in serial mode
2. Connect FTDI cable on UART0, Hold done boot button, Connect micro USB cable and check the terminal: No C characters, device must be in serial mode
3. Delete USB serial driver in device manager(somehow my USB ethernet device was recognized by Windows as a serial device)
4. perform step 2 again
5. linux RNDIS devices pops up.

Next I have compiled a new u-boot-spl bootloader, and followed the steps of:

We demonstrate how to use Uniflash to program EEPROM for the OSD335x family here:
https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/#_Toc382081434

But somehow the device doesn’t show up in the UNIflash tool.

Eric

[Ericj92]

Hi Neeraj,

I tried a couple of different windows 10 host machines, but no success. Is there a special RNDIS driver required in order to get the RNDIS bootloader working?

[Ericj92]

I am sure that the device boots normally on the emmc, but I want the device to jump to USB boot to create an automated script for the initial flashing of the device(similar to the octavo application note). I assume that the following devices are probed during boot, from firs to last:

– SPI0: nothing present to boot
– MMC0: (SDcard interface) no card present, nothing to be booted
– USB0: Cable will be plugged in, while holding the boot button down
– UART0: A USB serial device pops up after few seconds and on the debug header(UART0) a couple of c characters are printed.

Is there something wrong/odd with the USB layout preventing the USB boot to trappped?

[Author]

Posts