About RLebe.1

RLebe.1 · 2020-02-25

Context: Using STM3Cube. STM2L431CC. (256KB flash, single bank)I have RAM code that successfully erase and program page 64 to 72. The same ram-code is then used to program page 0..8.The problem it fails to erase any page in range 0..63.No interrupts ...

RLebe.1 · 2020-02-26

Solved. look in .list for _veneer indirectly called function where indirection table was still in flash. Now all code in RAM and runs fine. The IDE fooled me because the memory was actually erase. Also the "Memory" menu of the IDE doesn't display ...

RLebe.1 · 2020-02-25

I am on a lead. Even the non-interrupt based code depends on SysTick and is interrupt based. Can't flush page 0 since the vector are there.So I need to copy vector in RAM, change the VTOR and it should work. The handler and some other support code...

RLebe.1 · 2020-02-25

Interrupts are disabled, the code doesn't use them. VTOR still points a page 0. systick is running but interrupts are disabled.Is here an issue with systick running. ST code does active polling using systick to measure timout time. (But not interr...

RLebe.1 · 2020-01-07

OK. So I downloaded Segger 's J-Link commander and successfully updated my probe firmware, erase and load my hex file.Thanks for the tip. I won't insist with STM32CubeProgrammer.

RLebe.1 · 2020-01-07

I am having the same problem. The IDE works fine but the programmer under Win 10 64 bit and latest Java gives same results.COne.1798 can you be more specific about your comment: "Make sure the component/dependent DLLs are findable from the location ...

User statistics

User Activity

Using SRAM2 ram-code, why can't I erase page 0 since I can erase page 64?

Re: Using SRAM2 ram-code, why can't I erase page 0 since I can erase page 64?

Re: Using SRAM2 ram-code, why can't I erase page 0 since I can erase page 64?

Re: Using SRAM2 ram-code, why can't I erase page 0 since I can erase page 64?

Re: STM32CubeProgrammer - No ST-LINK Detected

Re: STM32CubeProgrammer - No ST-LINK Detected