• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 232 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.

Original question:

RTOS/CC1352P: Main Assert handler problem in cc1352 devices

CC1352P: MAin assert handler problem with CC1352P REV E IC

Haricharan sarpatwar
Expert 1750 points
Part Number: CC1352P

Hi,
I am using REV E CC1352P ICs in my custom board. My application is collector application in TI 15.4 stack
I am using following softwares
SDK V3.20.00.68
ccsV9.1

Collector in Non beacon mode


My application is working fine with REV C custom board but after porting to V3.2 and hardware changes in custom board are made. My firmware is entering in to main assert handler some times and some times debugging correctly. what could be the possible reasons for main assert handler in firmware.
Note: Hardware changes are made as per launchpad REVE schematic

Thanks and regards
Haricharan

  • 0
    TI__Mastermind 28400 points

    Hi,

    To narrow down where the issue could be, please try the following items:
    - run out-of-box 3.20 example on your custom board with Rev E silicon (if the example runs as expected, then the custom board is probably ok)
    - run your ported application on a launchpad with Rev E silicon (if your application runs as expected, then the ported software is probably ok)

    Let us know the results of these.

    Regards,
    Toby

  • 0 in reply to Toby Pan
    Expert 1750 points

    Hi,

    Thank you for your response, i added CPUDelay(12000000); instruction before initialization of peripherals which resolved my issue.

    Thanks & Regards

    Haricharan