• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 1994 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1443: Fail to burn spi flash with uniflash tool on customer ES2.0 board

Chris Meng
Mastermind 35145 points
Part Number: IWR1443
Other Parts Discussed in Thread: UNIFLASH

Hi,

My customer has made some IWR1443 boards. At beginning they used ES1.0 chips. Now with same PCB, they used ES2.0 sample on board. But they failed to burn the spi flash with uniflash tool (SOP=101). Pls find the error log below. Customer already see the COM port in device manger when connecting usb with board and PC and set the right COM port in uniflash tool.

Customer also tried some other tests.

1. Using uniflash tool to burn ES1.0 customer board. There is no COM port error.

2. Try to connect customer ES2.0 board with CCS. It is connected succesfuly. This means the IWR1443 chip should boot ok. SOP=100.

3. Try to power off/power on customer ES2.0 board, and try uniflash tool. But still fail.

No matter the customer board is using 1443 ES1.0 or ES2.0, customer burn same XDS110 image on the M4 chip on board (same design as EVM). I think there should be no difference on the XDS110 image for ES1.0 and ES2.0. Pls help to confirm.

Would you pls help to advise what is missed to burn the spi flash with uniflash tool on IWR1443 ES2.0 customer board?

Thanks,

  • 0
    TI__Intellectual 1305 points

    Hi Chris,

    The issue the customer is running into is strictly related to the serial port connection, and not the XDS110 image used for the ES1.0 or ES2.0 devices. Can you provide answers for the following questions:

    1) When testing with the ES1.0 device, is the exact same serial port connection (USB port) on the computer connected to the device?

    2) If after the ES2.0 device flashing was attempted (and failed), can the customer try to connect to the ES1.0 device to the same serial port connection on the computer and try to flash that device?

    What I am trying to figure out is if that particular serial port connection on the computer has an issue. Can the customer try a different USB port?

    During UniFlash testing, I once encountered a situation where the serial port on the windows machine would hang/be busy and I had to reboot my computer.

    I noticed from the errors produced in the captured image that the customer is clicking "Format SFLASH" button. Does the customer see the issue when trying to flash an image to the device with the "Load Image" button? I would expect the same behaviour.

    From what you have clearly explained above, I don't see any missing steps. The SOP value 101 is correct, and the device was powered off and on again while connected to the serial port.

    Thanks,

    Pragat

  • 0 in reply to Pragat Chaudhari
    TI__Mastermind 35145 points

    Pragat Chaudhari said:

    1) When testing with the ES1.0 device, is the exact same serial port connection (USB port) on the computer connected to the device?

    2) If after the ES2.0 device flashing was attempted (and failed), can the customer try to connect to the ES1.0 device to the same serial port connection on the computer and try to flash that device?

    ES1.0 and ES2.0 board uses same COM port (COM26). When flashing ES2.0 fail and then connect ES1.0 board, it is ok to use uniflash.


    Pragat Chaudhari said:
    What I am trying to figure out is if that particular serial port connection on the computer has an issue. Can the customer try a different USB port?

    Customer has tried two PCs.

    Pragat Chaudhari said:
    During UniFlash testing, I once encountered a situation where the serial port on the windows machine would hang/be busy and I had to reboot my computer.

    Customer has rebooted the PC, but still failed with ES2.0 board.

    Pragat Chaudhari said:
    I noticed from the errors produced in the captured image that the customer is clicking "Format SFLASH" button. Does the customer see the issue when trying to flash an image to the device with the "Load Image" button? I would expect the same behaviour.

    Yes. Same error when click load image on ES2.0 board.

  • 0 in reply to Chris Meng
    TI__Mastermind 35145 points
    Pragat,

    Is there any register customer can check (in ccs) the value of SOP ROM code reads? I can't find such register in TRM.
    Thanks,
  • 0 in reply to Chris Meng
    TI__Mastermind 35145 points
    Pragat,

    I think there is no difference on external circuit for IWR1443 ES1.0 and ES2.0. Would you pls help to confirm?

    Thanks,
  • 0 in reply to Chris Meng
    TI__Mastermind 35145 points
    Pragat,

    Customer has only two ES2.0 boards, but both of them failed to use uniflash.

    But there is one difference with two boards. The NERROR_OUT pin outputs low on one board and high on other board. I checked the ES1.0 1443 EVM and this pin outputs low, but this is an known issue. I think this should be fixed in ES2.0. But why two ES2.0 boards with different NERROR_OUT status?
    Both two boards have not been successfully burned spi flash yet.

    Thanks,
  • 0 in reply to Chris Meng
    TI__Mastermind 35145 points

    Pragat,


    The problem is solved. It is due to the failure of one diode on customer's ES2.0 board. After changing the diode, customer can burn the ES2.0 board well.

    Thanks,