Search Results

Quote from SEGGER - Nino: “Send the Crash Report if prompted ” There was no prompt: SES was just hanging - not crashing. It looks like the hang was due to problems with the JLink (or its USB connection) - with SES in the Hung state, pulling the JLink USB connection allowed it to close. I had been using the JLink via a hub; seeing that pulling the USB released the Hang, I've stopped using the hub - and haven't had these problems since...

And again. This time, the power failed on the Target during a debug session - and SES just hung. Quote from awneil: “As suggested in those threads, deleting the settings.xml file did allow it to start again. ” It seems that is necessary, but not sufficient. After deleting the settings.xml file, the PC has to be restarted before SES will open. Deleting the settings.xml file without restarting the PC still leaves SES in the hanging state.

Somewhat related to: Segger Embedded Studio Hangs on Startup with "Building" in the Title Bar I had a debug session running, and the Target power failed. SES hung, and could not be closed; had to restart the PC. Fortunately, this time, it didn't trash the settings.xml - so I was able to use it again once the PC restarted. But the IDE really should be able to survive this kind of situation without needing a computer restart (or invoking Task Manager)!

Quote from SEGGER - Nino: “In most cases not ES is the culprit but third party tools and software ” Hmmm ... it's just done it again. I don't, AFAIK, have any 3rd-party software; I haven't done any VCS integration or anything. I had left SES in debug mode with the Target running while I switched to other applications. When I tried to switch back to SES, it would not receive focus. It could not be terminated from the Task Bar - the only way to stop it was from Task Manager. Having done that, it a…

Same symptoms as this: [SOLVED] Segger Studio frozen on "Building", after failed attempted at GIT And this: [SOLVED] [BUG?] [workaround] SES v3.30 hangs on startup when source control exe path set incorrectly But I hadn't done anything to do with Git (or any other) integration. In fact, I hadn't done anything to or with SES at all since it last opened successfully. I didn't search any further, but it seems that SES is prone to corrupting its settings.xml file and, thus, getting into this unusabl…

Can the J-Link Remote Server run on a Raspberry-Pi ? And, if so, what are the requirements? and where can I find instructions? My main development machine is Windows-7, but I want to be able to debug my Target when it is far, far away (it's a radio device; I'm doing range testing). Something like this: Brainfuck Source Code (9 lines)

Have you seen devzone.nordicsemi.com/b/blog/…two-ble-examples-together on the Nordic site?

Quote from feistyz: “Any ideas what might be causing this? ” As it's an nRF chip, are you trying to debug a project with a SoftDevice? In that case, stopping at a breakpoint in your application is liable to crash the SoftDevice - which could lead to such problems...

Quote from Back in Feb 2015, SEGGER - Johannes: “We will add timestamps to RTT Viewer in a future version ” Any progress on that?

What about the "$(RelLinkerScriptPath)" issue?

Yes, it is a project from the Nordic SDK. Even an unmodified SES project from the Nordic SDK does not work: See: devzone.nordicsemi.com/f/nordi…icting-types-for-_putchar And: devzone.nordicsemi.com/f/nordi…---segger-embedded-studio but perhaps that should be a separate topic ...

If I replace the "$(RelLinkerScriptPath)" macro with the literal scatter file path, the link now fails with Quote: “L6236E: No section matches selector - no section to be FIRST/LAST. ” This seems to be because the import has not imported the original startup file - arm_startup_nrf52.s - but has instead used its own Cortex_M_Startup.s But the Scatter file has not been updated to match this change - hence the link error. So it would seem that this "import" is fatally flawed and not usable.

If I do 'Open Solution in Editor', I see: Quote: “external_link_command=""$(KEIL_TOOLKIT_DIR)/ARMCC/bin/armlink" $(LinkOptions) --scatter="$(RelLinkerScriptPath)" $(Objects) -o "$(RelTargetPath)" --list "$(RelMapPath)" --map" ” In the build output, I see: Quote: “Linking ‘nrf52832_xxaa.axf’ C:/bin/Keil/MDK/525/ARM/ARMCC/bin/armlink --cpu cortex-m4 --fpu fpv4-sp --diag_suppress 6330 --scatter=$(RelLinkerScriptPath) ./_build/main.o ./_build/host_comms.o ./_build/peripherals.o ./_build/timestamp.o …

The Scatter file does exist - in the same place that the original Keil project used it.

After importing a Keil MDK v5.25 Project (for Nordic nRF52832) and then trying to build the 'External' configuration. In fact, there were a couple of other failures: 1. The path to the CMSIS headers - core_cm4.h etc - was not added; 2. The --c99 option was not added. But, having fixed them, I am stuck with the Link failing: Quote from The Linker: “L6031U: Could not open scatter description file $(RelLinkerScriptPath): No such file or directory ” So 2 questions: 1. Where can I see what RelLinkerS…