What would happen if using the recently released Programmer app from nRF Connect v 2.6.1 for PC, you accidentally erase all de contain inside the Device Memory Layout window? Would this nRF5280 DK board boot as it was doing before, that is, with a shinning LED5 and LED1 ? Could this be the reason why suddenly my board is no longer being recognized by my PC nor leds lit when the board is connected to the USB interface (although LED5 still lits intermittently if I enter the bootloader mode)?. And finally. Should I assume that my board has gone for good, or there is a way to recover its previous functionality? Thanks for your time and comprehension with a newbie fellow.
Have you done any modifications to your board? Cut some solder bridges?
Hi Andreas. No, I didn't modify the board. The only thing I've done after initial setup working fine was, installing some additional tools to the basic toolchain and by doing so, maybe some sw conflicts could have arisen (?). Let me summarize the process. I am working in a 64bit windows10 machine but since in the "Nordic Tools and Downloads link", the nRFx Command Line Tools are only offered in a 32bit version, I did install this version. The board was being recognized and all leds were working as described in Nordics documentation. Then, using nRF Connect>Programmer, I accidentally erased de device memory layout content, but at the moment, I didn't notice any problem in the board. Later on, I continue trying to install the SDK and run the Keil MDK installer thinking it was mandatory to install the SDK. Then, I tried to program S140 SoftDevice through SES but since I couldn't, I tried with nRFgo Studio. Again I couldn't. Then I entered the Segger site and loaded J-Link v635g just in case. Then I realized that SDK was a library and wasn't to be installed but simply to be declared in the windows path. Finally, and following recommendations, I moved the SDK directory to C:>Nordic>SDK. All I remember is that installing some of those features, I got some dialogue windows stating that the installation had failed because some 32/64 bit incompatibility with already installed sw had been found. It was the next day when I reboot the PC that I noticed the board was apparently dead (although as I mentioned, LED5 intermittently lits is I enter the bootloader mode). Off course an ESD shock could have always arisen, but this would be too much unlucky. Anyhow. Before I order a new board, I would appreciate your valuable opinion. Learning on your own is a sticky road. Thanks so much.
p143 said:(although as I mentioned, LED5 intermittently lits is I enter the bootloader mode).
This is because the J-link driver on your PC is not able to communicate with the Segger chip, not that the board is in bootloader mode
p143 said:I am working in a 64bit windows10 machine but since in the "Nordic Tools and Downloads link", the nRFx Command Line Tools are only offered in a 32bit version, I did install this version.
We have a 64bit version, you can find it here. Can you delete the 32 bit version you have installed, and install the 64 bit version?
Hi Andreas. I installed the 64bit version and reinitiated my PC but unfortunately, nothing has changed. The Windows Device Manager does not even notice when I connect/disconnect the board to the USB interface.
I said LED5 only lits in bootloader mode because it only happens when I switch on SW8 and press SW5.