Search Results

I have an application with a separate bootloader and app partitions. If I enable RTT in the bootloader, I will not see the RTT Logs on the RTT Viewer once I jump to the app. If I disable the RTT on the boot, then I see it in the app, but now I have no logs for the bootloader. Is there are way to restart the RTT to allow logs to be seen on both applications? I have tried running the RTT Init at the start of each applications. Perhaps I need to specify a fixed RAM location for the RTT ram buffer s…

I have a project in SES 8.10b that disconnects when I hit the wait for interrupt command. It pops up immediately with "JLINK ERROR" Part: MSPM01306 Compiler: SEGGER Linker: GNU OS: Mac OS 14.2.1 System: Macbook Pro M1 Max If I use RTT Viewer, the JLINK does not disconnect and it reconnects when an interrupt source wakes the part. Is there a setting I need for the JLINK to wait for reconnect when the device wakes up from an interrupt source? I have tried with and without the STANDBY call, and it …

Attached is a picture of the part. TI told me it was a production revision. I read some of the pre-production revisions had issues. I have attached a demo hex and the linker script (change extension from .txt to .lds)

Hello, I am developing on the MSPM0L1306 Launchpad board. After several erase/write cycles using the J-Link and debugging with the RTT, the MSP0l1306 locked up and will not reflash. I looked through the TI forums and it seems like this can be an issue if the NONMAIN flash section is flashed. I am not touching this section in my code. I have had two separate boards lock-up when using a J-link only. On my third board, I have only used the TI debugger and it has not locked up. I am concerned there …

I have a large nRF52840 project on the NRF5 SDK and the erase by sector was taking longer than the reflash. Erasing all is faster than erasing by sector for this part.

Embedded studio version 5.70a has an "Erase All" option available in Project Options->J-Link->Erase All I do not see this in version 7.32. Is there another location where this option exists in 7.32? Thanks!

I am trying to convert an old NRF52840 project that works with 5.70a to work with the lastest build of 7.12a. However, it seems like the <stdint.h> is defining the integer sizes incorrectly. This code: C Source Code (1 line) Gives this warning: Source Code (1 line) This is a 32-bit processor. An unsigned int should be equal to an uint32_t correct? It seems like an "uint32_t" is defined as a long unsigned int ======= Adding Tests Size Info =========== C Source Code (11 lines)Source Code (4 lines)

Hello, I have the headless SES install working with the "--copy-files-to" command, but I need to automate this in a docker build to automatically accept the license terms. This thread seemed to indicate this was possible: [SOLVED] Headless Install - Nixos installation Thanks!

Here is what I tried. It sure *seems* to work, but I would like to know if there are any pitfalls to this solutions. I added a FLASH_INIT section in the memory map XML Source Code (11 lines) Then I added the .vectors to this section in the flash_placement: Smarty-Template (3 lines)It seems to format the binary file correctly. Please let me know if I need to add anything else to this init section for it to work properly.

Nino, Thanks for the reply. However, I still need to be able to modify where the code is placed due my bootloader configuration. I have to be able to re-flash in the field via the on board ROM bootloader chip from a wireless device. As you know, wireless communication and battery powered devices can be very un-reliable so it is not safe for me to have to erase this section of flash. If the bootloader erase is successful but a subsequent write to 0x400 is not, then the device will require a full …

Hello, I porting a Keil project using the NXP KL17Z128 to SES. I am trying to change the flash start address and sizes as follows: Flash Segment 1 (ARM start code)- start 0x0 size 0x400 Flash Segment 2 (Program Code) - start 0x1000 I have edited MKL17Z128xxx4_MemoryMap.xml to <MemorySegment name="FLASH" start="0x00001000" size="0x00020000" access="ReadOnly" /> Problem: However, inspecting the disassembly and *.bin file, there is still code being placed between 0x410 and 0x1000. It seems like Emb…

I downloaded ES version 3.40 and I am having one issue that is hard to find a good work around. In the find and replace window, results now show up with their (very long!) absolute path. This makes it much harder to read the search results. The same project in 3.34a finds the results listed very neatly underneath each *.c or *.h file. Do I have a setting set differently in 3.40 that makes it search this way? Thanks!

Hello, Is there a way to copy an existing build configuration in order to create a new build version in SES? Thanks, Luke