Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory.x contains incorrect FLASH : ORIGIN value #55

Closed
Erich-McMillan opened this issue Oct 27, 2018 · 3 comments
Closed

memory.x contains incorrect FLASH : ORIGIN value #55

Erich-McMillan opened this issue Oct 27, 2018 · 3 comments

Comments

@Erich-McMillan
Copy link

MEMORY
{
/* NOTE 1 K = 1 KiBi = 1024 bytes /
/
TODO Adjust these memory regions to match your device memory layout /
/
These values correspond to the LM3S6965, one of the few devices QEMU can emulate */
FLASH : ORIGIN = 0x00000000, LENGTH = 256K <- Value in source code
RAM : ORIGIN = 0x20000000, LENGTH = 40K
}

but had to change to

MEMORY
{
/* NOTE 1 K = 1 KiBi = 1024 bytes /
/
TODO Adjust these memory regions to match your device memory layout /
/
These values correspond to the LM3S6965, one of the few devices QEMU can emulate */
FLASH : ORIGIN = 0x08000000, LENGTH = 256K
RAM : ORIGIN = 0x20000000, LENGTH = 40K
}

then I was able to load the code onto the microcontroller.

Using Rev C+ of the STM32f3xDiscovery board, but that shouldn't be an issue.

@therealprof
Copy link
Contributor

@WolfgangAM Please note the comment just above the line you've modified. This file is supposed to be adjusted to the MCU you're using and the values are correct for a different MCU.

@Erich-McMillan
Copy link
Author

True, but because the README uses STM32 board the defaults in the memory.x should correspond, especially since the default RAM : ORIGIN and LENGTH are set to this board's specific RAM settings.

@therealprof
Copy link
Contributor

@WolfgangAM Actually the README specifically tells you to adjust the file to your needs using the STM32F3DISCOVERY as an example. To be honest I'd have the file contain invalid data so any attempt to compile the file without modification will fail, since this is a step that should never be skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants