cancel
Showing results for 
Search instead for 
Did you mean: 

Application runs after flashing from STlink, but not after power cycle

Shiv09
Senior

Hello All,

 

I am using touchgfx for one of my application using on STM32757I-Eval kit.

I am facing issue with running the application after successfully flashing the application, first time if I load from STM cube programmer, I can see the Program is running on display, but as I remove the Power from usb stlink and reconnect it back the Application is not loading and running.

Could you please help me to understand why it happens and how can I rerun the application so that I don't have to program it again and again.

Please let me know how to resolve it ?

 

Regards,

Shiv

11 REPLIES 11

Hello @MM..1 ,

 

Yes, Done for Flash Mode and System Mode, for both of them have pointed the Address to 0x08000000, Now whether it's in flash or System, when a fresh code is flashed from STMCubeProgrammer I can see from both Flash and System the Application is running, Even after pressing reset from both modes its running, 

 

But same trouble when power cycle is done, application don't run. 

 

I tried to check if Application data at 0x08000000 exist after power cycle, got a doubt if flash itself is getting erased, even this is looks good, the application still exist after power cycle.

 

If there is some more information required to verify then please do let me know.

 

 

Shiv09_0-1765177320633.png

 

Shiv09
Senior

Hello @emmataylor ,

 

Thanks for the reply !

Yes agreed, such issue could happen because of the points you mention. Below are the responses might be this could give more clarity of issue. if you need any additional information then please let me know.

 

1. Verify the BOOT0/BOOT1 pins – make sure they are configured to boot from flash memory.

-> Yes the SW1 position is at FLASH, Pointing at 0.  BOOT0 Jumper is OPEN(no jumper connected, JP3).


2. Check the linker script – confirm that the application is being written to the correct flash start address.

-> Attached 2 files, this might provide clue, 1 is for the Flash.ld and other is for RAM.ld


3. Make sure Option Bytes are correct – especially the Read-Out protection and Write protection settings.

--> Attached below 2 images for the settings.


4. Try erasing the full chip and flashing again to ensure no previous code is interfering.

-> Yes tried to erase flash every time I am flashing a new code (by clicking Erase flash  menory -> Full chip erase,  even Erase external memory).

 

Shiv09_0-1765178473977.png

Shiv09_1-1765178529936.png