Posted by silvio.vallorani on 2016-03-13 12:38

Good morning all,
I’m very enthusiast STM32 user and love the System Workbench coz of all Open Source technologies, but I found a really limiting issue for my projects.

I need to partition the ROM area into sections and I does it using ld script.
I used 2 methods:
- (DP) Direct Partitioning: partitioning in memory definitions and placing of section at desired memory partition;
- (SA) Section Address: single flash partition and positioning of the sections at fixed addresses in section definitions.

I test using 3 nucleo boards: NUCLEO-F091RC, NUCLEO-F4303K8, NUCLEO-F411RE

I create 2 different partions for all the board and using the 2 methods above:
- (1-1-2-R) that means 1K + 1K + 2K + REST of ROM
- (6-2-16-R) that means 6K + 2K + 16K + REST of ROM

I test the builds using SystemWorkbench (SW) and ST-Link Utility (ST-L) for all the combinations.

RESULTS:
Compile  : ALL OK
Link  : ALL OK

DEBUG REPORT:

As you can see, I can’t debug in SystemWorkbench when using NUCLEO-F091RC and NUCLEO-F4303K8 in (6-2-16-R) partitioning mode, but I can normally debug when use the NUCLEO-F411RE.

I can Run, Halt, Step, Reset, etc... normally with all the 3 boards in all situations using ST-Link Utility.

Because of the dimensions I can’t attach it, but I link the zip file of the enteire workspace with the three projects and with all the sistuations mentioned above:
https://drive.google.com/open?id=0B9VxKVnIagPvZkJ2ZmdneG1xT00

In all projects there are 4 configurations and 4 linker scripts (one per configuration), at the very begin of every linker script there are detailed explanations of tools versions and memory partition used.

(The amap.exe included to simply navigate the map files is a Sergey Sikorskiy project and can be freely downloaded here: http://www.sikorskiy.net/prj/amap )

Hope this can help you guys to resolve this problem.

Best regards,

Silvio Vallorani.