Skip to content

Conversation

@maclobdell
Copy link
Contributor

Add support for the Cypress PSoC6 Prototyping board (CY8CPROTO_062_4343) using internal flash for both kvstore an update storage.

This replaces #37.

@iot-pdmc
Copy link
Collaborator

Thanks for your changes.
@ARMmbed/pdmc-integrators please review.

@teetak01
Copy link
Contributor

@maclobdell can you resolve the merge conflicts?

update cy8cproto bootloader file name

add cy8cproto to list, rearange configs

rearrange cy8ckit-062-4343w configs
@teetak01
Copy link
Contributor

build-only

@iot-pdmc
Copy link
Collaborator

@teetak01 teetak01 self-requested a review December 17, 2019 07:03
"target.bootloader_supported" : true,
"target.mbed_rom_start" : "0x10000000",
"target.mbed_rom_size" : "0x00200000",
"target.sectors" : [[268435456, 512]]
Copy link
Contributor

Choose a reason for hiding this comment

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

@maclobdell the last four fields suggest that the Mbed OS support/configuration is not fully ready yet?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it is true that these should probably be added to target.json. I can request Cypress do that or make a PR myself. the last three are needed because there is not a CMSIS pack for this target. Are you okay to accept these configurations now, if we work to move them to a better location later?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think its fine. Just wanted to understand the background better.

Choose a reason for hiding this comment

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

Hi @maclobdell
I am on MBED-os 5.15.0
I had all the configuration done as stated above for CY8CPROTO_062_4343W board.
Same bootloader and same configuration in mbed_app.json but while building I am having below errors.

Using ROM regions bootloader1, bootloader2, header, application in this build.
Region bootloader1: size 0x1400, offset 0x10000000
Region bootloader2: size 0xa400, offset 0x10002000
Region header: size 0x70, offset 0x1000c000
Region application: size 0x1f3c00, offset 0x1000c400
Configuration error: Bootloader not supported on this target. RAM start not found in targets.json.

Am I missing anyrhing?

@teetak01 teetak01 added ready-to-merge build-only Target has no CI support and is approved with only build-check and removed Requires CI labels Dec 20, 2019
@teetak01 teetak01 merged commit 7debdcd into master Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build-only Target has no CI support and is approved with only build-check ready-to-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants