• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 900 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.

IWR6243: How to troubleshoot boot up

Tyler Barton
Prodigy 20 points
Other Parts Discussed in Thread: IWR6243

I have some demo boards based on PROC127A.  My schematic and PROC127A are 100% identical.  I have one board that is fully functional and I am able to get data off the CSI2 interface.  My other boards fail at different steps in the boot up process.  I am looking for any flags put out by the IWR6243 to see what the exact problem is.  Are there any suggestions on what pins to monitor to see what is going on?

  • 0
    TI__Genius 14415 points

    Hi Tyler,

    What MCU are you using to control these devices? Or what other board are you using? The board you refer to above has just 2 IWR6243 devices on board right? What devices are failing to boot, and what stages are they failing? Upon initial ROM boot, after configuration, after the first transmission? Any pattern or other info? If there are board to board variations it seems likely to be a power or soldering issue. 

    Do any of the nerror LEDs come on? Are they on from power or turn on during the boot/configuration?

    Thanks,

    Jackson

  • 0
    Prodigy 20 points

    I am using the PROC137A (Sitara AM273X) board to control these devices.  Yes, the PROC127A have two IWR6243 devices.  I have four non-functional boards.  Two go through boot up to the point that they send the rlRfInit and fails before it sends data out on the CSI2.  Neither have NERROR LEDs light up.  Another board ssends the rlDevicePowerOn(Master) and then gives the NERROROUT.  The last board sends the rlDeviceAddDevices(slaves), but then hangs and does not turn on the NERROROUT.  Is there a BSDL file available to do a boundary scan of the chips?  Or can we get the code composer configuration for the IWR6243 and the source code that runs on the R4 microcontroller and its build system?

  • 0 in reply to Tyler Barton
    TI__Genius 14415 points

    Hi Tyler,

    Thanks for the details. I will look into this. I still think a power issue seems the most likely since they seem to fail at different points. However, are these scenarios repeatable? For each board the error happens at the same point each time?

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 20 points

    Jackson,

    The IWR6243 is getting the correct voltages.  It is likely a bad component or improper workmanship.  The errors are repeatable.  It would be helpful to narrow down what the issue is by looking at flags during the boot sequence.  It would also help a lot to do a boundary scan to rule out the IWR6243 itself.

  • 0 in reply to Tyler Barton
    TI__Genius 14415 points

    Hi Tyler,

    I also agree. I more meant runtime power issue, which would likely be some board manufacturing issue. I am getting some more suggestions for testing and checking. Please give me until Friday to coordinate a couple more suggestions based off the demo SW on the sitara we provided.

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    TI__Genius 14415 points

    Hi Tyler,

    Common reasons for the setup to fail during those steps is improper power during the calibrations that run leading to a brownout. This could be why they are all failing at slightly different times. Are you able to scope the power while running startup to see if it is getting pulled down?

    I think at this point we likely need to take this offline so we can do a layout review and talk more specifically about the power measurements and setup. I will start an email thread to discuss.

    Regards,

    Jackson