This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM0C1104-Q1: XDS110 debug fails when Segger works - 8 byte flash issue

Part Number: MSPM0C1104-Q1

I customized my linker, and have a section of 4 bytes.  Segger Jlink is able to flash my image and I can debug fine.  I attempted an XDS110, but it fails on the 4byte block since it's not a multiple of 8.  Is this a limitation of the xds110, or is there a setting to make it flash the entire image instead of block by block?

  • Hi Thomas,

    These devices are programmed based on a minimum Flash word size. The minimum Flash word size for this device is 8-bytes, and the Flash loaders used by the XDS110 expect code alignment if 8-bytes. This is not modifiable, but you can specify in the linker to fill gaps between sections or manually modify the output file to do the same.

    Best Regards,
    Brian

  • I have a 4 byte section followed by another section, no gaps.   Segger is able to load and flash without issue, so it's able to flash by the 8 bytes, the 4 byte section, and 4 bytes of the next section.  XDS is not smart enough to do the same, and there is no work around?

  • Hi Thomas,

    The workarounds I can think of would be to either push the adjacent section by 4 bytes to create give the initial section a full 8 bytes, or to combine the two sections into one. Our software team member responsible for our device support packages is currently out of office, but I will confer with them to determine if there may be something else, I am missing.

    Best Regards,
    Brian

  • Thanks, I could adjust, but that is not ideal, and I would not use the XDS110 pod if that is the case.  I will wait for further clarification from your team member to see if there are other options.