How to specify custom uartboot.bin to cli_programmer when running an external tool

Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
Last seen: 2 years 3 days ago
Joined: 2020-09-22 23:05
How to specify custom uartboot.bin to cli_programmer when running an external tool

I am working on a custom board with a 32MHZ external crystal.  In order to use the cli_programmer with this custom board and crystal, a modified uartboot.bin second stage bootloader is required.  When operating from the command line this can be accomplished with -b option.   I have built the custom bootloader and moved it to binaries/uartboot_XTAL_32MHZ.bin  

Is there a recommended method for program_qspi_jtag_win.bat and other similar external tool scripts (e.g. erase_qspi_jtag_win) to pass parameters to cli_programmer?


I would like to avoid modifying cli_programmer so I can easily switch back to non-custom boards such as the EDK.


Last seen: 9 months 1 week ago
Joined: 2018-02-08 11:03
Hi There,

Hi There,

You could use the CLI commands in order to pass the correct version of the uartboot.bin Please check section 29.2. CLI for DA1468x and DA1469x family chips from the  SmartSnippets Toolbox user manual -  link is provided below. You could specify the path of the uartboot.bin

Thanks, PM_Dialog

Last seen: 1 year 8 months ago
Joined: 2020-10-08 18:34
In order to pass the correct

In order to pass the correct version, you must use the CLI commands. Please review section 29.2. 

CLI for family chips DA1468x and DA1469x from 

the user manual of the Smart Snippets Toolbox-connection below. 

You should define it.

the route to the.