They can be used as long as they live, and we do nothing to shorten the life span. We do not purposely “brick” our own products. That is of course if you use our boot loader and not some hacked replacement boot loader. Firmware update can continue the next time. Our Firmware update is in fact “bullet proof”, in a sense that were a firmware update gets interrupted, LPC4322 (M4/M0) for J-Link Base and Plus and a FPGA (Zynq) with built-in Cortex-A9 for high end models (J-Link ULTRA+ / PRO). So newer J-Links do not use an STM32F7 CPU. Posted in Microcontrollers, Tool Hacks Tagged in-circuit debugger, j-link, segger, unbrick Post navigation This was not the end of the story, however, as after this the SEGGER software was unable to update the firmware on the device, due to a missing bootloader that was not part of the firmware image.ĭigging further into this, found out a whole host of fascinating details about not only these SEGGER J-Link devices, but also the many clones that are out there, as well as the interesting ways that SEGGER makes people buy new versions of their debug probes. This led to the interesting discovery that apparently the MCU’s Flash ROM had seemingly lost the firmware data.įortunately was able to flash back a version of the firmware which was available on the internet, allowing the J-Link device to work again. The Tag-Connect style JTAG header on the PCB appeared to be a good second stop, requiring only a bit of work to reverse-engineer the exact pinout and hook up an ST-Link V2 in-circuit debugger to talk with the STM32F205RC MCU on the PCB. This led to take the device apart to figure out what was wrong with it.Īfter checking voltages on the PCB, nothing obvious seemed wrong. This was awkward not only because in-circuit debuggers are vital pieces of equipment in embedded firmware development, but also because they’re not that cheap. Last year found themselves in the situation where a SEGGER J-link debug probe suddenly just stopped working.
0 Comments
Leave a Reply. |