mbed Enabled certificate for the VBLUno51 board #4719

iotmember · 2017-07-06T17:07:25Z

Description

This PR add new BOARD_ID for the VBLUno51 board.

The mbed Enabled process for the VBLUno51 board

Status

READY

Migrations

NO

Signed-off-by: iotvietmember [email protected]

adbridge · 2017-07-07T10:14:16Z

@iotvietmember please remove the merge commit and do a rebase instead. Thanks

iotmember · 2017-07-08T01:02:55Z

@adbridge I have just fixed those problem. Thanks

adbridge · 2017-07-10T09:49:50Z

@iotvietmember Thanks :)

adbridge · 2017-07-10T09:50:28Z

/morph test

mbed-bot · 2017-07-10T11:56:58Z

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 751

All builds and test passed!

iotmember · 2017-07-10T13:24:00Z

@adbridge I saw the good results

theotherjimmy · 2017-07-10T17:16:23Z

@iotvietmember This PR is on hold until we get 10 samples. See https://www.mbed.com/en/about-mbed/mbed-enabled/#Program_Requirements for more details.

iotmember · 2017-07-11T00:02:57Z

@theotherjimmy We have sent 10 samples of the VBLUno51 board for mbed team in Japan on 08 June 2017.
Tracking

And the following file is apply form for mbed Enabled Apply form

0xc0170 · 2017-07-11T14:30:26Z

@theotherjimmy We have sent 10 samples of the VBLUno51 board for mbed team in Japan on 08 June 2017.

cc @toyowata

iotmember · 2017-07-13T09:56:35Z

@toyowata Would you please check the mbed Enabled progress for the VBLUno51 board. Many thanks

toyowata · 2017-07-13T11:40:12Z

I sent the board to Austin/TX team from Japan two days ago. Test engineer will be assigned in that team for the VBLUno51 board.

iotmember · 2017-07-13T12:35:15Z

@toyowata @0xc0170 @theotherjimmy Thanks for your support and hope that we will be received the good news from your soon.

Email from Sarah Marsh (mbed): ************************************ Hi, Here is your daplink board ID: C006 The slug: VBLUNO51 When I execute mbedls, it looks like you have used the DAPLink ID for the NRF51_DK. You need your own unique ID. We are running the tests with the NRF51_DK ID mocked as your platform, but you will need to do the following to be mbed enabled: Please submit a PR against mbed-ls (https://github.com/ARMmbed/mbed-ls), so your board can be detected with our tools. Please also submit a PR against DAPLink (https://github.com/mbedmicro/DAPLink), so that your board is uniquely identifiable. Thanks, Sarah ************************************ The VBLUno51 board was added to mbed-os 5.5.2 released ARMmbed/mbed-os#4629 ARMmbed/mbed-os#4719 Signed-off-by: iotvietmember <[email protected]>

Sarah Marsh (mbed) said that the VBLUno51 board could use board ID is C006 The slug: VBLUNO51 The VBLUno51 board was added to mbed-os 5.5.2 released ARMmbed/mbed-os#4629 ARMmbed/mbed-os#4719 Signed-off-by: iotvietmember <[email protected]>

Email from Sarah Marsh (mbed): ************************************ Hi, Here is your daplink board ID: C006 The slug: VBLUNO51 When I execute mbedls, it looks like you have used the DAPLink ID for the NRF51_DK. You need your own unique ID. We are running the tests with the NRF51_DK ID mocked as your platform, but you will need to do the following to be mbed enabled: Please submit a PR against mbed-ls (https://github.com/ARMmbed/mbed-ls), so your board can be detected with our tools. Please also submit a PR against DAPLink (https://github.com/mbedmicro/DAPLink), so that your board is uniquely identifiable. Thanks, Sarah ************************************ The VBLUno51 board was added to mbed-os 5.5.2 released ARMmbed/mbed-os#4629 ARMmbed/mbed-os#4719 Signed-off-by: iotvietmember <[email protected]>

Sarah Marsh (mbed) said that the VBLUno51 board could use board ID is C006 The slug: VBLUNO51 The VBLUno51 board was added to mbed-os 5.5.2 released ARMmbed/mbed-os#4629 ARMmbed/mbed-os#4719 Signed-off-by: iotvietmember <[email protected]>

0xc0170 · 2017-10-19T11:19:59Z

/morph build

mbed-ci · 2017-10-19T11:58:52Z

Build : SUCCESS

Build number : 259
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/4719/

Skipping test trigger, missing label 'NEED CI'

mbed-ci · 2017-10-31T06:57:59Z

Exporter Build : FAILURE

Build number : 38
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/4719/

adbridge · 2017-10-31T14:35:39Z

@0xc0170, @theotherjimmy, @senthilr Could you please confirm you are happy with the changes ?

studavekar · 2017-11-03T21:35:17Z

/morph build

studavekar · 2017-11-03T22:18:59Z

/morph export-build

mbed-ci · 2017-11-03T22:33:24Z

Build : SUCCESS

Build number : 431
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/4719/

Triggering tests

/morph test
/morph uvisor-test

mbed-ci · 2017-11-04T01:36:30Z

Test : FAILURE

Build number : 222
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/4719/222

mbed-ci · 2017-11-05T07:12:18Z

Exporter Build : SUCCESS

Build number : 82
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/4719/

mbed-ci · 2017-11-05T07:13:41Z

Test : FAILURE

Build number : 238
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/4719/238

iotmember · 2017-11-05T13:51:44Z

What is the problem?

0xc0170 · 2017-11-06T10:27:46Z

What is the problem?

We are currently investigating the K64F failures, not related to this pull request.

studavekar · 2017-11-09T19:01:27Z

Looks like master is all green starting fresh build

Triggering build

/morph build

mbed-ci · 2017-11-09T19:35:03Z

Build : SUCCESS

Build number : 482
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/4719/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

mbed-ci · 2017-11-09T20:00:41Z

/morph export-build

mbed-ci · 2017-11-09T21:09:21Z

Exporter Build : SUCCESS

Build number : 99
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/4719/

mbed-ci · 2017-11-09T21:26:37Z

Test : SUCCESS

Build number : 302
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/4719/302

iotmember · 2017-11-20T15:33:26Z

What do I need to do?

theotherjimmy · 2017-11-20T19:23:24Z

@iotvietmember I think this is waiting on @senthilr's review.

c1728p9 · 2017-11-22T18:25:57Z

Hi @iotvietmember, I took a look at why this was failing tests-mbed_drivers-ticker on gcc. Its because UART data is being lost during the test. If flow control is enabled in DAPLink and on the VBLUNO51 then this test passes reliably.

The VBLUno51 board needs to be disabled UART Hardware flow control feature, compatible with nrf51822 target on mbed Online Compiler.

You mentioned that flow control needed to be turned off due to the nrf51822. The VBLUno51 has an nrf51822 on it and it works with flow control. By nrf51822 do you mean a board other than the VBLUno51? If so what board?

adbridge · 2018-01-02T14:22:48Z

@iotvietmember Could you please address address @c1728p9 question ?

mbed-ci · 2018-01-02T14:22:50Z

Automatic CI verification build not done, please verify manually.

cmonr · 2018-01-12T16:39:35Z

Are we still waiting on DevX/@senthilr's ok, since the MBed page for the hardware is live?

@iotvietmember Ping on @c1728p9's question.

iotmember · 2018-01-16T15:58:44Z

@cmonr @adbridge @c1728p9 My board is the VBLUno51 and we hope that we can use 'VBLUNO51' as target name on mbed.
On hardware, the VBLUno51 has UART hardware flow control.

When I created the https://os.mbed.com/platforms/VBLUNO51/, A notice in the upper right corner with content
"To compile a program for this board using Mbed CLI, use nrf51822 as the target name."
So I have to cancel the HWFC UART feature on the VBLUno51.
After that, you modified
"To compile a program for this board using Mbed CLI, use VBLUNO51 as the target name."
This means that we can use VBLUNO51 as the name of the board on the mbed. This means that the UART HWFC feature is used (fw_daplink_vbluno51_release_1.0.0.bin
https://os.mbed.com/teams/VNGIoTLab/wiki/vbluno51-interface-firmware)

Many thanks

cmonr · 2018-01-22T16:28:30Z

@iotvietmember Thanks for that clarification!

adbridge added the needs: work label Jul 7, 2017

iotmember force-pushed the release_os_5 branch from b5a08b4 to eca4855 Compare July 8, 2017 01:01

adbridge added needs: CI and removed needs: work labels Jul 10, 2017

adbridge added ready for merge release-version: 5.5.3 and removed needs: CI labels Jul 10, 2017

theotherjimmy added do not merge and removed ready for merge release-version: 5.5.3 labels Jul 10, 2017

iotmember mentioned this pull request Jul 21, 2017

Add support for the VBLUno51 board ARMmbed/mbed-ls#187

Merged

iotmember mentioned this pull request Jul 21, 2017

Add support for the VBLUno51 board pyocd/pyOCD#324

Merged

iotmember mentioned this pull request Jul 21, 2017

Add support for the VBLUno51 board ARMmbed/DAPLink#290

Merged

cmonr added ready for merge release-version: 5.7.4 and removed needs: review labels Jan 19, 2018

cmonr merged commit a33acaa into ARMmbed:master Jan 22, 2018

cmonr removed the ready for merge label Jan 23, 2018

mbed Enabled certificate for the VBLUno51 board #4719

mbed Enabled certificate for the VBLUno51 board #4719

Uh oh!

Conversation

iotmember commented Jul 6, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Status

Migrations

Uh oh!

adbridge commented Jul 7, 2017

Uh oh!

iotmember commented Jul 8, 2017

Uh oh!

adbridge commented Jul 10, 2017

Uh oh!

adbridge commented Jul 10, 2017

Uh oh!

mbed-bot commented Jul 10, 2017

Output

Uh oh!

iotmember commented Jul 10, 2017

Uh oh!

theotherjimmy commented Jul 10, 2017

Uh oh!

iotmember commented Jul 11, 2017

Uh oh!

0xc0170 commented Jul 11, 2017

Uh oh!

iotmember commented Jul 13, 2017

Uh oh!

toyowata commented Jul 13, 2017

Uh oh!

iotmember commented Jul 13, 2017

Uh oh!

0xc0170 commented Oct 19, 2017

Uh oh!

mbed-ci commented Oct 19, 2017

Uh oh!

mbed-ci commented Oct 31, 2017

Uh oh!

adbridge commented Oct 31, 2017

Uh oh!

studavekar commented Nov 3, 2017

Uh oh!

studavekar commented Nov 3, 2017

Uh oh!

mbed-ci commented Nov 3, 2017

Triggering tests

Uh oh!

mbed-ci commented Nov 4, 2017

Uh oh!

mbed-ci commented Nov 5, 2017

Uh oh!

mbed-ci commented Nov 5, 2017

Uh oh!

iotmember commented Nov 5, 2017

Uh oh!

0xc0170 commented Nov 6, 2017

Uh oh!

studavekar commented Nov 9, 2017

Triggering build

Uh oh!

mbed-ci commented Nov 9, 2017

Triggering tests

Uh oh!

mbed-ci commented Nov 9, 2017

Uh oh!

mbed-ci commented Nov 9, 2017

Uh oh!

mbed-ci commented Nov 9, 2017

Uh oh!

iotmember commented Nov 20, 2017

Uh oh!

theotherjimmy commented Nov 20, 2017

Uh oh!

c1728p9 commented Nov 22, 2017

Uh oh!

adbridge commented Jan 2, 2018

Uh oh!

iotmember commented Jul 6, 2017 •

edited

Loading