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.

CCS/IWR1642BOOST: Unable to Programming Serial Data Flash Over UART used UniFlash tool

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH, , IWR1642, AWR1642

Tool/software: Code Composer Studio

Hello, uniflash team,

I have a test in TI IWR1642BOOST, I want to download the demo package BIN file(xwr16xx_mmw_demo.bin) via UART directory in UniFlash(5.0.0) without usb(connect with XDS110),

(1) Modify the IWR1642BOOST Hardware, remove the R128 and 129, connect the R169 and R166 with 0 Omh resistance,as below,

(2) Select the Flashing Mode(101),
(3) Used a FTDI to USB adapter to connect PC and iwr1642 UART(RX: Ball N4 / TX: Ball N5 ) through J6(Pin 5 and Pin 7).
(4) Used a 5V/2A power adapter to supply Power, then connect [FTDI to USB adapter] to PC. Open uniflash tool to download BIN file.

But it could not download, the error code as above!!!!

I have posted the issue in Sensors forum(e2e.ti.com/.../3028358

the TI Engineer in the Sensors forum let me check with the uniflash team by posting on the Tools forum to comfirm if the USB adapter is compatible.

Could you take some suggestions?

I am waiting for your reply, it is very very Important for me.

Regards,

Eric

  • Eric,

    Looking at the schematics it seems the UART communications port of the XDS110 is indeed directly connected to the AWR1642 device. This suggests the device is handling the boot and flashing mechanism and Uniflash may simply be waiting for some sort of string from the AWR1642 device and starts sending data to it. 

    However, I suspect that Uniflash may issue a device or board reset, so the SOP jumpers can be re-read and the AWR1642 device boots in the proper way to accept UART commands. 

    You can try to manually tap the reset switch (NRST SW2) immediately before or after you try to connect to the device and see if Uniflash is capable of communicating with it. 

    Apart from this, I don't know what else could be happening as the device UART boot should be straightforward, unless there is another intrinsic hardware-related feature that I am unaware. 

    Hope this helps,

    Rafael

  • Eric,

    I am unsure what else may be going on in this case. I was pointed out to chapter 4 of the document below and specifically to the flowchart at section 4.4, which indicates the device waits for a break signal from Uniflash, thus it does not seem to require a full reset if the device is already in SOP mode 5. 

    http://www.ti.com/lit/an/swra551/swra551.pdf

    At any rate, double check the requirements of this document and perhaps try to insert a logic analyzer and see if you can evaluate the signaling and flow. Another aspect may be signal integrity via an oscilloscope. 

    Hope this helps,

    Rafael

  • Hi User,

    It appears you are not connecting to the correct COM port, you'll need to connect to the port corresponding to Class Application UART as shown in the SDK Demo User Guide.

    Cheers,

    Akash