-
Notifications
You must be signed in to change notification settings - Fork 3k
Update CMSIS pack index json for STM32H7xx family #11709
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Becoming hard to review (file too large), I got one unicorn earlier today for this file 🙄
Hi |
"access": { | ||
"execute": true, | ||
"non_secure": false, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove IROM2 part for H743, and double IROM1 size?
as it is a single core, and full ROM can be used.
"access": { | ||
"execute": true, | ||
"non_secure": false, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can we rename IROM1 into IROM_CM7 ?
and IROM2 into IROM_CM4 ?
@jeromecoutant - for the modifications here - all the information is coming from the cmsis-pack you have supplied to KEIL. Nothing is generated manually and if we start changing things manually, it means we must maintain this file manually forever. Which might or might not be something we really want. @jeromecoutant - in an ideal world, STM would re-generate the STM file, after which I would re-generate the CMSIS-pack to match. @MarceloSalazar @mark-edgeworth @bulislaw @kjbracey-arm @madchutney - we really need to think what exactly we need and where, as it seems to me have lots of duplicate information. Flash sectors and sizes are in the cmsis-packs (in this PR) AND the target files. Either one of them is a duplicate. We have some similar information also in the compiler linker/scatter files, too. Also, having one 13 MB JSON file also does not sound like a feasible plan going into the future, we should consider splitting the file into vendor parts (if we truly even need that one .JSON file) - too large files become unmanageable/hard to review. |
@JanneKiiskila: @ARMmbed/mbed-os-tools are looking at this right now... |
@jeromecoutant can you rereview? As data in this PR are coming from the pack, can we use these and once pack is fixed, it will be fixed as well. We would like to have this update on master as soon as possible.
Separation should help here, it will just grow in size day-by-day. |
I don't think these are duplicates. Not all drivers provide memory layout in the driver itself like the reference above (they could but there is no way we could get it writing one script without changes per each target family and its SDK). This information is in the cmsis packs - what we use, also what other tools use. This is standardized way to get this data. Regarding linker scripts - this is one of the things we would like to have - one linker file per toolchain and generate it per target. |
6325b3c
to
652a00d
Compare
Travis reports the device name is not valid:
|
652a00d
to
3f8c9e6
Compare
Oh yes, the device name for DISCO_H747I was still wrong - it's not On the other hand, I'd like to get this one merged in pretty soon - the problem is that the |
Manually replaced the existing STM32H7 section and replaced it with the context of updated `index.json` that pulled in the Keil packs available today, as of 18th October, 2019. See related PR; ARMmbed#11707
Compilation of bootloader requires these parameters.
Add definitions for H743ZI2, required by bootloader.
The proposed review fixes by Jerome, cherry-picked in. (cherry picked from commit fb15f02) Signed-off-by: Janne Kiiskila <[email protected]>
3f8c9e6
to
eed920e
Compare
"mbed_rom_start": "0x08000000", | ||
"mbed_rom_size" : "0x200000", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sorry, but in order to remove warnings,
we should also add (for both H743ZI and ZI2):
"mbed_ram_start": "0x24000000",
"mbed_ram_size" : "0x80000",
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which warnings? I don't recall seeing any?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, anyways.
Adding the RAM definitions per request of Jerome Coutant.
CI started |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
Failure seems to be related to exporter tests;
|
License error, restarting exporters |
Description
Manually replaced the existing STM32H7 section and replaced it with the
context of updated
index.json
that pulled in the Keil packs availabletoday, as of 18th October, 2019.
See related PR; #11707
Pull request type
Reviewers
@0xc0170 @ARMmbed/team-st-mcd @jeromecoutant
Release Notes
CMSIS pack index updated for STM32H7xx -family.