[Ankan]

Never mind, I solved it.

My change to linker script was correct. I just had a bug in my code that broke it.

[Ankan]

Hi again,

1. Add a memory region for RAM1 or RAM2 if it’s not added already.
   Already added by default MCU SRAM1 (m_text) and SRAM2 (m_data) (See linked linking script above) https://sysprogs.com/w/forums/topic/add-more-flash-on-stm32mp157/#post-29847

2. Create a section that will be placed there. Make sure it’s not placed in the regular FLASH (see the Additional Memories tutorial).
   Sections for m_text and m_data is already created as default. (See linked linking script ) https://sysprogs.com/w/forums/topic/add-more-flash-on-stm32mp157/#post-29847
3. Use attributes to place parts of your program into the new section.
   m_text have a .text section that take all non-attribute-specified-code and put it there. Why is my solution above not working as it seams logic?

It’s good that you can offer your consulting services to solve this for us. But I don’t think it’s that unique as it’s only about how to use STM32MP1 with VisualGDB.

[Ankan]

Hi,

I have read both tutorials but don’t really understand how to apply this to my STM32MP157 processor.

My linker script look like this: https://github.com/STMicroelectronics/STM32CubeMP1/blob/master/Projects/STM32MP157C-DK2/Templates/SW4STM32/Templates/stm32mp15xx_m4.ld In other words it’s default linker script for stm32mp15xx processors.

As you can read here: https://wiki.st.com/stm32mpu/wiki/STM32MP15_RAM_mapping#Zoom_in_the_Cortex-A7-2FCortex-M4_shared_memory m_text and m_data are same kind of memory and can be tuned.

I tried to define memory like this:

MEMORY
{
m_interrupts (RX) : ORIGIN = 0x00000000, LENGTH = 0x00000298
m_text (RX) : ORIGIN = 0x10000000, LENGTH = 0x00030000
m_data (RW) : ORIGIN = 0x10030000, LENGTH = 0x00010000
m_ipc_shm (RW) : ORIGIN = 0x10040000, LENGTH = 0x00008000
}

It compiled but didn’t work.

What have I missed?

• This reply was modified 3 years, 10 months ago by Ankan.

[Ankan]

Does this mean that it’s not possible to use the so called RAM1 or RAM2 as FLASH?

What I understand it should be possible to customize the M4 memory mapping

https://wiki.st.com/stm32mpu/wiki/STM32MP15_RAM_mapping

[Ankan]

Thank you! It works much better.

[Ankan]

… more screenshots from the wizard.

Attachments:

You must be logged in to view attached files.

[Ankan]

I remove all toolchains and doublechecked that c:\SysGCC was deleted. I uninstalled VisualGDB, reboot computer and reinstalled VisualGDB 5.5 RC1. Then I reinstalled the STM32MP1 toolchain from inside the wizard but still same problem.

Then only thing that differ from the openstlinux image on the STM32MP1 is that I have installed g++, rsync, zip, openssh-server, make, sudo, cmake, ninja-build, git and gdb.

I get this /not/exist error even if my STM32MP1 is powered off so I don’t get it. It looks like the error lay in the toolchain, but I have reinstalled it over and over again. If I choose a different toolchain like raspberry or ubuntu I can sync without problem.

I have attached screenshots from the wizard.

Attachments:

You must be logged in to view attached files.

[Ankan]

If I change Cross-toolchain to for example ubuntu I can sync, but got lot of errors as it is a architecture mismatch. So I guess the problem lay in the STM32MP1 Cross-toolchain.

[Ankan]

I have created 10th of different projects and they all got same error. I even get this error when running the New Linux Project wizard, before the projects actually is created.

I have reinstalled VisualGDB and also the Cross-toolchain STM32MP1 multiple times without luck.

I ran VisualGDB 5.4r12 and is now trying 5.5rc1, but with no success.

Where should sysroot be set or where can I set it to see if that would help as I guess it’s not set?

[Author]

Posts