Nvflash freeze

Technical Support
, ,
1

I was trying to follow the instruction of “Txx Recovery Mode” to update my newly purchased Apalis T30 from pre-installed linux to WinCE 2013. The process failed at “update.bat” (nvflash). It was hung at “sending file: loader.nb0”. Here is the full output:

Nvflash version 2.5 started
rcm version 0X30001
System Information:
   chip name: unknown
   chip id: 0x30 major: 1 minor: 3
   chip sku: 0xb1
   chip uid: 0x0000000000000000015d4bdf4d38100a
   macrovision: disabled
   hdcp: enabled
   jtag: enabled
   sbk burned: false
   dk burned: false
   boot device: emmc
   operating mode: 3
   device config strap: 0
   device config fuse: 0
   sdram config strap: 0

Sending generated BCT...533Mhz Done
downloading bootloader -- load address: 0x88300000 entry point: 0x88300000
sending file: loader.nb0

Not sure what went wrong – any suggestions?
Thanks.

2

Dear @yzoupri,

Thank you for contacting support.

Was that module booting with Linux?

Could you please log the debug message which will be output on UART-A and share with us during recovery?

Which Carrier board or Eval board you are using? which all are USB ports are connected to the PC?

Is there any USB driver installation problem(yellow mark) on the Windows development PC?

Did you already recovery mode flashing success on the Windows development PC?

3

Hi Raja.tx,

Yes, the module is booting with Linux – even after the failed “update.bat”. My original post includes all the output from the command prompt (the same as in log file). The carrier board is Ixora. I was using Windows 10 installed on VMware Fusion hosted by iMac Pro. There are two USB ports used: one for USB-serial and one for APX. All drivers installed without any issue. One more interesting I have noticed during the trials is that, if I open command prompt and run nvflash.exe --configfile ce8.cfg --create --go directly instead of update.bat, I got a bit further (some bytes sent, but not all after sending file: loader.nb0. Here is the output:

Nvflash version 2.5 started
rcm version 0X30001
System Information:
   chip name: unknown
   chip id: 0x30 major: 1 minor: 3
   chip sku: 0xb1
   chip uid: 0x0000000000000000015d4bdf4d38100a
   macrovision: disabled
   hdcp: enabled
   jtag: enabled
   sbk burned: false
   dk burned: false
   boot device: emmc
   operating mode: 3
   device config strap: 0
   device config fuse: 0
   sdram config strap: 0
Sending generated BCT...533Mhz Done
downloading bootloader -- load address: 0x88300000 entry point: 0x88300000
sending file: loader.nb0
 - 65536/472104 bytes sent

The flashing process hangs forever at this point.

Thanks,

4

Hi Raja.tx,

It turns out the issue is with doing it from Windows 10 installed on VMWare – for whatever reason. I was able to flash the board from a pure windows PC.

Thanks,

Yong

5

Hi Raja.tx,

Yes, the module is booting with Linux – even after the failed “update.bat”. My original post includes all the output from the command prompt (the same as in log file). The carrier board is Ixora. I was using Windows 10 installed on VMware Fusion hosted by iMac Pro. There are two USB ports used: one for USB-serial and one for APX. All drivers installed without any issue. One more interesting I have noticed during the trials is that, if I open command prompt and run “nvflash.exe --configfile ce8.cfg --create --go” directly instead of “update.bat”, I got a bit further (some bytes sent, but not all after “sending file: loader.nb0”. Here is the output:

Nvflash version 2.5 started
rcm version 0X30001
System Information:
   chip name: unknown
   chip id: 0x30 major: 1 minor: 3
   chip sku: 0xb1
   chip uid: 0x0000000000000000015d4bdf4d38100a
   macrovision: disabled
   hdcp: enabled
   jtag: enabled
   sbk burned: false
   dk burned: false
   boot device: emmc
   operating mode: 3
   device config strap: 0
   device config fuse: 0
   sdram config strap: 0

Sending generated BCT...533Mhz Done
downloading bootloader -- load address: 0x88300000 entry point: 0x88300000
sending file: loader.nb0
 - 65536/472104 bytes sent

The flashing process hangs forever at this point.

Thanks,