Hi Andrzej,
Again, thanks for your help. Next step is to build the blinky app.
Here is what I did:
The source did not change, I verified that LED_BLINK_1 is indeed connected
to P1_1 pin and specified in the BSP.
I tried to set breakpoint in main, but something isn't working. Any help
would be very appreciated.
newt target show da1469x_blinky
targets/da1469x_blinky
app=apps/blinky
bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
build_profile=debug
newt run da1469x_blinky 0
...
Reading symbols from bin/targets/da1469x_blinky/app/apps/blinky/blinky.elf
...
0x20000d04 in g_os_main_stack ()
Resetting target
0x20000262 in da1469x_m33_sleep_state ()
(gdb) b main
Breakpoint 1 at 0x16009a4c: file apps/blinky/src/main.c, line 46.
(gdb) c
Continuing.
On Tue, Aug 6, 2019 at 6:18 PM Dr. Juergen Kienhoefer <juer...@aircable.net>
wrote:
> Thank you for your help. So far so good, it seemed to work.
> Here are my steps loading the boot loader.
> Will continue with the app later. My plan is to build the blemesh app from
> Nimble on this board.
>
> pip3 install click cryptography
>
>
> newt new NewtBLE
>
> cd NewtBLE/
>
>
> add external repositories to project.yml
>
> repository.juullabs-oss-mcuboot:
>
> type: github
>
> vers: 1-latest
>
> user: JuulLabs-OSS
>
> repo: mcuboot
>
>
>
>
> Bootloader
>
> newt target create da1469x_boot
>
> newt target set da1469x_boot app=@mcuboot/boot/mynewt
>
> newt target set da1469x_boot
> bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
>
> newt target set da1469x_boot build_profile=optimized
>
>
> newt target create da1469x_flash_loader
>
> newt garget set da1469x_flash_loader
> app=@apache-mynewt-core/apps/flash_loader
>
> newt target set da1469x_flash_loader
> bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
>
> newt target set da1469x_flash_loader build_profile=optimized
>
> newt target set da1469x_flash_loader
> syscfg=FLASH_LOADER_DL_SZ=0x10000:RAM_RESIDENT=1
>
> newt install
>
>
> newt build da1469x_boot
>
> newt build da1469x_flash_loader
>
>
> newt load da1469x_boot
>
>
> Loading bootloader
>
>
>
> On Tue, Aug 6, 2019 at 4:52 PM Andrzej Kaczmarek <
> andrzej.kaczma...@codecoup.pl> wrote:
>
>> Hi,
>>
>> On Wed, Aug 7, 2019 at 1:17 AM Dr. Juergen Kienhoefer <
>> juer...@aircable.net>
>> wrote:
>>
>> > @mkiiskila: Thanks for providing the DA1469x board support.
>> > I'm putting together a tutorial how to get Newt working on these boards
>> > with Nimble.
>> > So far I gathered these bits of information. Apparently, it's not quite
>> > enough.
>> > Please help me getting it complete:
>> >
>> <snip>
>>
>> > FLASH LOADER
>> >
>> > newt target create da1469x_flash_loader
>> >
>> > newt target set da1469x_flash_loader
>> > app=@apache-mynewt-core/apps/flash_loader
>> >
>> > newt target set da1469x_flash_loader
>> > bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
>> >
>> > newt target set da1469x_flash_loader build_profile=optimized
>> >
>> > newt target set da1469x_flash_loader
>> > syscfg=FLASH_LOADER_DL_SZ=0x10000:RAM_RESIDENT=1
>> >
>> >
>> > APP
>> >
>> > newt target create da1469x_blinky
>> >
>> > newt target set da1469x_blinky app=apps/blinky
>> >
>> > newt target set da1469x_blinky
>> > bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
>> >
>> > newt target set da1469x_blinky build_profile=debug
>> >
>> >
>> > LOAD FLASHLOADER
>> >
>> > >>> must run "newt run da1469x_blinky" first to create
>> flash_loader.img,
>> > then load it
>> >
>> > newt load da1469x_flash_loader
>> >
>>
>> This is not how it works. You need 3 targets: flash_loader, bootloader and
>> app. What you are missing is a bootloader:
>> newt target create da1469_boot
>> newt target set da1469x_boot app=@mcuboot/boot/mynewt
>> newt target set da1469x_boot
>> bsp=@apache-mynewt-core/hw/bsp/dialog_da1469x-dk-pro
>> newt target set da1469x_boot build_profile=optimized
>>
>> You need to load bootloader and app to flash and this is where
>> flash_loader
>> is used, i.e. you do not load flash_loader, but download script requires
>> it
>> to be able to load app and bootloader to flash. The easiest way to do this
>> is:
>> newt load da1469x_boot
>> newt create-image da1469x_blinky 1.0.0
>> newt load da1469x_blinky
>>
>> "newt run da1469x_blinky 1.0.0" will create image for app and load it and
>> then start debugging session (as with newt debug) so can be used as a
>> shortcut for app, but bootloader needs to be loaded separately.
>> Also to load bootloader you will need Python 3.7 (3.6 or older won't work)
>> installed because part of bootloader download script which creates product
>> header is written in Python. Without proper product header internal
>> bootloader won't boot our bootloader (mcuboot) and app won't start.
>>
>> Once you load both bootloader and app, it should boot properly.
>>
>> Best,
>> Andrzej
>>
>
