Search Results

sort of, thank you. i see your point of the approach checking if the lock is in place. the issue with the EFM32GG is that after the chip lock (write a specific register), i cannot verify because the register will simply tell me its locked. unfortunatelly, this is not true unless after the write to the register, a HARD-reset is performed (either by SWD nRESET or by the /RESET pin). before that, the chip lock was just installed, but not active yet. Therefore, during production, i have a program wh…

Hi I need to be able to verify that the chip (MCU) is properly locked during production. so it basically is not this important what i do (example i could read a couple of words in flash, if i succeed, my verification would tell me that i did not lock my chip correctly. if i try any action on a locked cpu, the JLink will popup saying the chip is locked and if i want to unlock it (mass erase). can i somehow disallow the JLink.exe to generate this popup and rather give me some feedback (this will t…

Hello Im currently working on a system without any RTOS. We would like to test the new tool System View. I have so far modified the trace file, that ISRs are recorded OK, and the task description appears. As soon as i try to log the entry of a "task" entry and the exit, the system receives unknown packages and breaks down. The current setup looks like this and works OK, except the tasks are yet not visible, just the description. As soon as i define the C Source Code (1 line) and the C Source Cod…

Hi Im trying to use the SWO for printf via ITM_SendChar(); When i set a breakpoint within ITM_Sendchar() where it does write the character, it stopps. So writing seems OK. Also, on the J-Trace probe (i use the Target+Trace connector), the orange trace LED is on. But there is no output, i have tried: 1. No debug session, just SWO listening via the J-Trace probe via JLinkSWOViewerCL.exe: rem change to segger tools cd C:\"Program Files (x86)"\SEGGER\JLink_V614e rem JLinkGDBServerCL JLinkSWOViewerCL…

Hi Niklas, Question 1: The software enters EFM32 sleep mode 2 when there is no request by the application to stay awake and can be waken by IRQ. Although, im not sure if the MCU unit goes to sleep when you are in a debug session. Anyways, is this a requirement to stay the entire debug session awake to not-loose-connection? I could modify the firmware to stay awake. But still, it seems quite odd to my that the connection loss happens so randomly. Sometimes it took 6min, other sessions were workin…

Hi Im working with Atollic 7.1.2 and a J-Trace Cortex M Probe. My project is running most of the time for 3-6hours. Then, somehow the Debugger losses connection to the MCU: Error, cannot read register ..... I was wondering if Atollic may be the cause, so i also tried Seggers Ozone. Same result here. Do you have ideas what i have to suspect?