• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 84 subscribers
  • Views 1558 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.

Bricked F28069 Launchpad

Andrew Butler
Expert 2520 points


I believe I bricked my F28069 Launchpad. Are there any program files available that can unbrick my device?

  • 0
    Guru 192875 points
    HI Andrew,

    What actually did you do to brick it ? :)

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Expert 2520 points

    I'm not exactly sure but I was trying to power the board with a Lithium Ion battery and the battery is not actually 3.3V. It's more like 4V. I also was trying to communicate over the  USB to UART line.

  • 0 in reply to Andrew Butler
    Guru 192875 points

    So did you check what all components have been damaged by doing so?
    Check the mcu's health first! So did you give Li-ion battery directly to 3.3V pin & GND?

  • 0 in reply to Gautam Iyer
    Expert 2520 points
    I provided the battery directly to 3.3V and GND. It will be easier if I try and unbrick the launchpad then to check every single component on the board. If it won't unbrick then I can possitively say its a hardware issue. So is there any programs that can unbrick the F28069 launchpad?
  • 0 in reply to Andrew Butler
    TI__Guru** 119670 points
    if you over-voltage the MCU pins there is nothing to un-brick, the device is damaged and would need to be replaced. which in your case means just getting a new Launchpad.

    "bricking" is a term usually describing that the memory of the device has been corrupted and you would like to un-brick (wipe the memory back to default settings) to start fresh. This is not possible on F28x devices if the CSM has been set with unknown values. There is no mass erase function (as this is a security hole). Once the CSM is set you must know the password to unlock. Period.
  • 0 in reply to ChrisClearman
    Expert 2520 points
    The main reason why I thought I bricked the board is because it doesn't makes sense for a 3.3V battery to damage a 3.3V MCU. So I figured something got corrupted in software and I just wanted to reset it. However, since that is not an option, can you provide me with a diagram of the proper way to connect a battery to this board with the correct jumper positions so i wont damage another one.
  • 0 in reply to Andrew Butler
    TI__Mastermind 22025 points

    Andrew,

    I took a look at the electricals for that device and it looks like it should be able to handle up to 4.6V, so I'm not sure why the board isn't working with your battery.

    When you've tested it since, has it been powered by the battery or USB?  You may want to try using USB power if you haven't yet.

    BR,

  • 0 in reply to Trey German289
    Expert 2520 points
    Yes, I have tried powering it with USB and the LEDs come on on the board and it even allows me to flash code to the board. However, as soon as I run the the code it exits and goes into disassembly. The only other thing I can think that is damaging the board is the current draw so maybe I am trying to draw more current than the battery can source and the battery just craps out. The battery can only source 1A and the battery only has internal under/over voltage protection.
  • 0 in reply to Andrew Butler
    Expert 2520 points
    I also had the USB cord plugged in while the battery was powering the board because I was reading data over the USB/UART
  • 0 in reply to Andrew Butler
    TI__Mastermind 22025 points
    If you can flash the board, the MCU and all of its support hardware are fine.

    A brownout could cause the code to go into disassembly, so that's an option. Is there a load connected to the same power source drawing a lot of current? The other option is that there could be problems with your application which is causing it to go "into the weeds".

    BR,
  • 0 in reply to Trey German289
    Expert 2520 points
    It works fine if I run my code while powering the board using USB. I only have problems when using a battery. This is the 2nd board I have done this to. I know the 1st board has hardware damage because the board lights up for a second and then goes dead but the is 2nd board allows me to do everything but run the code. It goes without saying that my battery is the problem but that is weird to me.