Skip to content

Add support for the VBLUno52 board #4765

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
Jul 27, 2017

Conversation

iotmember
Copy link
Contributor

Description

This PR add new target for the VBLUno52 board (VNG Bluetooth Low Energy UNO nRF52832)

  • The VBLUno52 board
    nRF52832 ARM Cortex-M4F processor
    Bluetooth Low Energy 5.0
    DAPLink interface
    UNO pinout
    4 power
    Pinout :
    vbluno52_mbed

Status

READY

Migrations

NO

Test results

Pass all test case in mbed test suite

test_result_vbluno52.zip

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 18, 2017

Can you please instead of merging rebase your branch from master? thanks

@iotmember
Copy link
Contributor Author

@0xc0170 Give me more specific about your request? Thank you

@theotherjimmy
Copy link
Contributor

theotherjimmy commented Jul 19, 2017

@iotvietmember You used the command git merge or git pull (which defaults to the same behavior as git merge) to pull in changes from the latest master and resolve your conflicts. This created a commit with a name starting with "Merge branch" and that indicated to us that you used a merge. Instead of using git merge or git pull we are asking that you use the command git rebase in particular, the command you would probably run is git rebase master.

Looks like you just got it, actually!

@iotmember
Copy link
Contributor Author

@theotherjimmy I have just fixed the problem. Was my action right or wrong?

@theotherjimmy
Copy link
Contributor

What matters is that the history looks correct. I think you took a correct action.

@iotmember
Copy link
Contributor Author

@theotherjimmy @0xc0170 Thank you for your support. I hope that this PR will be reviewed soon.

@iotmember
Copy link
Contributor Author

@theotherjimmy I hope that this commit will be reviewed soon. Thank you very much

Copy link
Contributor

@theotherjimmy theotherjimmy left a comment

Choose a reason for hiding this comment

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

Looking good, but we should get another review on here.

Questions/minor improvements suggested below.





Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this file full of white space?

"supported_form_factors": ["ARDUINO"],
"inherits": ["MCU_NRF52"],
"macros_add": ["BOARD_PCA10040", "NRF52_PAN_12", "NRF52_PAN_15", "NRF52_PAN_58", "NRF52_PAN_55", "NRF52_PAN_54", "NRF52_PAN_31", "NRF52_PAN_30", "NRF52_PAN_51", "NRF52_PAN_36", "NRF52_PAN_53", "S132", "CONFIG_GPIO_AS_PINRESET", "BLE_STACK_SUPPORT_REQD", "SWI_DISABLE0", "NRF52_PAN_20", "NRF52_PAN_64", "NRF52_PAN_62", "NRF52_PAN_63"],
"device_has": ["ANALOGIN", "ERROR_PATTERN", "I2C", "I2C_ASYNCH", "INTERRUPTIN", "LOWPOWERTIMER", "PORTIN", "PORTINOUT", "PORTOUT", "PWMOUT", "RTC", "SERIAL", "SERIAL_ASYNCH", "SERIAL_FC", "SLEEP", "SPI", "SPI_ASYNCH", "SPISLAVE"],
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you not set ERROR_PATTERN? It's not really a piece of hardware after all...

@iotmember
Copy link
Contributor Author

iotmember commented Jul 21, 2017

@theotherjimmy I have just fixed the problem in "device.h". I think that I should declare ERROR_PATTERN in "targets.json" for the VBLUno52 board which use Nordic nRF52832 chip, same as NRF52_DK board.
Thank you for your support.

@theotherjimmy
Copy link
Contributor

theotherjimmy commented Jul 21, 2017

@iotvietmember I don't understand what you're trying to say. Could you explain?

@iotmember
Copy link
Contributor Author

@theotherjimmy I have just fixed the problem in "device.h". I think that I should declare ERROR_PATTERN in "targets.json" for the VBLUno52 board which use Nordic nRF52832 chip, same as NRF52_DK board.
Thank you for your support.

@theotherjimmy
Copy link
Contributor

theotherjimmy commented Jul 21, 2017

Hmmm... @iotvietmember I would rather the Nordic boards, or any boards, not declare "ERROR_PATTERN" in targets.json. It certainly won't affect support. It only affects the led behavior of the function mbed_die.

@iotmember
Copy link
Contributor Author

@theotherjimmy In your opinion, What is file name which I need to declare ERROR_PATTERN in it?

@theotherjimmy
Copy link
Contributor

@iotvietmember leave it in targets.json. I'll submit a PR to remove all of the ERROR_* things next week.

@iotmember
Copy link
Contributor Author

@theotherjimmy I have just fixed the problem about ERROR_PATTERN for the VBLUno52 and VBLUno51 board in targets.json.

@theotherjimmy
Copy link
Contributor

theotherjimmy commented Jul 21, 2017

@iotvietmember Now your commit modifies VBLUno51 as well. Could you add that to the commit message or break up the commit? You added it to the commit message! My bad.

Copy link
Contributor

@theotherjimmy theotherjimmy left a comment

Choose a reason for hiding this comment

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

👍

Fix ERROR_PATTERN in VBLUNO52 config

Signed-off-by: iotvietmember <[email protected]>
@iotmember
Copy link
Contributor Author

@theotherjimmy I have just fixed the problem. Thanks

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 24, 2017

/morph 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 test

Output

mbed Build Number: 872

Build failed!

@mbed-bot
Copy link

Result: SUCCESS

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

/morph export-build

Output

mbed Build Number: 91

All exports and builds passed!

@iotmember
Copy link
Contributor Author

@theotherjimmy The test results is good. Thank you

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 25, 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: 885

All builds and test passed!

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.

4 participants