Closed tdaileygithub closed 4 years ago
Thank you for your feedback. You're right that you should not copy the board definition, but I think I did it this way ( I just wanted to move on). I had to cut a few corners to get it compiled. But it eventually did.
Later on I ran into trouble uploading over the air, where he would not swap the images.... (it did upload though!)
At first I thought it was spi-flash-related, but this was not the case.
~# mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image list Images: image=0 slot=0 version: 1.6.0 bootable: true flags: active confirmed hash: 661bbd5ff74e4efeaadde3b76940dc67bafdd36037973888dbcd0d476a4be113 image=0 slot=1 version: 1.8.0 bootable: true flags: pending permanent hash: 5fc02cc9042c750d9329a82948e9d92ae1f26a9e3ebd3be53c3aef78e699f979 Split status: N/A (0)
Excellent Work!
I successfully flashed all your zephyr sample apps except mcuboot on my pinetime dev kit!
However, I am having build/env var issues with zephyr+mcuboot build/documentation.
TLDR
Results in:
Which makes sense as mcuboots directory does not have that board. Is there a way to merge board dirs/link.
If I copy the pinetime board configs into ZEPHYR_BASE... it gets further but this can't be right.
I am booting up on both zephyr and mcuboot so if there is a simple environment variable that is omitted from the docs that would be a great addition.
Cool Stuff. Be well.