Search Results

The buffer submitted as part of the FLM APIs e.g. Verify, Program, and MSP set by debugger are overlapping the R/W data of the executable. How is the address of buffer and MSP deduced by the debugger? Why would MSP overlapping the R/W data section?

I can see the following section in the object file: Source Code (3 lines) And following is included in the linked executable file: Source Code (1 line)I have checked that the compilation is happening for C, not sure why c++ constructor style static init is being included in the compilation and linking. This is the reason structure variable is not initialised. I am looking into why C++ code is being included

I am also working on polling method of the flash driver, and I am facing an interesting issue. I have a global structure variable whose members are all initialised. During run-time I can see that the members of the structure variable are not initialised. Any clues why this might be happening?

HW used J-Trace Pro Custom microcontroller with M33 connected to QSPI Flash SW used J-Flash Background I am working on flash loader FLM file for loading code to an external QSPI Flash. The chip on which FLM is loaded is custom with M33 processor. .*FLM + Data -> J-Flash (on PC) -> J-Trace Pro -> Custom microcontroller with M33 -> QSPI Flash Aim Use flash driver with interrupts within the FLM. The reason being that the flash driver has gone through substantial testing, and we want to keep the sam…