Skip to main content

Linux: SmartSnippetsStudio2.0.7 crashes after first run

1 month ago

Linux: SmartSnippetsStudio2.0.7 crashes after first run

Posted bymark@memfault.com25 points 6回复
0 upvotes

I'm running Ubuntu 20.04 (Linux) and I've installed SmartSnippetsStudio2.0.7 (many times now) with SDK version DA1468x_DA15xxx_SDK_1.0.14.1081, hotfix 002 applied.

我第一次运行SSS它允许我导入所有现有的项目,并完成所有的事情。

However, if I exit and re-start SSS it simply crashes after the splash screen disappears and gives me an error dialog (see attached file, smartsnippet-failure.png). I've also include the .log file renamed so it could be uploaded.

If I completely remove the .metadata folder I can run SSS again but of course all the projects are gone so I have to re-import them and the next time I try to use SSS it crashes again.

我得到SSS耐腐蚀合金h after the first run by simply changing any configuration like "insert spaces instead of tabs". Doing just that and restarting causes the crash.

I've even cleaned out my bash environment so that it only has this:

bash-5.0$ env PWD=/home/user/DiaSemi/DA1468x_DA15xxx_SDK_1.0.14.1081 DISPLAY=:0 SHLVL=1 _=/usr/bin/env

SSS still crashed so I don't think it's some environment issue but who knows.

谢谢你的帮助。

Attachment Size
Error dialog when SmartSnippets fails to load 14.05 KB.
这generated .log file renamed to log.txt 505.77 KB

1 month ago

PM_Dialog

嗨马克,

Thanks for your question online and for your interest in our BLE solution

这SSS v2.0.7 is not recommended with the DA1468x product family and SDK1.

我的建议将是使用SSS v2.0.16 - 您将在DA1468x产品页面的“开发工具”部分下找到它:

https://www.dialog-seminile.com/produ亚博电竞菠菜cts/bluetooth-low-energy/da14682-and-da14683#tab-field_tab_content_resources.

Could you please give a try with that version and let us know if this resolves the issue?

Thanks, PM_Dialog

1 month ago

mark@memfault.com 25 points

Thank you. That works MUCH better. No crashing and the toolbox seems to do something. I'm still hardfaulting after programming the QSPI and then connecting with the debugger but hopefully I can figure that out. Maybe because there are no QSPI partitions? Whatever they are.

1 month ago

mark@memfault.com 25 points

QSPI:我无法通过sigtrap。我就像文件一样,我已经设置了一切,但我一直在这里看到附加的文件对话框 - sigtrap。我已经为`freertos_rtt`项目构建了QSPI调试配置,并通过J-Link QSPI配置基于SmartBond的基于SmartBond配置的调试配置。无论eclipse要求jlink要编程ELF文件还是使用外部`program_qspi_jtag_linux`应用程序,我最终会出现同一地址,然后不要在Eclipse中下载ELF。

What am I missing about programming this DA14683 chip? What is the correct sequence of steps to get an ELF file into the chip so that it can be debugged?

Attachment Size
Dialog SIGTRAP 30.13 KB

1 month ago

PM_Dialog

嗨马克,

为混乱道歉。这SmartSnippets Studio V1.6.3 for Linux操作系统推荐为DA1468X和SDK1。我们将更新“开发工具”部分。因此,请安装SSS v1.6.3并尝试开始调试项目。

这"SIGTRAP, Trace/breakpoint trap" is not a real crash, but it indicates that the Jlink debugger resets. If this issue still exists with SSS v1.6.3 :

1. Can you please indicate if you are able to erase the QSPI Flash via JTAG by executing the erase_qspi_jtag_linux script?

2. Then, can you program it properly executing the program_qspi_jtag_linux script? If yes, does the device boot?

3.您正在使用的Segger J-Link版本是什么?

4. Please navigate to the debug configurations and make sure that you have placed the .elf file (see attached)

Thanks, PM_Dialog

1 month ago

mark@memfault.com 25 points

谢谢回复。

I can erase and program the QSPI Flash using the scripts that hook into External Tools. The device does boot and runs. I'm running SEGGER J-Link GDB Server V6.96 Command Line Version.

I have finally figured out what is going on. I cannot tell JLinkGDBServer how to program the QSPI flash like I did for the NXP4088. With that chip, any writes into the QSPI mapped memory address range caused the chip's QSPI controller to do the write so GDB didn't need to do anything special. For this DA14683 chip there seems to be some custom way to program the QSPI flash that GDB cannot be taught. So, I now use the cli_programmer binary and it works.

I now have a .gdbinit macro that calls cli_programmer appropriately. This seems to be working well.

monitor reset
shell cli_programmer --prod-id DA14683-00 gdbserver write_qspi_exec myproject.bin
file myproject.elf

I can use Eclipse to build the new binaries but I've given up on SSS (Eclipse) for debugging. It just doesn't work (sits in the SIGTRAP).

I have not tried SSS v1.6.3. Since things seem to be working so maybe I won't bother. I'm using my own installation of Eclipse (Version: 2020-12 (4.18.0)) to do the builds now anyway so I'm not even using SSS.

1 month ago

PM_Dialog

嗨马克,

Glad that you are able to program the DA14683 and thanks for the indications.

Thanks, PM_Dilaog