Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Initial addition of files to support CY8CKIT_064S2_4343W target #11434
This PR brings support for new Cypress target in mbed-os - CY8CKIT_064S2_4343W.
Tests run logs:
Pull request type
@maclobdell Hi Mac, in current implementation this one depends on #11504, but since status and resolution of 11504 is not clear right now i can make a little tweak (it is ready, just need to push) to make this one work without 11504 to align implementation with existing CY8CKIT_062_WIFI_BT and we would be able to push this one forward.
In case 11504 would be merged - all existing targets would need update anyways.
@romanjoe This is pretty unclear case how it fails. This is handled similar way than CY8CPROTO_064_SB which works well. But in this happens:
First line comes from
The key question is that what is so different in this than CY8CPROTO_064_SB that this cannot work? Wifi example build works well with CY8CPROTO_064_SB.
Problem with mbed-os-example-wifi raises because of lack of flash for this example. I suppose you would be able to find message similar to this:
This message comes from tool that adds cryptographic signature to compiled image. This tool has set of parameters used for adding signature. One of them is a slot size used by Cypressbootloader for boot. This value is set in policy file - mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/sb-tools/policy/policy_single_stage_CM4.json and equals 0x50000.
There should be 2 slots of this size to enable upgrade possibility using UPGRADE slot.
CY8CPROTO_064_SB target has no connectivity (thus no wifi/bt code compiled and included to hex file) and 1M of flash overall. So it can fit 2 slots of size 0x50000 (considering flash alignments restrictions and memory protection configuration restrictions).
CY8CKIT_064S2_4343W uses same policy file and slot sizes, but has wifi/bt and as result much bigger hex file, than 0x50000. Since this board has 2M of flash - slot sizes can be stretched to fit bigger hex file. This described in Secure Boot user guide and Readme.md in mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/sb-tools (https://www.cypress.com/secureboot-sdk-user-guide).
As a solution for CI i can add additional file to mbed-os/targets/TARGET_Cypress/TARGET_PSOC6/sb-tools/policy, with stretched bootloader slots sizes to use with CY8CKIT_064S2_4343W.
@OPpuolitaival did you try to build wifi example with latest changes i made yesterday? i was able to compile and get image signed successfully with new policy file. actually having this new file as template for 2M board would provide better user experience with no need to read User Guide immediately after getting started