Skip to content

NUCLEO_L496ZG: Add new Platform #4650

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 28 commits into from Nov 2, 2017
Merged

NUCLEO_L496ZG: Add new Platform #4650

merged 28 commits into from Nov 2, 2017

Conversation

pmancele
Copy link
Contributor

@pmancele pmancele commented Jun 27, 2017

Description

Add support for the NUCLEO_L496ZG and the STM32L496xG MCUs.
All the toolchains (ARM_MICRO/ARM_STD/IAR/GCC_ARM) have been added but only the GCC_ARM one has been tested on our side.

This PR should resolve #4606.

Status

Ready

This is our first port so feel free to point anything we should change.

Regards

@pmancele pmancele changed the title NUCLEO_L496ZG: Add new Plateform NUCLEO_L496ZG: Add new Platform Jun 27, 2017
@theotherjimmy
Copy link
Contributor

@pmancele When #4610 comes in, could you take advantage of that targets.json refactor?

@pmancele
Copy link
Contributor Author

@theotherjimmy Yes for sure, we noticed the incoming changes.

Description updated.

@theotherjimmy
Copy link
Contributor

@pmancele #4610 is in. Please inherit from the Family STM32 target

@pmancele
Copy link
Contributor Author

@theotherjimmy done

@theotherjimmy
Copy link
Contributor

Excellent. Thank you.

Copy link
Contributor

@0xc0170 0xc0170 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one misaligned line

@@ -63,6 +63,7 @@
{ "target": "NUCLEO_F446ZE", "toolchains": "GCC_ARM", "libs": ["dsp", "usb"] },
{ "target": "NUCLEO_F746ZG", "toolchains": "GCC_ARM", "libs": ["dsp", "usb"] },
{ "target": "NUCLEO_F767ZI", "toolchains": "GCC_ARM", "libs": ["dsp", "usb"] },
{ "target": "NUCLEO_L496ZG", "toolchains": "GCC_ARM", "libs": ["dsp"] },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you align this line ?

@jeromecoutant
Copy link
Collaborator

Hi
I don't any issue after review.
I can't test yet, I should receive a board soon :-)
thx


const PinMap PinMap_ADC[] = {
{PA_0, ADC_1, STM_PIN_DATA_EXT(STM_MODE_ANALOG, GPIO_NOPULL, 0, 5, 0)}, // ADC1_IN5
// {PA_0, ADC_2, STM_PIN_DATA_EXT(STM_MODE_ANALOG, GPIO_NOPULL, 0, 5, 0)}, // ADC2_IN5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of commenting those lines, we use now this convention: "PA_0_ALT0". With PA_0_ALT0 defined in PinNames.h. You can have a look for example in the DISCO_L475VG_IOT01A target.


const PinMap PinMap_I2C_SDA[] = {
{PB_4, I2C_3, STM_PIN_DATA(STM_MODE_AF_OD, GPIO_NOPULL, GPIO_AF4_I2C3)},
// {PB_7, I2C_1, STM_PIN_DATA(STM_MODE_AF_OD, GPIO_NOPULL, GPIO_AF4_I2C1)}, // (pin used by LED2)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have also decided recently to enable all pins even those connected to other board's components. This way anobody who has created his own board with the same device will be able to use this target. We use also this convention "// Connected to LED2".

};

//*** PWM ***

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add this comment: "// Warning: Pins using PWM_5 cannot be used as TIMER5 is already used by the us_ticker."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that now we enable all pins and use the convention "PA_0_ATL0" for example to let users access to all pins on custom boards. But should I also uncomment the pins using PWM_5 ? I guess no as user shouldn't use them while TIMER5 is used by the ticker.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you're right. The pins using PWM_5 must remain commented.

{PA_0, PWM_2, STM_PIN_DATA_EXT(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF1_TIM2, 1, 0)}, // TIM2_CH1
// {PA_0, PWM_5, STM_PIN_DATA_EXT(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF2_TIM5, 1, 0)}, // TIM5_CH1
{PA_1, PWM_15, STM_PIN_DATA_EXT(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF14_TIM15, 1, 1)}, // TIM15_CH1N
// {PA_1, PWM_2, STM_PIN_DATA_EXT(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF1_TIM2, 2, 0)}, // TIM2_CH2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use PA_1_ALT0 and same for all commented pins

{PD_2, UART_5, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF8_UART5)},
{PD_6, UART_2, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF7_USART2)},
{PD_9, UART_3, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF7_USART3)},
{PG_8, LPUART_1, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF8_LPUART1)},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add "// Connected to STDIO_UART_RX"

{PC_12, UART_5, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF8_UART5)},
{PD_5, UART_2, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF7_USART2)},
{PD_8, UART_3, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF7_USART3)}, // ARDUINO D1
{PG_7, LPUART_1, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF8_LPUART1)},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add "// Connected to STDIO_UART_TX"

@@ -0,0 +1,96 @@
/* mbed Microcontroller Library
*******************************************************************************
* Copyright (c) 2015, STMicroelectronics
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2017


#include "PeripheralPins.h"

// =====
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add this note instead:

//==============================================================================
// Notes
//
// - The pins mentionned Px_y_ALTz are alternative possibilities which use other
//   HW peripheral instances. You can use them the same way as any other "normal"
//   pin (i.e. PwmOut pwm(PA_7_ALT0);). These pins are not displayed on the board
//   pinout image on mbed.org.
//
// - The pins which are connected to other components present on the board have
//   the comment "Connected to xxx". The pin function may not work properly in this
//   case. These pins may not be displayed on the board pinout image on mbed.org.
//   Please read the board reference manual and schematic for more information.
//
//==============================================================================

#ifdef __cplusplus
extern "C" {
#endif

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add:

typedef enum {
    ALT0  = 0x100,
    ALT1  = 0x200,
    ALT2  = 0x300,
    ALT3  = 0x400
} ALTx;

#endif

typedef enum {
PA_0 = 0x00,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add:
PA_0_ALT0 = PA_0|ALT0,
whenever it is necessary. We put only used pins not all of them.

/*-Memory Regions-*/
define symbol __ICFEDIT_region_ROM_start__ = 0x08000000;
define symbol __ICFEDIT_region_ROM_end__ = 0x0807FFFF;
define symbol __ICFEDIT_region_ROM_TARA_start__ = 0x08080000; /* TARA Lite Demo */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be removed. Is it from previous project ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your review !
I get this file on STM32Cube as indicated here ST porting guide but it seems that I took it from a project example. I will replace it with the template provided by STM32Cube.

@pmancele
Copy link
Contributor Author

pmancele commented Jul 4, 2017

@bcostm The 4 new commits should resolve what you pointed in your review 😉

@bcostm
Copy link
Contributor

bcostm commented Jul 4, 2017

Thanks for your contribution.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 4, 2017

Thanks @bcostm for the review.

@pmancele Any tests run on this new platform? Can you share the results?

@pmancele
Copy link
Contributor Author

pmancele commented Jul 4, 2017

@0xc0170 By test you mean the results of mbed test ?
If so, here is the result of the mbed test command :

+-----------------------+---------------+--------------------------------------------------------------------------------------+---------+--------------------+-------------+
| target                | platform_name | test suite                                                                           | result  | elapsed_time (sec) | copy_method |
+-----------------------+---------------+--------------------------------------------------------------------------------------+---------+--------------------+-------------+
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-basic_test                        | OK      | 8.38               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-basic_test_default                | OK      | 8.35               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-case_async_validate               | OK      | 8.53               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-case_control_async                | OK      | 8.35               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-case_control_repeat               | OK      | 10.72              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-case_selection                    | OK      | 8.61               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-case_setup_failure                | OK      | 9.21               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-case_teardown_failure             | OK      | 8.54               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-control_type                      | TIMEOUT | 65.86              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-minimal_async_scheduler           | OK      | 8.38               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-minimal_scheduler                 | OK      | 10.23              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-test_assertion_failure_test_setup | OK      | 8.36               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-test_setup_case_selection_failure | OK      | 8.53               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-frameworks-utest-tests-unit_tests-test_setup_failure                | OK      | 8.57               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-tests-filesystem-heap_block_device                                  | OK      | 8.38               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-tests-filesystem-mbr_block_device                                   | TIMEOUT | 67.38              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-features-tests-filesystem-util_block_device                                  | OK      | 8.91               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-rtos-rtx5-target_cortex_m-tests-memory-heap_and_stack                        | OK      | 8.34               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-events-queue                                                           | TIMEOUT | 67.05              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-events-timing                                                          | OK      | 8.55               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-integration-basic                                                      | OK      | 8.39               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-c_strings                                                 | OK      | 10.5               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-dev_null                                                  | OK      | 8.46               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-echo                                                      | OK      | 8.56               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-flashiap                                                  | OK      | 8.37               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-generic_tests                                             | OK      | 9.48               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-lp_timeout                                                | OK      | 17.89              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-race_test                                                 | OK      | 9.95               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-rtc                                                       | OK      | 19.4               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-stl_features                                              | OK      | 9.33               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-ticker                                                    | OK      | 8.54               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-timeout                                                   | OK      | 8.56               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_drivers-wait_us                                                   | OK      | 8.55               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_functional-callback                                               | OK      | 8.37               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_functional-callback_big                                           | OK      | 8.47               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_functional-callback_small                                         | OK      | 10.21              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_functional-functionpointer                                        | OK      | 8.53               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_hal-flash                                                         | OK      | 8.64               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_hal-lp_ticker                                                     | OK      | 8.52               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_hal-rtc_time                                                      | OK      | 8.53               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbed_hal-ticker                                                        | OK      | 8.56               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-mbed-attributes                                              | OK      | 8.44               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-mbed-call_before_main                                        | OK      | 8.36               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-mbed-cpp                                                     | OK      | 8.47               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-mbed-div                                                     | OK      | 8.39               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-mbed-static_assert                                           | OK      | 8.54               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-basic                                              | OK      | 8.41               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-isr                                                | OK      | 8.57               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-mail                                               | OK      | 8.39               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-malloc                                             | OK      | 25.83              | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-mutex                                              | OK      | 8.45               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-queue                                              | OK      | 8.54               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-semaphore                                          | OK      | 8.52               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-signals                                            | OK      | 8.49               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-threads                                            | OK      | 8.55               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedmicro-rtos-mbed-timer                                              | OK      | 8.57               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedtls-multi                                                          | OK      | 8.54               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-mbedtls-selftest                                                       | OK      | 8.52               | shell       |
| NUCLEO_L496ZG-GCC_ARM | NUCLEO_L496ZG | mbed-os-tests-netsocket-ip_parsing                                                   | OK      | 8.53               | shell       |
+-----------------------+---------------+--------------------------------------------------------------------------------------+---------+--------------------+-------------+
mbedgt: test suite results: 56 OK / 3 TIMEOUT

We also try with success the blinky example and some 6LoWPAN program using the ATMEL Firefly 6LoWPAN shield.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 4, 2017

what are those timeouts ? HAve you resolved them?

@pmancele
Copy link
Contributor Author

pmancele commented Jul 5, 2017

@0xc0170 It seems that it is an issue specific to Linux (we are using Ubuntu 16.04). Sometimes we have a lots of timeout, sometimes not. I just ran the tests on windows and 100% of the test were OK.

@jeromecoutant
Copy link
Collaborator

Hi
If you have time, last thing is to add the NUCLEO board in
https://github.com/ARMmbed/mbed-ls/blob/master/mbed_lstools/lstools_base.py
:-)

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 18, 2017

/morph uvisor-test

@mbed-ci
Copy link

mbed-ci commented Oct 18, 2017

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 19, 2017

/morph uvisor-test

@theotherjimmy
Copy link
Contributor

/morph export-build

@mbed-bot
Copy link

Result: FAILURE

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

/morph export-build

Output

mbed Build Number: 168

Exporter Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 23, 2017

@pmancele The one and only one failure, NUCLEO_L496ZG for uvision does not build, can you please retest blinky example, should be able to reproduce the failure

@bcostm
Copy link
Contributor

bcostm commented Oct 24, 2017

I ran mbed export -m NUCLEO_L496ZG -i uvision5 and built the project without any error. I have no access to the ci error. What is it exactly ?

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 27, 2017

@bcostm thanks for testing. I run it also locally, no errors for me, blinky, uvision5.

/morph export-build

@mbed-bot
Copy link

Result: FAILURE

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

/morph export-build

Output

mbed Build Number: 169

Exporter Build failed!

@adbridge
Copy link
Contributor

16:48:46 irq_cm4f.S: Error: #5: cannot open source input file "__UVISION_VERSION SETA 521": No such file or directory
16:48:46 irq_cm4f.S: __UVISION_VERSION SETA 521: 0 warnings, 1 errorirq_cm4f.S: Error: A1067E: Output file specified as 'mbed-os\rtos\TARGET_CORTEX\rtx5\TARGET_RTOS_M4_M7\TOOLCHAIN_ARM\irq_cm4f.S', but it has already been specified as '.\build\irq_cm4f.o'
16:48:46 irq_cm4f.S: error: A1905U: Pre-processor step failed for '__UVISION_VERSION SETA 521'

@theotherjimmy Could this be a tool issue ?

@theotherjimmy
Copy link
Contributor

Maybe. It looks like spaces in an assembly path did not get escaped correctly

@theotherjimmy
Copy link
Contributor

sigh it's in common code. If that's the case why did this board fail, and no others.

@mbed-ci
Copy link

mbed-ci commented Oct 31, 2017

@adbridge
Copy link
Contributor

On the latest exporter build I can't actually see what the failure was! Re-running
/morph export-build

@studavekar
Copy link
Contributor

From the logs looks like Segmentation fault

"/builds/ws/exporter-build-matrix/37/K66F_make_iar/sources/mbed-os/features/FEATURE_COMMON_PAL/sal-stack-nanostack-eventloop/source/system_timer.c",313  Warning[Pe546]: transfer of control bypasses initialization of:
            variable "event" (declared at line 318)
make[1]: *** [mbed-os/rtos/TARGET_CORTEX/rtx5/TARGET_RTOS_M4_M7/TOOLCHAIN_IAR/irq_cm4f.o] Segmentation fault (core dumped)
make[1]: *** Deleting file 'mbed-os/rtos/TARGET_CORTEX/rtx5/TARGET_RTOS_M4_M7/TOOLCHAIN_IAR/irq_cm4f.o'
make[1]: *** Waiting for unfinished jobs....

@mbed-ci
Copy link

mbed-ci commented Oct 31, 2017

@studavekar
Copy link
Contributor

Re-triggering the exporter build as make_iar segmentation fault is fixed
/morph export-build

@mbed-ci
Copy link

mbed-ci commented Nov 1, 2017

@0xc0170
Copy link
Contributor

0xc0170 commented Nov 2, 2017

@studavekar I did not report status back (the last exporter build)

@0xc0170
Copy link
Contributor

0xc0170 commented Nov 2, 2017

Fixed now, all green, ready for merge 🎆

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.

No target for STM32L496