casaroli opened a new pull request, #21388:
URL: https://github.com/apache/nuttx/pull/21388

   ## Summary
   
   Since the merge of apache/nuttx-apps#3936 and #3953, two configurations do 
not link, and the CI jobs Linux (arm-imx) and Linux (arm64-01) fail for every 
PR:
   
   ```
   verdin-mx8mp:rpmsg:   arm-none-eabi-ld: region `flash' overflowed by 16 bytes
   imx93-evk:bootloader: aarch64-none-elf-ld: region `ocram' overflowed by 408 
bytes
   ```
   
   - **boards/verdin-mx8mp: Disable ramtest in rpmsg to fit the ITCM.** The 
code and data filled the 128 KiB ITCM up to 8 bytes, and #3953 adds 16 bytes to 
nshlib.
   - **boards/imx93-evk: Disable ostest in bootloader to fit OCRAM.** #3936 and 
#3953 add 400 bytes of text. The text then crosses a 4 KiB boundary, and 
`.rodata` (aligned to 4 KiB in ocramboot.ld) moves up by 4 KiB. 0bbe9f802b4 
disabled getprime for the same reason. Without ostest the text is 77 KiB 
smaller, so the next additions fit too.
   
   ## Impact
   
   Only these two configurations: verdin-mx8mp:rpmsg has no `ramtest` command, 
and imx93-evk:bootloader has no `ostest` command. No code change, no 
documentation change.
   
   ## Testing
   
   nuttx master 35452445223, nuttx-apps master, with the GNU toolchains of the 
CI (arm-none-eabi and aarch64-none-elf 13.2.Rel1):
   
   | Configuration | master | this PR |
   | --- | --- | --- |
   | verdin-mx8mp:rpmsg | region `flash` overflowed by 16 bytes | links, text 
127344 + data 1224 bytes, 2504 bytes of the ITCM free |
   | imx93-evk:bootloader | region `ocram` overflowed by 408 bytes | links, 
text 203500 bytes |
   
   With nuttx-apps before #3953 (4d36a6d56^), verdin-mx8mp:rpmsg links with 8 
bytes free. Both defconfigs are normalized (`make savedefconfig` gives the same 
file). `tools/checkpatch.sh -c -u -m -g` passes.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to