[runout]

also to keep in mind:
the Project was imported by the VGDB-Wizard from a Keil-Source…

[runout]

I’ve imported the project again via gpdsc-file.
Now it runs fine.

Kind regards

[runout]

OK, thanks for your advice.
Do I absolutely need the “Custom or higher” – Version?
Is it possible to tweak the BSP_ROOT variable?
(in “FindBSP.props” e.g.)

Kind Regards

[runout]

Hi,

no chance to find the mentioned button
Where is the default clang-style-format located?

Please a little nudge…

Attachments:

You must be logged in to view attached files.

[runout]

Hi,

thank for your reply.
The problem is meanwhile solved.

The differences of the Linker-Scripts and the startup_xxx.c are significant.
There are no differences of system_xxx.c between Simplicity-Studio and VGDB.

In the Simplicity-Linker-Scripts are sections like text_apploader, text_application.
This is neccesary for converting ELF/AXF-File via objcopy and Commander.exe (from Silabs) to *.gbl-files

I use “fixed heap & Stack”-Option.
_sbrk() was defined double:  in StackAndHeap.c  (VGDB) and retargetio.c (Simplicity-Studio)

Anyway, it is possible to switch from Simplicity-Studio/Eclipse 🙁 to VGDB :-).

last question:
How to avoid this Message? “The memory location used for the Stack is not writable… You can disable automatic stack checking via…”
Have no found any Option.
maybe: Preprocessor-Macros: “__StackLimit=0x20000000” ???

Kind Regards

 

 

 

 

 

 

• This reply was modified 5 years, 1 month ago by runout.

Attachments:

You must be logged in to view attached files.

[runout]

Hi does it mean, a ELF-File is exactly the same as a AXF-File?

that (gcc)-linker options generate a “real” axf-File: (by Silabs Simplicity-Studio)
-g -gdwarf-2 -mcpu=cortex-m4 -mthumb -T “${workspace_loc:/${ProjName}/efr32bg13p632f512gm48.ld}” -Xlinker –gc-sections -Xlinker -Map=”${BuildArtifactFileBaseName}.map” -mfpu=fpv4-sp-d16 -mfloat-abi=softfp –specs=nano.specs

that (gcc)-linker options generate a elf-File: (w/o extension) in Visual GDB
-o “C:\xxx\EmBGM13P22F512GA_Test01\VisualGDB\Debug\EmBGM13P22F512GA_Test01″ -Wl,-gc-sections -L”Stack/platform/radio/rail_lib/autogen/librail_release” -L”Stack/protocol/bluetooth/lib/EFR32BG13P/GCC” -l”rail_efr32xg13_gcc_release” -l”bluetooth” -l”mbedtls” -l”psstore”

btw:
in VisualStudio/VGDB it’s very simple to extend the elf-file Name.
In “Properties” (Alt+Enter) /General/Target Extension (normally empty) set to “.axf”

BUT, this is not the Solution to the Issue descripted above.
Is it related to Parameter “-g -gdwarf-2” ??

I need “real” axf-Files as input for the Silabs Converting-Tool
to generate gbl-Files.

Kind Regards

 

[runout]

Hi,

thanks for your advice.
A quick solution helps (in my case):
“Reset Windows Layout”
Windows: ALT + W, R

Do you plan to release a “major version” (e.g. 5.5) next time? (with version history…)

Kind Regards
Runout

[runout]

another attachment

Attachments:

You must be logged in to view attached files.

[runout]

Edit: Problem solved (Name-Convention)
<lib>LibName<.a> is the required format (at least at Arm-GCC)

 

[runout]

Hi,

you’ve seen my attachment?

An Entry in “Additional Linker Inputs” also not works.

The Raw-Name of the Lib is “BIQ_CM4_GCC.a” (not libBIQ_CM4_GCC.a)
Maybe a Issue with the name conventions?

Is there a Visual-GDB-Menu for setup the Linker Options?
(verbose e.g.)

Kind regards
Thomas

 

[Author]

Posts