• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 232 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.

IWR1443BOOST: Uniflash Flash Program Not Running

Mari Tsunoda
Expert 5726 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: UNIFLASH,

Tool/software:

Hi Team,

My customer is trying to run a program that they loaded via Uniflash. 

They are flashing the mmw demo on their IWR1443BOOST (ES3.0) board and using mmWave SDK v2.1.

They connecting the jumpers SOP0 and SOP2 for flash programming mode and writing the xwr14xx.bin file as the metaimage via Uniflash GUI.

After they disconnect power from the board, they remove the SOP2 jumper to enable functional mode and connect to power.

They then connect the User UART COM port via teraterm and send sensorStop command, but there is no response.

They have also tried adding the code below to light up DS3 onboard LED within the mmwDemo_initTask in main.c file, but the LED is not lighting up.

/* Initialize the GPIO */
GPIO_init ();
GPIO_write (SOC_XWR14XX_GPIO_2, 1U); //DS3 LED

Do you have any comments or advice to debug this?

Best regards,

Mari Tsunoa

  • 0
    TI__Expert 5726 points

    They are also using Uniflash version 8.8.1. Has there been any reported bugs or issues using uniflash and ES3.0 booster board?

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 20520 points

    Hello Mari.

    I don't believe there is any known issues at the moment.  When you hit enter on teraterm, do you see any output?  Have you also made sure that you adjusted the baud rate in the serial terminal to the one expected by the demo(should be 115200 but may be different based on the demo).

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 5726 points

    Hi Santosh, 

    Yes they have already configured for the correct baudrate as you mentioned.

    Is there any other way they can debug this to see if it has been loaded correctly?

    Can they use a memory browser feature in ccs or Uniflash? I do not have an evm on hand so I cannot confirm on my end.

    Best regards,

    Mari Tsunoda

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 20520 points

    Hello Mari.

    There is a memory browser feature in CCS that you can use.  Also, if there is a boot issue the nERROR LED should turn on on the EVM.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Expert 5726 points

    Hi Santosh,

    They gave me an update.

    They re-installed the mmwaveSDK, ran the setenv.bat and rebuilt their environment using make which output the .bin file. When they flashed this file via uniflash, they could not send commands via UART (no output).

    I asked my customer to try loading the ccsdebug.bin via CCS using the target config file as well. They rebuilt the ccsdebug.bin file in their environment, flashed the binary and executed the .xer4f from CCS and were able to successfully send UART commands.

    So it looks like the board itself is not the issue and the image or flashing steps is the issue instead.

    I saw some other threads comment that firewall could block UART commands, but this also does not seem to be the issue.

    Could you give some advice on how to proceed debug for my customer?

    Does .bin file not allow for UART commands to be received? 

    Best regards,

    Mari Tsunoda

  • 0 in reply to Mari Tsunoda
    TI__Mastermind 20520 points

    Hello Mari.

    Let me see if I can replicate this on my end with a 1443BOOST EVM.  I will try to acquire an EVM by sometime next week and try the steps myself.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Mastermind 20520 points

    Hello Mari.

    Which demo is your customer using?  And are they making any modifications to the demo?  Since they are able to flash the demo, it may be a problem with the demo execution itself.  I would try flashing the debug binary, then load the .xer4f binary via CCS debug to see where it may be hanging or crashing.

    Sincerely,

    Santosh