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

[feature] st-util: Add specialized memory map for STM32H7 devices #1060

Merged
merged 1 commit into from
Nov 6, 2020
Merged

[feature] st-util: Add specialized memory map for STM32H7 devices #1060

merged 1 commit into from
Nov 6, 2020

Conversation

cmdrf
Copy link
Contributor

@cmdrf cmdrf commented Oct 26, 2020

Add a special memory map for STM32H742, STM32H743/753 and STM32H750 (at least). It includes the additional SRAM regions in these chips.

Data taken from linker script generated for H750 by CubeMX software and verified against table 7 of reference manual RM0433 (except for option byte area, which is not documented):

MEMORY
{
DTCMRAM (xrw)      : ORIGIN = 0x20000000, LENGTH = 128K
RAM_D1 (xrw)      : ORIGIN = 0x24000000, LENGTH = 512K
RAM_D2 (xrw)      : ORIGIN = 0x30000000, LENGTH = 288K
RAM_D3 (xrw)      : ORIGIN = 0x38000000, LENGTH = 64K
ITCMRAM (xrw)      : ORIGIN = 0x00000000, LENGTH = 64K
FLASH (rx)      : ORIGIN = 0x8000000, LENGTH = 128K
}

@cmdrf
Copy link
Contributor Author

cmdrf commented Oct 26, 2020

Looking at 1e20921#diff-44941250a4c135836a4d4d41b9c21282b90e379111bcb9fbab698d66e99872ba I think I might have the option bytes wrong...

@Nightwalker-87
Copy link
Member

Please verify that your patch applies to the specs and update it by pushing another commit if necessary.

@Nightwalker-87 Nightwalker-87 added this to the v1.6.2 milestone Oct 26, 2020
@Nightwalker-87 Nightwalker-87 changed the title st-util: Add specialized memory map for STM32H7 devices [feature] st-util: Add specialized memory map for STM32H7 devices Oct 26, 2020
@cmdrf
Copy link
Contributor Author

cmdrf commented Oct 28, 2020

Updated and confirmed against the manual.

@cmdrf
Copy link
Contributor Author

cmdrf commented Oct 28, 2020

Noo, something else is wrong now:

Overlapping regions in memory map: ignoring

Is it overlapping with the peripheral registers?

@cmdrf
Copy link
Contributor Author

cmdrf commented Oct 28, 2020

I checked the peripheral registers in the manual, and it's correct (except that the length is off by one, but that's the same in all other memory maps, too). So it seems a separate option byte area is not required at all.

@Nightwalker-87 Nightwalker-87 merged commit 835b496 into stlink-org:develop Nov 6, 2020
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Dec 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants