[STM32L4] Modify folder structure #3657
Conversation
adbridge
changed the title
| define symbol __size_cstack__ = 0x4000; | ||
| define symbol __size_heap__ = 0x8000; | ||
| define symbol __size_cstack__ = 0x8000; | ||
| define symbol __size_heap__ = 0xa000; |
There was a problem hiding this comment.
Is this an intentional modification? Were the old values incorrect?
There was a problem hiding this comment.
Yes, I have discussed with @jamike who wrote the previous values, and we agreed that it used to be a typo
| "supported_toolchains": ["ARM", "uARM", "IAR", "GCC_ARM"], | ||
| "inherits": ["Target"], | ||
| "detect_code": ["0827"], | ||
| "device_has": ["ANALOGIN", "ANALOGOUT", "CAN", "I2C", "I2CSLAVE", "I2C_ASYNCH", "INTERRUPTIN", "LOWPOWERTIMER", "PORTIN", "PORTINOUT", "PORTOUT", "PWMOUT", "RTC", "SERIAL", "SERIAL_ASYNCH", "SERIAL_FC", "SLEEP", "SPI", "SPISLAVE", "STDIO_MESSAGES"], | ||
| "macros": ["TRANSACTION_QUEUE_SIZE_SPI=2","USBHOST_OTHER"], | ||
| "device_has": ["ANALOGIN", "ANALOGOUT", "CAN", "I2C", "I2CSLAVE", "I2C_ASYNCH", "INTERRUPTIN", "LOWPOWERTIMER", "PORTIN", "PORTINOUT", "PORTOUT", "PWMOUT", "RTC", "SERIAL", "SERIAL_ASYNCH", "SERIAL_FC", "SLEEP", "SPI", "SPISLAVE", "SPI_ASYNCH", "STDIO_MESSAGES", "TRNG"], |
There was a problem hiding this comment.
Was the addition of SPI_ASYNCH and TRNG intentional here?
There was a problem hiding this comment.
Yes, L486 and L476 are supposed to get the exact same devices modules, except when it will be about HW encryption :)
|
Hi @bridadan |
|
@mbed-bot: TEST HOST_OSES=ALL |
|
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
[Build 1242] |
|
Hi @bridadan |
waiting for jenkins CI to complete. It was green but not reported here on github |
Ports for Upcoming Targets Fixes and Changes 3432: Target STM USBHOST support ARMmbed/mbed-os#3432 3181: NUCLEO_F207ZG extending PeripheralPins.c: all available alternate functions can be used now ARMmbed/mbed-os#3181 3626: NUCLEO_F412ZG : Add USB Device +Host ARMmbed/mbed-os#3626 3628: Fix warnings ARMmbed/mbed-os#3628 3629: STM32: L0 LL layer ARMmbed/mbed-os#3629 3632: IDE Export support for platform VK_RZ_A1H ARMmbed/mbed-os#3632 3642: Missing IRQ pin fix for platform VK_RZ_A1H ARMmbed/mbed-os#3642 3664: Fix ncs36510 sleep definitions ARMmbed/mbed-os#3664 3655: [STM32F4] Modify folder structure ARMmbed/mbed-os#3655 3657: [STM32L4] Modify folder structure ARMmbed/mbed-os#3657 3658: [STM32F3] Modify folder structure ARMmbed/mbed-os#3658 3685: STM32: I2C: reset state machine ARMmbed/mbed-os#3685 3692: uVisor: Standardize available legacy heap and stack ARMmbed/mbed-os#3692 3621: Fix for #2884, LPC824: export to LPCXpresso, target running with wron ARMmbed/mbed-os#3621 3649: [STM32F7] Modify folder structure ARMmbed/mbed-os#3649 3695: Enforce device_name is valid in targets.json ARMmbed/mbed-os#3695 3723: NCS36510: spi_format function bug fix ARMmbed/mbed-os#3723
Description
ST team has noticed that STM32L476 and STM32L486 should not have the same startup files (the L486 has a few more interrupts).
The folder L476_L486 makes no more sense.
We have thought about introducing a TARGET_STM32L4[device] folder between TARGET_STM32L4 and TARGET_[platform]
With this new folder structure we can share files for several platforms that uses the same STM32 device. For instance, NUCLEO_L476RG and DISCO_L476VG has the same STM32L476xG devices.
I will create the same kind of modifications in other families
Status
READY
Migrations
NO
TESTS:
I have passed tests-integration-basic on the 3 L4 platforms.