- Tue Jan 05, 2021 10:29 pm
#222105
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.
[*}SparkFun now maintains their own fork of the Ambiq SDK. It has a single submodule with additional Board Support Files that they wrote for their products. https://github.com/sparkfun/AmbiqSuiteSDK. Make sure to double check all paths in the document when doing this
[*}SparkFun now maintains their own fork of the Ambiq SDK. It has a single submodule with additional Board Support Files that they wrote for their products. https://github.com/sparkfun/AmbiqSuiteSDK. Make sure to double check all paths in the document when doing this
- When you first set up the project, the following is what you should see for the file structure
- Setup
- SEGGER_Flash.icf
- Source
- main.c
- System
- Cortex_M_Startup.s
- SEGGER_THUMB_Startup.s
- Use forward slashes (/) everywhere. I had a few things that got messed up when I used backslashes \
- You should only have two configurations: "Debug" and "Release". If you see more than that, you selected the option to create a project using both Internal and External Tools. (This threw me off for a while).
- Segger cannot assemble its own assembly file if you are using the SEGGER assembler. This is because Segger's assembler does not support multiline comments. The fix is to right click on the project->select options and set the compiler to gcc.
- All config options that you changed other than renaming the Code: Select all
DEBUG[\code] preprocessor definitions and setting the debug/optimization levels should be applied to the [i]common[\i] configuration. This is then set them for both the [i]debug[\i] and [i]release[\i] configurations. [*] The [i]memory segments [/i]option is no longer in the [i]build[/i] section. Instead it is in the [i]Linker [/i]section [*] The [i]additional linker files[/i] is now called [i]Additional Input Files[/i] I can't guarantee that all of this works, as I do not have a J-Link (yet). But it seems to run fine in the Simulator built into Embedded Studio.
- Setup