i.MX RT Crossover MCUsのトピックRe: Is there any expected problem when remove .ARM.exidx section?

Is there any expected problem when remove .ARM.exidx section?

GoodDay — Tue, 16 Apr 2024 05:26:29 GMT

With below conditions, size of binary file is so big which can not be used.

- MCUXpresso 11.6.0 [Build 8187] with SDK 2.10.0 (494)

- RT1052

- Newlibnano

- Link application to RAM

With Redlib or without "Link application to RAM", binary file can be normally generated.

At binary file, most of regions are filled with 0x00 and last line filled some data.

I checked address of last line and I found that it is .ARM.exidx.

When I make binary file after removing .ARM.exidx section, normal binary data is generated.

.ARM.exidx is included at libgcc.a(_udivmoddi4.o).

[Questions]

1. Can I remove .ARM.exidx section or move memory position of .ARM.exidx section to generate small binary file?

2. If 1st solution is impossible, is there any expected problem when remove .ARM.exidx section?

To generate proper size binary data, I need to remove .ARM.exidx section.

Thanks.

EdwinHz — Thu, 18 Apr 2024 20:49:19 GMT

If your project uses -fno-exceptions dialect flag, you should be able to remove .ARM.exidx section without issues. This can be done like this other post describes: Solved: How to allocate C++ code to ITCM - NXP Community.

BR,
Edwin.

GoodDay — Thu, 25 Apr 2024 00:04:43 GMT

I checked post which you recommend.

I try it but it can not solve the problem.

Please refer below.

.ARM.exidx section is not removed and I think not source codes but new library or new nano library has exception.

Because new nano library can not be compiled again and redlib has not this problem.

Thanks.