开云体育

Hi,
I got this:

.....
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: build/ch.elf section `.data' will not fit in region `flash0'
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: region `flash0' overflowed by 208 bytes
collect2: error: ld returned 1 exit status
make: *** [ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:243: build/ch.elf] Error 1


$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (15:7-2018-q2-6+b1) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]

How could I fix it?

Many thanks

Lapo

Well, if this is only for your own personal use, I would suggest you can begin removing all the help text and associated code, incuding the info text.??
Afterall, you already know how to use the commands, right???
... Larry



On Wed, 4 Dec 2019 at 6:50 PM, Lapo Pieri<ik5nax@...> wrote: Hi,
I got this:

.....
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: build/ch.elf section `.data' will not fit in region `flash0'
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: region `flash0' overflowed by 208 bytes
collect2: error: ld returned 1 exit status
make: *** [ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:243: build/ch.elf] Error 1


$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (15:7-2018-q2-6+b1) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]

How could I fix it?

Many thanks

Lapo

I tested it on arm-none-eabi-gcc (15:4.9.3+svn231177-1) 4.9.3 20150529 (prerelease)

The latest github version can fit into memory with all commands enabled, just out of the repository.

01:10 Thu 05 Dec 19 , Larry Rothman wrote:

Well, if this is only for your own personal use, I would suggest you can begin removing all the help text and associated code, incuding the info text.??

I've to figure out how to remove that part of code

Afterall, you already know how to use the commands, right???

Is there a sort of code configuration to issue before compiling?

Thanks

Lapo

23:17 Wed 04 Dec 19 , QRP RX wrote:

I tested it on arm-none-eabi-gcc (15:4.9.3+svn231177-1) 4.9.3 20150529 (prerelease)

Mine is newer (from debian unstable) and probabily has some different
default compiling/linking options, this has happened several times in gcc
history... Or maybe some compiling strategies has changed... I'm not an
expert

The latest github version can fit into memory with all commands enabled, just out of the repository.

I take it yesterday from the repo but non luck.

I've tried to substitute -O2 with -Os but fw start, show start and stop freq
and a whole black screen, no more.

I'll study it a bit

Thank you!

Lapo

I personally have not tried to compile the code but it logical that if you remove most of the help text, you will free up code space.?
Maybe QRP could create a 'help-free' version to be used primarily with NanoVNA Saver and other PC apps so the freed-up space could be used for newer features??? :-)



On Thu, 5 Dec 2019 at 4:29 PM, Lapo Pieri<ik5nax@...> wrote: 01:10 Thu 05 Dec 19? , Larry Rothman wrote:

Well, if this is only for your own personal use, I would suggest you can begin removing all the help text and associated code, incuding the info text.??

I've to figure out how to remove that part of code

Afterall, you already know how to use the commands, right???

Is there a sort of code configuration to issue before compiling?

Thanks

Lapo

On Thu, Dec 5, 2019 at 11:29 PM, Lapo Pieri wrote:

Is there a sort of code configuration to issue before compiling?

You can comment lines 28-30 in the file nanovna.h to enable/disable support for scanraw and color command. It will reduce memory usage.

I just installed arm-none-eabi-gcc with apt-get install on my old Ubuntu machine and it can compile code from repository with no needs for any change.

Here is screenshot:

just tried to clone it from scratch and compile - compiled okay with no errors.

Clone and compile sequence is the following:

$ git clone
$ cd NanoVNA-Q/
$ git submodule update --init --recursive
$ make