Part Number:AWR1443BOOST
Hi,
Having issues with flashing the high accuracy lab xwr1443 to the AWR1443BOOST EVM module. Its under version 3.1.1 of the industrial toolbox but ive also tried 2.5.2 with the same issue. Console output of Uniflash below.
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Initialization complete.
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Flashing process starting...
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Connecting to COM Port COM1...
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Reset connection to device
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Set break signal
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Connection to COM port succeeded. Flashing can proceed.
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Reading device version info...
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: ** 2 files specified for flashing.
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Checking file C:/Users/danielsa/Documents/mmwave_industrial_toolbox_3_1_1__win/mmwave_industrial_toolbox_3_1_1/labs/lab0004-high-accuracy-14xx/lab0004_high_accuracy_14xx_pjt/prebuilt_binaries/xwr12xx_xwr14xx_radarss.bin for correct header for
AWR1443.
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Header of C:/Users/danielsa/Documents/mmwave_industrial_toolbox_3_1_1__win/mmwave_industrial_toolbox_3_1_1/labs/lab0004-high-accuracy-14xx/lab0004_high_accuracy_14xx_pjt/prebuilt_binaries/xwr12xx_xwr14xx_radarss.bin file indicates it is not a valid file to flash to
AWR1443: 0xb55a03d1L
[21/11/2018 16:35:33] [ERROR] Cortex_R4_0: !!! Aborting flashing of specified files!!!
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Disconnecting from device on COM port COM1...
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...
[21/11/2018 16:35:33] [INFO] Cortex_R4_0: Instance deinitialized!
I had this same issue with the demo code too. I had to move from a 3.0SDK to 2.1SDK, it flashed succesfully for the 2.1SDK and i've had the radar module running on the visualiser succesfully, 3.0 has the same error as above.
I dont understand why im getting these issues as its the latest silicon ES3.0 594FC.
SOP headers have been checked and double checked, and as indicated previously i have had demo code sdk2.1 flashed on the device and ran succesfully