Skip to content

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

Merged
merged 1 commit into from
Apr 6, 2017
Merged

Introducing UBLOX_C030 platform. #3992

merged 1 commit into from
Apr 6, 2017

Conversation

RobMeades
Copy link
Contributor

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.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 23, 2017

ARM, IAR and GCC toolsets are supported and all mbed platform tests pass.

Can you please share test results?

@RobMeades
Copy link
Contributor Author

Here they are for GCC. Do you need them for ARM and IAR as well?

ublox_c030_tests_gcc.txt

@adbridge
Copy link
Contributor

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1726

All 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;
Copy link
Contributor

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) ?

Copy link
Contributor Author

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?

Copy link
Contributor Author

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.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 29, 2017

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1787

All builds and test passed!

@adbridge
Copy link
Contributor

retest uvisor

@RobMeades
Copy link
Contributor Author

Have moved TARGET_UBLOX_C030 under an STM32F437xG sub-directory in alignment with @adustm's new structure.

@RobMeades
Copy link
Contributor Author

Is this uVisor build/test fail a real one? Can someone pass me the failure reason?

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 3, 2017

Is this uVisor build/test fail a real one? Can someone pass me the failure reason?

Jenkins error, investigating and restarting jobs here.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 3, 2017

retest uvisor

@bridadan
Copy link
Contributor

bridadan commented Apr 3, 2017

/morph test

@bridadan
Copy link
Contributor

bridadan commented Apr 3, 2017

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

@mbed-bot
Copy link

mbed-bot commented Apr 3, 2017

[Build 1330]
SUCCESS: Building succeeded and tests were run! Be sure to check the test results

@mbed-bot
Copy link

mbed-bot commented Apr 4, 2017

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1821

All builds and test passed!

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 4, 2017

Waiting for Jenkins CI to be fixed (some hw related issues currently).

@RobMeades
Copy link
Contributor Author

Found some badly named files, now fixed.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 4, 2017

/morph test

@adustm
Copy link
Member

adustm commented Apr 4, 2017

Hello @RobMeades
Thank you for this file structure. It seems fine to me.
Kind ergards
Armelle

@mbed-bot
Copy link

mbed-bot commented Apr 4, 2017

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1828

All builds and test passed!

Copy link
Contributor

@bridadan bridadan left a 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
Copy link
Contributor

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?

Copy link
Contributor Author

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?

Copy link
Member

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) && \
Copy link
Contributor

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?

Copy link
Contributor

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.

Copy link
Contributor

@bridadan bridadan left a 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!

@sg- sg- merged commit 7a35a4d into ARMmbed:master Apr 6, 2017
aisair pushed a commit to aisair/mbed that referenced this pull request Apr 30, 2024
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants