(I had to change the extension, as the forum does not allow uploading files with the. The empty set of points that for the bluetooth subsystem are not configured.ĭoes anyone know what the reasoning is for the last two bullet points? I have uploaded the startup files below for reference.Additional IRQ vectors are defined at the end of the vector table.The Vector Interrupt Definitions are done in a seperate file.The CMSIS Files are in a folder that SES creates in the project. However, there are a couple of notable differences that the Segger template provides from what Robin's tutorial documents suggest. The end result is that if you use it, you will need to do a lot of tweaking to the configuration files to get Sparkfun's examples working, as they use defines that are not in the older CMSIS versions (related to IC revision checking). They use a older version of the Ambiq CMSIS files than you can get through Sparkfun. So I tried using the Ambiq templates that Segger now has built in. But I suppose that statement deserves a thread of its own. In general, I am not a fan of the Apollo3 timer functionality. If you hit a breakpoint, the timers keep counting. The Apollo3 processor does not support that. That allows you to singlestep and poke around and then take off again without disturbing the time. For example, on most other processors I have worked with, when you hit a breakpoint, you can arrange for the timers to stop counting whenever the processor is halted. I still encounter problems debugging, but they are due to limitations of the Apollo3, not Segger. There are other choices now, but I am used to the Segger development environment, and actually like it a lot. Looking back, when I started with the Artemis, Segger was the only game in town for debugging an Apollo3 (at least that I could make work). Does it mean that we fix the bug in the Sparkfun fork? Is that not a recipe for needless divergence? I don't really want to go down that road. Their bug management system says that the issue is "open". I have reported a bug in the 2.5.1 SDK to Ambiq over 3 months ago and never even received acknowledgement of the issue. I don't know what to make of Sparkfun maintaining their own fork of the SDK. I have worked around the missing routines in the one project I have migrated from V4 to V5, but it is an annoying enough issue that I am not migrating the rest of my projects until the library fully exists. That seems like a serious misstep to me, but I don't work at Segger and don't know what is going on inside their engineering & marketing heads. Segger says that the entire library will be released at some point, but it is not clear when that would be. Reading the Segger forums showed that I am not alone. In particular, it is not fully implemented so certain runtime routines I had been using don't exist anymore. The problem is that the improved runtime library got released a bit too early. The downside is that as part of the V5 Segger release, they "improved" their Segger runtime library, and as of V5, it is the only one you can use. I think that a V1.9 doc would be a lot simpler. I think that Segger V5 simplifies a lot of the process described in that document. At the moment, I am waiting for Segger version 5 to settle down a bit. There were a couple mistakes and some improvements incorporated between 1.6 and 1.8. All config options that you changed other than renaming the.The fix is to right click on the project->select options and set the compiler to gcc. This is because Segger's assembler does not support multiline comments. Segger cannot assemble its own assembly file if you are using the SEGGER assembler.If you see more than that, you selected the option to create a project using both Internal and External Tools. You should only have two configurations: "Debug" and "Release".I had a few things that got messed up when I used backslashes \ When you first set up the project, the following is what you should see for the file structure.Make sure to double check all paths in the document when doing this It has a single submodule with additional Board Support Files that they wrote for their products. [*}SparkFun now maintains their own fork of the Ambiq SDK. Just looked through the 1V6 guide, and I thought it was great, but I ran into a few issues (Though it probably does not help that I have never used SES before ) that were not really covered by the guide that I wanted to mention in case others have the same issues that I did.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |