Skip to content

Support NUMAKER_PFM_M487 #40

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Support NUMAKER_PFM_M487 #40

wants to merge 1 commit into from

Conversation

ccli8
Copy link
Contributor

@ccli8 ccli8 commented Oct 4, 2019

Description

This PR is split of #25 and to support NUMAKER_PFM_M487.

@anttiylitokola
Copy link
Contributor

Can one of the admins verify this patch?

1 similar comment
@anttiylitokola
Copy link
Contributor

Can one of the admins verify this patch?

@ccli8 ccli8 mentioned this pull request Oct 4, 2019
Closed
@ccli8
Copy link
Contributor Author

ccli8 commented Oct 28, 2019

Make modifications:

  1. Do rebase
  2. Update COMPONENT_NUSD.lib to support change of M2351 base target name to match platform name enrolled in mbed-os-tools platform database.

teetak01
teetak01 reviewed Nov 28, 2019
View reviewed changes
Copy link
Contributor

@teetak01 teetak01 left a comment

Choose a reason for hiding this comment

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

Can you update the README?

@teetak01
Copy link
Contributor

run-ci

@iot-pdmc
Copy link
Collaborator

Test run: FAILED

Test summary:
Executed: 14
Failed: 12
Skipped: 0
Errors: 2

Failed test cases:
K64F-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2.K64F - [Timeout: Did not find Endpoint Name within 600 seconds]
K64F-ARM-TCP: ExampleAppCloudTest01_Rel1_2.K64F - [Timeout: Did not find Endpoint Name within 600 seconds]
K66F-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2.K66F - [Timeout: Did not find Endpoint Name within 600 seconds]
K66F-ARM-TCP: ExampleAppCloudTest01_Rel1_2.K66F - [Timeout: Did not find Endpoint Name within 600 seconds]
NUCLEO_F429ZI-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2.NUCLEO_F429ZI - [Timeout: Did not find Endpoint Name within 600 seconds]
NUCLEO_F429ZI-ARM-TCP: ExampleAppCloudTest01_Rel1_2.NUCLEO_F429ZI - [Timeout: Did not find Endpoint Name within 600 seconds]
UBLOX_EVK_ODIN_W2-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2.UBLOX_EVK_ODIN_W2 - [Timeout: Did not find Endpoint Name within 600 seconds]
UBLOX_EVK_ODIN_W2-ARM-TCP: ExampleAppCloudTest01_Rel1_2.UBLOX_EVK_ODIN_W2 - [Timeout: Did not find Endpoint Name within 600 seconds]
NUCLEO_F411RE-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2.NUCLEO_F411RE - [Timeout: Did not get network connection within 600 seconds]
NUCLEO_F411RE-ARM-TCP: ExampleAppCloudTest01_Rel1_2.NUCLEO_F411RE - [Timeout: Did not get network connection within 600 seconds]
NUMAKER_PFM_M487-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2 - [Execution configuration file ./pdmc-jenkins/test-configs/mbed-os-example-pelion-configs/tc_NUMAKER_PFM_M487.json does not exist.]
NUMAKER_PFM_M487-ARM-TCP: ExampleAppCloudTest01_Rel1_2 - [Execution configuration file ./pdmc-jenkins/test-configs/mbed-os-example-pelion-configs/tc_NUMAKER_PFM_M487.json does not exist.]
DISCO_L475VG_IOT01A-GCC_ARM-TCP: ExampleAppCloudTest01_Rel1_2.DISCO_L475VG_IOT01A - [Timeout: Did not find Endpoint Name within 600 seconds]
DISCO_L475VG_IOT01A-ARM-TCP: ExampleAppCloudTest01_Rel1_2.DISCO_L475VG_IOT01A - [Timeout: Did not find Endpoint Name within 600 seconds]
Build artifacts

posted-by-tag: https://jenkins-client.isgtesting.com/job/mbed-os-example-pelion/

@ccli8
Support NUMAKER_PFM_M487
fa31228 
Based on mbed-os-pelion-example master/mbed-bootloader 4.1.0/mbed-cloud-client 4.0.0,
support Nuvoton targets:
1.  Support Nuvoton targets:
    -   NUMAKER_PFM_M487
2.  Change storage to NUSD (SD card in SDIO bus mode) from SD (SD card SPI bus mode)
    (1) Add COMPONENT_NUSD.lib.
    (2) Add component NUSD (target.components_add).
    (3) Change default BlockDevice to NUSD:
        Override BlockDevice::get_default_instance (nusd.provide-default-blockdevice).
        Required since mbed-cloud-client 2.1.0 (arm_uc_blockdevice_ext) or in:
        mbed-bootloader/modules/storage/pal-blockdevice/source/arm_uc_pal_blockdevice_mbed.cpp
    (4) Enable kvstore with blockdevice type being "other".
        i)  Override get_other_blockdevice() (nusd.provide-kvstore-other-blockdevice).
        ii) Configure storage type to "FILESYSTEM".
        iii)Configure file system type to "LITTLE".
        vi) Configure block device type to "other".
        v)  Configure external size to 64MiB, which cannot overlap with update-client.
            storage-address/update-client.storage-size.
3.  Requirements for mbed-os version:
    -   mbed-os 5.13.0 (or afterwards) to support kvstore with block device type being "other"
    -   mbed-os 5.13.1 (or afterwards) to fix 'undefined pal_plat_osEntropyInject(...)' error
@teetak01 teetak01 closed this Jan 9, 2020
@ccli8 ccli8 mentioned this pull request Jan 10, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@teetak01 teetak01 teetak01 left review comments

Assignees
No one assigned
Labels
Missing hardware in CI new platform Requires CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ccli8 @anttiylitokola @teetak01 @iot-pdmc