• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 563 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1243: Differences in Hardware versions- in bootloader

Santhana Raj
Expert 1765 points
Part Number: AWR1243

Hi team,

I am facing a problem with firmware load over SPI between different versions of AWR1243 devices. My problem is as below.

I power on the device, load the firmware and the config for the master then followed by add device and load firmware for slaves. I am always getting an error /hang during the firmware load of the slave.

I have tried increasing the timeout for the SPI/interrupt for every message to 5s. Still the error happens

This approach works superbly fine with my earlier version of the custom board, but doesnt work with the current version. (there is no hardware PCB change between the two versions of the Custom board).

My questions are as below:

1) I suspect that there are some minor changes related to hardware chip versions on my boards.I suspect this is related to the Bootloader as it might be expecting some process flow differently and I am doing differently in Sw (as per old version). Can anyone help us to confirm whether there are any changes in this regard between ES1.0, ES2.0 and ES3.0 for AWR1243?

Please note that the Custom Board is from my Customer and I don't have any information regarding which ES version is being used in old custom board and new custom board.

2) I am pretty sure that the current Custom board uses AWR1243P. Hence, My earlier question applies here again.

Is there any minor changes in Boot loader, that changes the firmware load approach between the devices AWR1243 and AWR1243P.

Any pointers on this issue will be really helpful.

Thanks in Advance,

Santhana Raj

PS: We are using 4 chip Cascaded mode of AWR1243.

  • 0
    TI__Mastermind 24955 points
    Santhana,

    AWR1243P has not released to market so the board in question would only have AWR1243 devices on it.

    You should load the firmware to all devices before completing any configurations.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Expert 1765 points
    Hi Kyle,

    Thanks for the info about firmware. But It is not clear what you are suggesting.
    About AWR1243P, i understand that its not available in public access. But I assure you that our new board has them. Cause of NDA, I cant disclose any more details.

    I understand that firmware has to be loaded before any profile/chirp configurations. But Is the firmware load compulsory for initial QSPI/SPI/UART transmissions also??
    This is a bit contradictory because, the Radar SDK use-cases dictate to program the AWR1243 devices through SPI lines. Hence I suspect the bootloader can initiate the basic SPI/QSPI/UART interfaces on startup before firmware load.
    My question basically boils down to : Is there a different RSS firmware to load on AWR1243P devices that are supposed to work in Cascaded mode???
  • 0 in reply to Santhana Raj
    TI__Mastermind 24955 points
    Santhana,

    You download the same BSS firmware to the AWR1243, regardless of whether the device is acting as the master device or the slave device in a cascade setup.

    Regards,
    Kyle