• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 196 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.

CC2642R: BIOS_start hangs in TimerProxy startup

Esa Heinonen
Prodigy 70 points

Part Number: CC2642R

My application hangs in BIOS_start() before any of the application's tasks start to run. This doesn't happen every time, but the frequency seems to be increasing.

Looks like an exception has occurred in TimerProxy startup (see the partial screenshot below). What could be the reason for the exception?

  • 0
    TI__Guru**** 223617 points

    Hi Esa,

    Are you using a custom PCB or TI EVM, and have you tested with multiple units?  What is your debugger interface/connection and does the device ever lock up if you free run without the debugger?  Does this happen with default TI examples and have you made any modifications to the CCFG?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 70 points

    Hi Ryan,

    This is a custom PCB developed by my customer. So far I have only tested with one board, but I do have another one to try. The other developer in this project has also seen some occasional lockups, but I'm not sure they are related to this one.

    The debugger interface is XDS110 with a two-wire cJTAG connection to the board. I think I have seen the issue also when the device was running free.

    Once the issue pops up, restarting the program in the debugger does not help (Suspend/Restart/Resume). Starting a new debug session usually lets the device pass through BIOS_start and start running the application's tasks.

    I haven't tried to run the TI examples on these boards. Our program is based on Project Zero and we have modified the CCFG to use an external LF clock source.

    I'll see if I can find out some more symptoms or clues.

    Regards,
    Esa

  • 0 in reply to Esa Heinonen
    TI__Guru**** 223617 points

    Thanks for the update.  Please test multiple boards and make sure you have a short, robust cJTAG connection.  You can test with the internal LF RCOSC to determine whether the external crystal contributes to the issue (see SWRA499 and SWRA640) and consider submitting a SIMPLELINK-2-4GHZ-DESIGN-REVIEWS if you have any concerns about the hardware design.

    Regards,
    Ryan