Adds support for nrf5340-DK board (application and networking core) #302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rkudaj
force-pushed
the
porting_to_nrf5430_dk_app_and_net_core
branch
from
d3f8c60 to
0896b99
Compare
rkudaj
force-pushed
the
porting_to_nrf5430_dk_app_and_net_core
branch
from
0896b99 to
ab13535
Compare
|
sorry I was a bit busy recently, and this falled off my radar. I will try to review/test and update this as soon as I could. Thank you for your works and patient. |
|
@hathach Did you do the review/test? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request contains three segger studio projects for dual-core nrf5340_DK board:
Bootloader settings and configuration sections are currently deactivated in this pull request.
Application bootloader is almost the same as for other previous micros, it implements additional mechanizm which
basing on uf2 block address decides whether its destination is application core flash or networking core flash.
In case it is networking core flash it copies data into allocated RAM area (shared with networking core) and sends request
to networking core to write it under proper address. When all blocks are flashed application core sends request to
networking core to start execution of newely received firmware.
Building and flashing sequence:
nrfjprog --recover --coprocessor CP_NETWORK; nrfjprog --recover
Mass storage device should show up on PC.
All bootloaders should be now ready for receiving firmware (diodes LED 1 and 2 should go on).
Drag and drop binaries, example: blinky_nrf5340_app_zephyr_0x1000_2Hz.uf2 (located in uf2binaries folder)
Bootloaders should be now ready again for receiving new firmware.
Drag and drop binaries, example: blinky_nrf5340_net_zephyr_0x01004000_05Hz.uf2
Both cores should start executing flashed firmware, diodes LED3 and LED 4 should be blinking, LED3 controlled by application core and LED4 by networking core.
NOTE: nrfx drivers updated to newest release nrfx 2.11.0 from Nordic repo.