Search Results

Sorry about that, I thought the project should already have the correct chip version selected. After switching to the suggested chip, the code progresses further but still cannot connect to MQTT broker. I do see: Write failed @0x08064800, read value=0x00000000, expected=0x2d2d2d2d Error writing 2048 bytes at 0x08064800 Should I be worried

ping?

Sorry about that, here is the right log.

I am trying to run Amazon FreeRTOS demo on STM32L4+ Discovery kit IoT node, but getting the "Active read protected STM32 device detected" message. If I choose to perform an unlock, the code ends up in HardFault_Handler. So in both cases, whether if I choose to perform the unlock or not, I cannot see the MQTT messages in the AWS console. Have not made any local modifications to the code except the needed credentials. I am using J-Link V6.98 Attaching what I think is the JLink log

I recently acquired a couple of Jlink Ultra+ probes for debugging my K50DX256CMC10 based product. I use FreeRTOS v9.0.0 and Atollic TrueStudio, the thing is that I am having problems with debugging the application while the processor is in its LLS mode, the debugger loses conection and restarts the application. I read in the manual that I need to add “monitor exec LowPowerHandlingMode = 1” to the start configurations and disable all periodic memory accesses. I cant find how to do it, I tried add…