Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 5 replies
  • Answers 4 answers
  • Subscribers 7 subscribers
  • Views 1083 views
  • Users 0 members are here
Related

Bricked FRDM-K82F

cybermah

Hi,

 

I have a  FRDM-K82FFRDM-K82F board that I bricked by plugging it in my windows 10 laptop before knowing about the bootloader bug with windows 10 I would like to get the board working again and I was wondering if anyone has information on how to reload the OpenSDA bootloader I have seen post somewhere for a different board where they used another board to reload it I do have a second K82F board but I'm not sure how to use it to load a bootloader on the bricked one I was also thinking about buying a programmer from ebay that I think would do the same job ULINK2 USB JTAG Emulator support MDK4.54 ARM7 Cortex Keil Debug Adapter AK, but I would have to make a cable to convert it from a 20 pin 2.54mm pitch to a 10 pin 1.27mm pitch.  Has anyone used this type of programmer? And would it work to load the bootloader?

 

Thanks

Dana.

Parents
  • 0

    Hi Dana,

     

    I don't know what bricking issue you're referring to, nor have I used this board, but I have noticed that a lot of the FRDM boards won't work with Windows 10 until the bootloader has been upgraded, and so far for me that has entailed finding a Windows 7 machine and performing the bootloader upgrade via USB, not with a USB-JTAG adapter. However recently someone reported finding a way to do it with Windows 10, see here: https://developer.mbed.org/questions/74001/Update-FRDM-bootloaders-using-only-Windo/  although I've not tried this so far.

    Regarding the USB-JTAG, if you did need it, then it is quite hard to make that cable due to the size. However it is available with other dev-boards sometimes, e.g. I'm sure I've received one with a TI dev-board in the past. There is a very low-cost one here which looks like it might fit (I have not tried it so I can't be sure): ARM-JTAG-20-10ARM-JTAG-20-10

  • 0 in reply to shabaz

    The bricking issue is with the OpenSDA v2.1 that gets corrupted when plugging it into a windows 10 pc.  Here is the link to the issue https://community.nxp.com/docs/DOC-330935  I had plugged my board into the pc before the issue was known and now it appears dead. 

     

    I was researching the ulink2 on ebay a bit more and it says it supposts 10pin 1.27mm pitch so I think I may just have to buy a cable for it If it doesn't the adapter you suggested looks like it will work I will probably end up buying this tool as I believe it would be useful for other boards

     

    I also seen an article about using a second board to reprogram the bricked one https://mcuoneclipse.com/2016/06/26/how-to-recover-the-opensda-v2-x-bootloader/    I was thinking I would try that as I do have a second K82f board, but I'm a little paranoid about bricking that too and being out 2 boards.

     

    I don't have a lot of experience with bootloaders,  Thats why I think the tool from ebay would be the best choice, I would just hate to spend the money if it wouldn't work.

     

    Thanks.

  • 0 in reply to cybermah

    Hi Dana,

     

    I think it could be worth just trying your failed board on Windows 7 first just in case it works (because the bricking issue is rare according to the earlier link), if it is already bricked then no further harm can be done to it.

    Regarding the use of the second board, I don't think it would become bricked if you use Windows 7, because the issue seems related to Windows 10 only. After the bootloader is upgraded, then you can use Windows 10 safely from what I can tell from the mcuoneclipse.com link.

  • 0 in reply to shabaz

    Actually I meant to mention that I had tried it in a windows 7 pc and an ubuntu one.  The board wont show up at all.  Even though I can tell it is powered up.  I'm pretty confident that the bootloader is corrupted.  I had contacted NXP after it happened, and thats how I got the second board, I had told them what it was doing and they sent me a new board, I only had to pay for shipping, no other question asked.  Funny thing is when I first got the board, I was using it on a windows 7 pc and it worked fine.  It was only when I tried it in my laptop (windows 10) that it stopped working.  Then when I put it back in the windows 7 pc it wouldn't work anymore.  After a couple of weeks of frigging around with it, the windows 10 issue showed up on a couple of forums.

     

    If it isn't possible for to repair the bootloader, I know I can still program the board by loading the bin using the mcu debug port instead. So that's why I either need to buy the tool or use the second board as a bootloader.

     

    With the second board, It will work with windows 10 now because I was able to upload the new bootloader before corrupting it on my windows 10 pc (lesson learned on the first board). 

Reply
  • 0 in reply to shabaz

    Actually I meant to mention that I had tried it in a windows 7 pc and an ubuntu one.  The board wont show up at all.  Even though I can tell it is powered up.  I'm pretty confident that the bootloader is corrupted.  I had contacted NXP after it happened, and thats how I got the second board, I had told them what it was doing and they sent me a new board, I only had to pay for shipping, no other question asked.  Funny thing is when I first got the board, I was using it on a windows 7 pc and it worked fine.  It was only when I tried it in my laptop (windows 10) that it stopped working.  Then when I put it back in the windows 7 pc it wouldn't work anymore.  After a couple of weeks of frigging around with it, the windows 10 issue showed up on a couple of forums.

     

    If it isn't possible for to repair the bootloader, I know I can still program the board by loading the bin using the mcu debug port instead. So that's why I either need to buy the tool or use the second board as a bootloader.

     

    With the second board, It will work with windows 10 now because I was able to upload the new bootloader before corrupting it on my windows 10 pc (lesson learned on the first board). 

Children
No Data