Avoid truncating .isr_table from custom linker section on LPC176X #6633

0x6d61726b · 2018-04-13T10:43:19Z

Description

Type: Bug | Question
Priority: Major

Bug / Question

Target
LPC176X

Toolchain:
GCC_ARM (GNUARM)

Expected behavior
Custom ".isr" section shall be present in output .hex file

Actual behavior
Custom ".isr" section is missing in output .hex file

Steps to reproduce
0. Compile and link the project with an unmodified .ld file from /targets/TARGET_NXP/TARGET_LPC176X/device/TOOLCHAIN_GCC_ARM/LPC1768.ld

Modify the linker file to place the ".isr_vector" into a custom ".isr" section (LPC1768_isr.ld)
Compile and link the project with modified LPC1768_isr.ld file
List and compare the section headers of both .elf files with: arm-eabi-readelf -S .elf

   Relevant entry of unmodified sections:
   Section Headers:
     [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
     [ 0]                   NULL            00000000 000000 000000 00      0   0  0
     [ 1] .text             PROGBITS        00000000 010000 00f530 00  AX  0   0  8

   Relevant entry of modified sections:
   Section Headers:
     [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
     [ 0]                   NULL            00000000 000000 000000 00      0   0  0
     [ 1] .isr              PROGBITS        00000000 0202e4 0000cc 00      0   0  4
     [ 2] .text             PROGBITS        00002000 002000 00f460 00  AX  0   0  8
   .hex file content:
     Block  0  Starts at: 0x2000  Ends at: 0x11683 (Length: 0xF684=63108)
     00002000:  10 B5 05 4C  23 78 33 B9   04 4B 13 B1  04 48 AF F3  ...L#x3..K...H..
     00002010:  00 80 01 23  23 70 10 BD   E8 02 00 10  00 00 00 00  ...##p..........
     00002020:  5C 14 01 00  08 4B 10 B5   1B B1 08 49  08 48 AF F3  \....K.....I.H..
     00002030:  00 80 08 48  03 68 03 B9   10 BD 07 4B  00 2B FB D0  ...H.h.....K.+..
     00002040:  BD E8 10 40  18 47 00 BF   00 00 00 00  EC 02 00 10  [email protected]..........
     00002050:  5C 14 01 00  E4 02 00 10   00 00 00 00  15 4B 00 2B  \............K.+

Patch the startup file and assign the ".isr_vector" the section attribute "allocated" in file /targets/TARGET_NXP/TARGET_LPC176X/device/TOOLCHAIN_GCC_ARM/startup_LPC17xx.S

   63c63
   <     .section .isr_vector
   ---
   >     .section .isr_vector,"a"

List the section headers of the patched version with the modified LPC1768_isr.ld file

   Section Headers:
     [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
     [ 0]                   NULL            00000000 000000 000000 00      0   0  0
     [ 1] .isr              PROGBITS        00000000 010000 0000cc 00   A  0   0  4
     [ 2] .text             PROGBITS        00002000 012000 00f460 00  AX  0   0  8
   .hex file content:
     Block  0  Starts at: 0x   0  Ends at: 0x  CB (Length: 0xCC=204)
     Block  1  Starts at: 0x2000  Ends at: 0x11683 (Length: 0xF684=63108)
     00000000:  E0 7F 00 10  55 A6 00 00   85 A6 00 00  87 A6 00 00  . ..U...........
     00000010:  89 A6 00 00  8B A6 00 00   8D A6 00 00  00 00 00 00  ................
     00000020:  00 00 00 00  00 00 00 00   00 00 00 00  45 C5 00 00  ............E...
     00000030:  91 A6 00 00  00 00 00 00   AF C5 00 00  E5 C5 00 00  ................
     00000040:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     00000050:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     00000060:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     00000070:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     00000080:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     00000090:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     000000A0:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     000000B0:  97 A6 00 00  97 A6 00 00   97 A6 00 00  97 A6 00 00  ................
     000000C0:  97 A6 00 00  97 A6 00 00   97 A6 00 00               ............    
     00002000:  10 B5 05 4C  23 78 33 B9   04 4B 13 B1  04 48 AF F3  ...L#x3..K...H..
     00002010:  00 80 01 23  23 70 10 BD   E8 02 00 10  00 00 00 00  ...##p..........
     00002020:  5C 14 01 00  08 4B 10 B5   1B B1 08 49  08 48 AF F3  \....K.....I.H..
     00002030:  00 80 08 48  03 68 03 B9   10 BD 07 4B  00 2B FB D0  ...H.h.....K.+..
     00002040:  BD E8 10 40  18 47 00 BF   00 00 00 00  EC 02 00 10  [email protected]..........
     00002050:  5C 14 01 00  E4 02 00 10   00 00 00 00  15 4B 00 2B  \............K.+

Question

Is there a way to define the "allocated" section attribute in the linker file?
Is it a suitable way to extend mbed-os LPC17xx.S startup file to avoid this bug?

The text was updated successfully, but these errors were encountered:

0x6d61726b · 2018-04-13T10:46:46Z

Sorry for the bad formatting, but Firefox ESR is not supported any longer by github which seems to result in non-available java-script stuff
[Mirrored to Jira]

0xc0170 · 2018-04-13T10:53:47Z

I reformatted a bit the above.

I don't think we do any magic there that would stop you from editing linker file + startup file. So rather this looks like its error in the implementation than tools.

Custom ".isr" section is missing in output .hex file

I might need some details to understand the problem (lot of numbers in the pasted data). .isr is the default one. isr_vector is the one you define in the linker file but does not get to the output file ?

[Mirrored to Jira]

0x6d61726b · 2018-04-13T10:54:19Z

If you ask why the custom .isr section was introduced in the .ld file, the question is simple:
We want to use the small 4K flash sectors to store arbitrary data and not the large 32K sectors that are located at the end of the flash. Unfortunately those sectors are located at the beginning of the flash (sectors 0 to 15).

here is an excerpt of the modified linker file:

/* Linker script for mbed LPC1768 */

/* Linker script to configure memory regions. */
MEMORY
{
  ISR    (rx)  : ORIGIN = 0x00000000, LENGTH = 4K                 /* ISR table, CRP */
  FLASH  (rx)  : ORIGIN = 0x00002000, LENGTH = (512K - 8K)        /* generic flash flash */
  RAM    (rwx) : ORIGIN = 0x100000C8, LENGTH = (32K - 0xC8 - 32)  /* topmost 32 bytes used by IAP functions */

  USB_RAM(rwx) : ORIGIN = 0x2007C000, LENGTH = 16K
  ETH_RAM(rwx) : ORIGIN = 0x20080000, LENGTH = 16K
}
...
SECTIONS
{
    .isr :
    {
        KEEP(*(.isr_vector))
    } > ISR
       
    .text :
    {
        *(.text*)
        KEEP(*(.init))
        KEEP(*(.fini))
...

[Mirrored to Jira]

0x6d61726b · 2018-04-13T10:56:37Z

As far as we found out, the sections not marked with the flag "Flg" "A" are truncated from the output .hex file.
[Mirrored to Jira]

0x6d61726b · 2018-04-13T11:03:16Z

Additional information can be found here:
https://sourceware.org/binutils/docs/as/Section.html

If other sections are placed into the ".isr" section like the ".init" section, the ".isr" section automatically gets marked with the flags "Flg" "AX" for "allocated" and "executable".
[Mirrored to Jira]

0x6d61726b · 2018-04-13T11:22:53Z

isr_vector is the one you define in the linker file but does not get to the output file ?

The ".isr_vector" is also present in the original LPC1768.ld file but in the .text section. I have created a new memory location "ISR" and just moved the ".isr_vector" into it. All remaining sections are kept in the ".text" section which is located in the memory "FLASH".
[Mirrored to Jira]

0xc0170 · 2018-04-16T07:41:54Z

The ".isr_vector" is also present in the original LPC1768.ld file but in the .text section. I have created a new memory location "ISR" and just moved the ".isr_vector" into it. All remaining sections are kept in the ".text" section which is located in the memory "FLASH".

The issue resolved ?
[Mirrored to Jira]

0x6d61726b · 2018-04-16T07:49:46Z

The issue resolved ?

Not by default. It can be resolved, if the section is marked with the "a" (=allocated) flag in source code, as described in item #4 of the the initial post (.section .isr_vector,"a").
[Mirrored to Jira]

0xc0170 · 2018-04-16T08:22:17Z

Yes, that is correct. I recall having exact same problem when I was porting sometargets to GCC baremetal. If you review some of the startup files, they do .section .isr_vector, "a"

This should be fixed. Can you send PR please?
[Mirrored to Jira]

0x6d61726b · 2018-04-17T10:44:21Z

Thanks for the feedback.
I can do the PR, but please give me a few days since I am pretty busy right now.
[Mirrored to Jira]

0xc0170 · 2018-08-01T13:31:33Z

I can do the PR, but please give me a few days since I am pretty busy right now.

@0x6d61726b Any update ?
[Mirrored to Jira]

adbridge · 2018-10-04T12:19:15Z

Internal Jira reference: https://jira.arm.com/browse/IOTPART-6051

maclobdell · 2019-01-15T16:15:40Z

@0x6d61726b Thanks for reporting this and offering to do a PR. What is the status? Have you made a PR?

0x6d61726b · 2019-05-30T08:45:19Z

I have written a small tool that modified all files that did not yet contain the "allocated" flag for the .isr_vector section. Sorry for the delay. I have committed, but not pushed the changes (I did the changes now to the latest master branch).

ciarmcom · 2019-10-31T16:57:10Z

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.

0xc0170 added the type: question label Apr 13, 2018

ciarmcom added the mirrored label Jun 1, 2018

ARMmbed deleted a comment from ciarmcom Oct 2, 2018

adbridge added the Jira status: OPEN label Oct 2, 2018

adbridge removed the type: question label Oct 25, 2019

ciarmcom closed this as completed Oct 31, 2019

ciarmcom added Jira status: CLOSED and removed Jira status: OPEN labels Oct 31, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Avoid truncating .isr_table from custom linker section on LPC176X #6633

Avoid truncating .isr_table from custom linker section on LPC176X #6633

0x6d61726b commented Apr 13, 2018 •

edited by 0xc0170

Loading

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

Uh oh!

0xc0170 commented Apr 13, 2018 •

edited by adbridge

Loading

Uh oh!

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

Uh oh!

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

Uh oh!

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

Uh oh!

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

Uh oh!

0xc0170 commented Apr 16, 2018 •

edited by adbridge

Loading

Uh oh!

0x6d61726b commented Apr 16, 2018 •

edited by adbridge

Loading

Uh oh!

0xc0170 commented Apr 16, 2018 •

edited by adbridge

Loading

Uh oh!

0x6d61726b commented Apr 17, 2018 •

edited by adbridge

Loading

Uh oh!

0xc0170 commented Aug 1, 2018 •

edited by adbridge

Loading

Uh oh!

adbridge commented Oct 4, 2018

Uh oh!

maclobdell commented Jan 15, 2019

Uh oh!

0x6d61726b commented May 30, 2019

Uh oh!

ciarmcom commented Oct 31, 2019

Uh oh!

Avoid truncating .isr_table from custom linker section on LPC176X #6633

Avoid truncating .isr_table from custom linker section on LPC176X #6633

Comments

0x6d61726b commented Apr 13, 2018 • edited by 0xc0170 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Bug / Question

Question

0x6d61726b commented Apr 13, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0xc0170 commented Apr 13, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0x6d61726b commented Apr 13, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0x6d61726b commented Apr 13, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0x6d61726b commented Apr 13, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0x6d61726b commented Apr 13, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0xc0170 commented Apr 16, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0x6d61726b commented Apr 16, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0xc0170 commented Apr 16, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0x6d61726b commented Apr 17, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

0xc0170 commented Aug 1, 2018 • edited by adbridge Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adbridge commented Oct 4, 2018

Uh oh!

maclobdell commented Jan 15, 2019

Uh oh!

0x6d61726b commented May 30, 2019

Uh oh!

ciarmcom commented Oct 31, 2019

Uh oh!

0x6d61726b commented Apr 13, 2018 •

edited by 0xc0170

Loading

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

0xc0170 commented Apr 13, 2018 •

edited by adbridge

Loading

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

0x6d61726b commented Apr 13, 2018 •

edited by adbridge

Loading

0xc0170 commented Apr 16, 2018 •

edited by adbridge

Loading

0x6d61726b commented Apr 16, 2018 •

edited by adbridge

Loading

0xc0170 commented Apr 16, 2018 •

edited by adbridge

Loading

0x6d61726b commented Apr 17, 2018 •

edited by adbridge

Loading

0xc0170 commented Aug 1, 2018 •

edited by adbridge

Loading