Skip to main content

Flashing QSPI through OSX

3 weeks ago

Flashing QSPI through OSX

Posted bymontea140 points 6 replies
0 upvotes

Hello Dialog,

I have been testing theDA14695 Development Kit – USBon my Mac and for that I have been following thesetup guide. I manage to debug the chip when flashing into RAM, however on page 38 I didn't see tools for flashing into QSPI underRun -> External Tools.I noticed there was a number of python scripts dedicated for this purpose under the SDK utilities/python_scripts folder, however they seem to only be supported by linux and win. Thus I suspect this is the reason why I cannot flash into QSPI from the SmartSnippets IDE. Thus my question, is there any way I could flash the QSPI using my Mac instead of Win/linux? Do you think it would be easily achievable or would I be blocked due to some binaries that need to be generated? I am fairly comfortable debugging python code, just want to make sure I won't be blocked by something fundamental at some point.

3 weeks ago

PM_Dialog

Hi montea,

Thanks for your question. You can use theezFlashCLItool to flash DA14695. The ezFlashCLI tool relies on the Segger J-Link™ library to control the Smartbond SWD interface. It is supported on macOS.

Thanks, PM_Dialog

3 weeks ago

montea 140 points

Thanks for the quick reply, I will give it a try today and tell you how it went!

3 weeks ago

montea 140 points

Ok, so good news - I can now flash the binary file into QSPI and thus the tool indeed works. However, I now seem to have a problem and not sure if this is related to the flashing tool or not. I was testing the ble_adv example and everything works whenever I build Debug-QSPI, flash it using ezFlashCLI and then debug it from within the IDE (I press continue to run without stopping and then can discover the device on the mobile app, can connect to it and read data, all good). However if instead I build Release-QSPI or even Debug-QSPI, then flash it and manually reset the board using reset button (skipping the debug from within the IDE part), I observe a very strange behavior. To begin, if I do not connect to the device, it will stop advertising after about 14 seconds. After that I can no longer detect it. If however, I connect to the device through the App, I get disconnected within 1-2 seconds and cannot connect to the device again unless I reset the board. Again, after I am forcefully disconnected, after a couple more seconds the device is no longer discoverable. I cannot imagine this being affected by to the flasher, however there are always possibilities. Just to note, flashing Release-QSPI or Debug-QSPI for bare_metal_blinky example, everything work without debugging it, thus it seems like this could be BLE issue too... Do you think I should open another ticket for this or maybe you are already aware of this problem and could point me in the right direction? thanks!

1 week ago

PM_Dialog

Hi montea,

谢谢你的问题。你能please provide some screenshots with the steps you are following so that I can understand it better?

If you would like to debug the project, you should build it for Debug-QSPI configuration ( not for Release-QSPI ).

So, if you build the ble_adv project for Debug-QSPI build configuration and program the QSPI flash, is it working fine?

你有一个定制的董事会或你正在使用的吗our DKs? If you are using the ble_adv project as provided by the SDK (without any modifications), this is working out-of-the box and the DA 469x should start adverting.

Thanks, PM_Dialog

1 week ago

montea 140 points

Hello Dialog,

To clarify, I am using the USB DA14695 Dev Kit from Dialog and I haven't modified anything within ble_adv project, just to confirm this I just re-downloaded the SDK with fresh examples. I recorded some videos displaying the steps I perform. For all of the steps I used Debug-QSPI build and the only difference is 1) I press debug within the IDE and then 'Resume' to let the sketch run forever and 2) I reset the board or power-cycle. Best to watch videos in this order:build_upload_and_debug.mp4(macbook recording) followed bydebug_on_smartsnippets.mp4(android phone recording). Then to show what happens when I do not enter debug within smart snippets and only power-cycle / reset the dev kit board the other two videoswithout_debug_without_connect.mp4andwithout_debug_but_connect.mp4.

Best Regards,
Montea

Attachment Size
build_upload_and_debug.mp4 9.27 MB
debug_on_smartsnippets.mp4 4.51 MB
without_debug_but_connect.mp4 2.38 MB
without_debug_without_connect.mp4 1.23 MB
accepted answer!

5 days ago

PM_Dialog

Hi montea,

Let's continue the discussion on this forum ticket :

//www.xmece.com/support-posts/da1469x-bleadv-examp…

I have replied there.

Thanks, PM_Dialog