AWR1642BOOST: can not uniflash the vital sign lab's bin（Uniflash stuck on "opening com port com3..."） , but can uniflash the sdk's domo bin by the same steps.

user5919941

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH, , AWR1642

Dear TI:

my device is awr1642boost（5337900391） , uniflash 4.6.0.

1. the com port showed on PC is ok .

2. and I follow the sdk' demo（choose the com3, browse the demo's bin, put the sop0 and sop2, powered recycle with sw2）, and uniflash the demo's bin successfully.

3. I follow the same steps in 2 above , of course i browsed the vital sign lab's bin, but it can not work.

[2019/2/19 下午12:35:35] [INFO] Cortex_R4_0: Initialization complete.

[2019/2/19 下午12:35:35] [INFO] Cortex_R4_0: Flashing process starting...

[2019/2/19 下午12:35:35] [INFO] Cortex_R4_0: Connecting to COM Port COM3...

[2019/2/19 下午12:35:35] [INFO] Cortex_R4_0: Reset connection to device

[2019/2/19 下午12:35:35] [INFO] Cortex_R4_0: Set break signal

[2019/2/19 下午12:35:55] [ERROR] Cortex_R4_0: Initial response from the device was not received. Please power cycle device before re-flashing.

[2019/2/19 下午12:35:55] [ERROR] Cortex_R4_0: Not able to connect to serial port. Recheck COM port selected and/or permissions.

[2019/2/19 下午12:35:55] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...

[2019/2/19 下午12:35:55] [INFO] Cortex_R4_0: Instance deinitialized!

4. and when i return to the sdk demo'bin in above 2, i got the same problem, it seem that the vital sign lab's bin caused the com port com3 's problem.

[2019/2/19 下午12:56:54] [INFO] Cortex_R4_0: Initialization complete.

[2019/2/19 下午12:56:54] [INFO] Cortex_R4_0: Flashing process starting...

[2019/2/19 下午12:56:54] [INFO] Cortex_R4_0: Connecting to COM Port COM3...

[2019/2/19 下午12:56:54] [INFO] Cortex_R4_0: Reset connection to device

[2019/2/19 下午12:56:54] [INFO] Cortex_R4_0: Set break signal

[2019/2/19 下午12:57:14] [ERROR] Cortex_R4_0: Initial response from the device was not received. Please power cycle device before re-flashing.

[2019/2/19 下午12:57:14] [ERROR] Cortex_R4_0: Not able to connect to serial port. Recheck COM port selected and/or permissions.

[2019/2/19 下午12:57:14] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...

[2019/2/19 下午12:57:14] [INFO] Cortex_R4_0: Instance deinitialized!

thanks a lot !

over 5 years ago

0 Jitendra Gupta over 5 years ago

TI__Guru 69330 points

Hi,
Binary file selection can not cause this issue. Before initiating UniFlash better you do the physical power cycle (adaptor disconnect/connect).
And are you able to flash xwr16xx_mmw_demo.bin multiple times after every power cycle?

Regards,
Jitendra

0 user5919941 over 5 years ago in reply to Jitendra Gupta

Prodigy 30 points

Dear Jitendra Gupta:

Thanks for your replying.

1. Of course i do the physical power cycle before initiating uniflash, and also power cycle before loading iamges. And i am not able to flash xwr16xx_mmw_demo.bin multiple times after every power cycle, but i can flash xwr16xx_mmw_demo.bin ater every power cycle.
2. In the uniflash, my device is auto-choosen like following .

3. The mmwave_automotive_toolbox is mmwave_automotive_toolbox_2_4_7 , but the vital signs lab 's bin is not in the path showed in the DriverVitalSigns_GettingStartedGuide (\labs\lab0001-driver-vital-signs\pre-built-binaries\vitalSigns_16xx.bin). In mmwave_automotive_toolbox_2_4_7 , the bin's path is \mmwave_automotive_toolbox_2_4_7\labs\lab0001-driver-vital-signs\vitalSigns_target\pre-built-Binaries\vitalSigns_16xx.bin.

4. and when i load the vital sign's bin, the uniflash gets stuck in the step (connected to com port ) like the following for hours , so i stopped the uniflash by PC's task manager。and please watch out the console.

5. Then i power cycle the device and load the sdk demo's bin , it worked. and i find the console, compared with the stucked picture above , it continued with the following :

[2019/2/20 下午2:27:17] [INFO] Cortex_R4_0: Checking file C:/ti/mmwave_sdk_02_00_00_04/packages/ti/demo/xwr16xx/mmw/xwr16xx_mmw_demo.bin for correct header for AWR1642.

[2019/2/20 下午2:27:17] [INFO] Cortex_R4_0: AWR1642 device, fileType=META_IMAGE1 detected -> OK

[2019/2/20 下午2:27:17] [INFO] Cortex_R4_0: !! Files are valid for AWR1642.

6. SO will it be that the vital sign's bin is not for correct header for AWR1642?（so the unifalsh get stucked in the console）, because the mmwave_automotive_toolbox is mmwave_automotive_toolbox_2_4_7, and the bin's path is also not the path in the DriverVitalSigns_GettingStartedGuide.

Thanks a lot!

0 user5919941 over 5 years ago in reply to Jitendra Gupta

Prodigy 30 points

Dear Jitendra:
Thanks a lot!
The problem is solved by put the aotomotive tool box in the default path, c/ti/<automotive toolbox>/......... 。
Because my early path includes the Chinese path, so it stucked on " Checking file ".

THanks again and Best wishes for you!

Sensors

Sensors forum

AWR1642BOOST: can not uniflash the vital sign lab's bin（Uniflash stuck on "opening com port com3..."） , but can uniflash the sdk's domo bin by the same steps.