13022591351 commented on PR #19982: URL: https://github.com/apache/nuttx/pull/19982#issuecomment-5474797673
> @13022591351 please fix: > > ``` > ==================================================================================== > Configuration/Tool: imx93-evk/bootloader > 2026-08-29 14:07:43 > ------------------------------------------------------------------------------------ > Cleaning... > Configuring... > Building NuttX... > aarch64-none-elf-ld: /github/workspace/sources/nuttx/nuttx section `.rodata' will not fit in region `ocram' > aarch64-none-elf-ld: section .data LMA [00000000204e0000,00000000204e213f] overlaps section .rodata LMA [00000000204c7000,00000000204e033f] > aarch64-none-elf-ld: region `ocram' overflowed by 832 bytes > make[1]: *** [Makefile:194: nuttx] Error 1 > make: *** [tools/Unix.mk:572: nuttx] Error 2 > make: Target 'all' not remade because of errors. > ``` I investigated the imx93-evk/bootloader overflow locally. This configuration is primarily an EL3/AHAB, DDR-training, and NSH bring-up image. After excluding the WQ ostest, the link map contains no actual work_queue() or work_cancel() users; the custom queue lifecycle functions are also removed by --gc-sections. The current WQ changes add 736 bytes of .text, which moves the page-aligned vector table and .rodata forward by 4 KiB and causes the reported 832-byte OCRAM overflow. With the WQ test excluded, the complete bootloader build succeeds and OCRAM usage drops from 100.29% to 98.62%. Therefore, instead of expanding the board’s OCRAM layout, I suggest that the bootloader configuration should not enable work-queue functionality: # CONFIG_SCHED_HPWORK is not set # CONFIG_SCHED_LPWORK is not set No linked bootloader component currently depends on these queues, while WQ functionality remains covered by other configurations. If this direction is acceptable, I can update the defconfig and verify the complete build. -- 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]
