-
Notifications
You must be signed in to change notification settings - Fork 3k
Introducing UBLOX_C030 platform. #3992
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
Can you please share test results? |
Here they are for GCC. Do you need them for ARM and IAR as well? |
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
define symbol __ICFEDIT_region_BKPSRAM_end__ = 0x40024FFF; | ||
/*-Sizes-*/ | ||
/*Heap 1/2 of ram and stack 1/8*/ | ||
define symbol __ICFEDIT_size_cstack__ = 0x6000; |
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.
If this is for mbed 5 only, isn't this stack size too big (its for ISR stack) ?
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.
Frankly, I just copied the ODIN one as the processor is the same RAM-wise. What size would you suggest for the needs of mbed-os?
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.
Reduced it to 4 kbytes as discussed.
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
retest uvisor |
Have moved TARGET_UBLOX_C030 under an STM32F437xG sub-directory in alignment with @adustm's new structure. |
Is this uVisor build/test fail a real one? Can someone pass me the failure reason? |
Jenkins error, investigating and restarting jobs here. |
retest uvisor |
/morph test |
@mbed-bot: TEST HOST_OSES=ALL |
[Build 1330] |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Waiting for Jenkins CI to be fixed (some hw related issues currently). |
Found some badly named files, now fixed. |
/morph test |
Hello @RobMeades |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
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.
Looks really good, though it seems like there's an awful lot of #ifdef
checks. I understand they may be necessary though. Would you mind clarifying?
#include "stm32f423xx.h" | ||
#else | ||
#error "Please select first the target STM32F4xx device used in your application (in stm32f4xx.h file)" | ||
#endif |
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.
Is it necessary to have all of these #ifdef
checks? Can't we streamline this? Or is this done this way to reduce the number of changes between ST provided sources?
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.
This is boiler plate STM code, maybe not so necessary with the new directory structure: @adustm your view?
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.
We'll discuss this in ST team. I'll let you know. Best regards
/* Uncomment the line below according to the target STM32 device used in your | ||
application | ||
*/ | ||
#if !defined (STM32F405xx) && !defined (STM32F415xx) && !defined (STM32F407xx) && !defined (STM32F417xx) && \ |
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.
This seems a bit heavy on the #ifdef
checks, can this not be simplified? Perhaps removing some of the commented out code?
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.
@bridadan Be aware this is device drivers that come outside of this repository. Good feedback, however should not block this pull request.
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.
@bridadan Be aware this is device drivers that come outside of this repository. Good feedback, however should not block this pull request.
Agreed, thanks for following up on this!
Ports for Upcoming Targets 3841: Add nRf52840 target ARMmbed/mbed-os#3841 3992: Introducing UBLOX_C030 platform. ARMmbed/mbed-os#3992 Fixes and Changes 3951: [NUCLEO_F303ZE] Correct ARDUINO pin ARMmbed/mbed-os#3951 4021: Fixing a macro to detect when RTOS was in use for the NRF52840_DK ARMmbed/mbed-os#4021 3979: KW24D: Add missing SPI defines and Arduino connector definitions ARMmbed/mbed-os#3979 3990: UBLOX_C027: construct a ticker-based wait, rather than calling wait_ms(), in the ARMmbed/mbed-os#3990 4003: Fixed OBOE in async serial tx for NRF52 target, fixes #4002 ARMmbed/mbed-os#4003 4012: STM32: Correct I2C master error handling ARMmbed/mbed-os#4012 4020: NUCLEO_L011K4 remove unsupported tool chain files ARMmbed/mbed-os#4020 4065: K66F: Move bss section to m_data_2 Section ARMmbed/mbed-os#4065 4014: Issue 3763: Reduce heap allocation in the GCC linker file ARMmbed/mbed-os#4014 4030: [STM32L0] reduce IAR heap and stack size for small targets ARMmbed/mbed-os#4030 4109: NUCLEO_L476RG : minor serial pin update ARMmbed/mbed-os#4109 3982: Ticker - kl25z bugfix for handling events in the past ARMmbed/mbed-os#3982
This pull request introduces the UBLOX_C030 platform. This is a "maker" development board which includes an STM32F4 processor, a cellular module, a GNSS module, a few other peripheral chips and Arduino pin-out. It is a successor to the C027 platform.
The board port is ready in this submission, integration of cellular and GNSS module interfaces will follow.
ARM, IAR and GCC toolsets are supported and all mbed platform tests pass.