I think I bricked my Renesas FRB-R9A02G021 with J-Flash Lite

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • I think I bricked my Renesas FRB-R9A02G021 with J-Flash Lite

      I have a Renesas FRB-R9A02G021 (renesas.com/en/products/microc…cu-fast-prototyping-board). It came with J-Link OB.

      On connecting to my computer, J-Flash said it needed to upgrade the J-Link OB. It took a couple of attempts, but I managed to get this done.

      I compiled a test application that blinked an LED, and then flashed it using J-Flash Lite. This was successful.

      I recompiled my test application, and I cannot flash it - I get errors from J-Link.

      I tried the UART Bootloader, and that cannot flash the device either - you get an error that Renesas tells me implies the device has been locked against further programming.

      When you run J-Flash Lite, it offers three memory regions. The middle one is unticked by default, and I might have ticked it (I don't recall). But, if I *had* ticked it, and that memory region was not in my .hex file, would J-Flash Lite have erased this area and left it at all-1s, or would it have written all-0s? I ask, because it's the Flash Configuration region and writing 0 to the first word will disable all programming, as appears to have occurred.
    • Hello,

      Flash Lite only erases sectors that are included in the data file being programmed.
      If you have enabled config flash but it is not included in your .hex file, Flash Lite will not erase or program this flash when you press the Programming button.

      However, if you click "Erase Chip," the config flash will be completely erased regardless of whether it is included in your .hex file.

      >> would J-Flash Lite have erased this area and left it at all-1s, or would it have written all-0s? I ask
      When the area is erased by J-Flash, it will be left with all 0xFF, assuming that this is the erased value of the flash.

      Best regards,
      Simon
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/

      Or you can contact us via e-mail.