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

Original question:

CC2340R5: Getting status code 0x21 from HCI_EXT_EnhancedModemTestTxCmd after porting my app to a newer sdk version

CC2340R5: Excessive Current Draw From MCU

Alexander Trujillo
Prodigy 170 points

Part Number: CC2340R5

Hello,

We have recently encountered an issue that is likely related to something during the manufacturing process that results in the CC2340R53 on our pcb drawing an absurd amount of current. Likely, something internally on the MCU is getting damaged. For example, our application normally averages between 10-20uA during operation, but units that exhibit this state end up drawing anywhere from hundreds of uA to hundreds of mA on average instead. The application seemingly works like normal otherwise when put on a test fixture.

I was wondering if there were any helpful registers that could be monitored to see what internally has happened to the MCU. One note is that if the problematic MCU is swapped out for a known good one, the current draw returns to normal, so we have narrowed it down to something happening to the MCU.

Thanks,
Alex Trujillo

  • 0
    TI__Genius 16044 points

    Hello Alex Trujillo 

    As a test could you load the empty project (and comment out the GPIO toggle), this project should put the device into a constant standby which we should be able to measure.

    Also for your project what is the target SDK being used? 

    Thanks,
    Alex F

  • 0 in reply to Alex Fager
    Prodigy 170 points

    To clarify, this is an issue after our devices are built up so something is likely happening during our manufacturing process to cause this. 

    The standby current on devices with this issue sits at anywhere from a few hundred uA to a few hundred mA. This has already been measured. The main thing I was looking for were some hardware status registers that could be read via HWREG that could provide some status information as to what part of the mcu is being damaged.

  • 0 in reply to Alexander Trujillo
    TI__Genius 16044 points

    Hello Alex Trujillo,

    If we are unaware of what register is damaged you can dump the registers, have two cases one register dump of the "working" device and one of the "error" device and do a compare. 

    Thanks,
    Alex F