[SOLVED] GDB Server (v5.02a) LPC11A12 device map issue

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

  • [SOLVED] GDB Server (v5.02a) LPC11A12 device map issue

    Just a quick post to help anyone in the future who comes across this bug - after a day of tearing hair out over trying to figure out why enabling some code would cause the device to not load whatsoever, I spotted the error in the log output of the GDB Server:
    ERROR: Failed to erase sectors 3 @ address 0x00003000 (Algo124: Invalid sector)


    It turns out the LPC11A12/101 device map is only configured for 12kb, not the full 16kb flash.

    Instead, reconfigure for the LPC11A12/201 (a non-existent device, or at least not listed in UM10527) and writes to the final 4kb flash then work!
    Downloading 200 bytes @ address 0x00003000

  • Hi,

    Thank you for your investigation. Will be checked & fixed in the next official version.


    Best regards
    Erik
    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.

  • It turns out the LPC11A12/101 device map is only configured for 12kb, not the full 16kb flash.
    This is not correct. The flash of the device is configured as 4x4KB sectors == 16 KB. We have noticed, that you do not use the latest version of the J-Link software package. There was a bug in the flash controller which requires to perform some special handling to erase / program the last sector successfully. We have added this special handling in later versions. Can you please give the latest version V5.03d a quick try and check if the issue is solved?

    The version is available for download here: segger.com/jlink-software-beta-version.html

    (a non-existent device, or at least not listed in UM10527)
    The work-around is working by chance. The non-existent device has been added on demand from NXP. It is some kind of preliminary device. We will make sure that it is no longer listed in the public device selection dialog.


    Best regards
    Erik
    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.

  • We have just released V5.03e in which the device names have been changed.
    Can you please give the version a quick try and provide feedback?

    Best regards
    Erik
    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.