Posted by dalewheat on 2017-01-30 17:59

@diabolo38

Thank you for replying to my request for assistance/clarification.

“why do you want to rewrite everyting ?”

Because I can. Because I’m interested in how things work. Because I want total control over my software. Because I don’t completely trust other people’s code. Because I don’t want to be beholden to anyone’s particular licensing scheme. Because I want to teach other people how to do these things for themselves and not rely on other people’s past efforts. There are other reasons but those are some of the main ones.

” Want template startupxxx.s will do fine no? ”

Yes, it most certainly does work, and I have often started projects using this proven, working code. However, in the dim past (circa 2007) there were no “new project wizards” that created instant ARM Cortex-M projects, and I had to figure out how all this worked, with the assistance of other, like-minded individuals:

http://e2e.ti.com/support/microcontrollers/stellaris_arm/f/471/p/44559/157356

I then went on to use this newly-gained knowledge to write a two-part article that was published in Circuit Cellar magazine, issues 229 & 230 (August & September 2009), titled “Get Started With Embedded Development”, which was well-received, and featured the STM32 line of ARM Cortex-M3 devices.

“wihout this “common” .s i would make sure “do not use standard start file” linker option is chedk that can make standard symbol that you could miss to come from standard crt0 and play you tricks .”

You are correct: this has been done.

“are your sure your “vector” section is well placed in the ld at cpu reset vector adress ?”

and

“Are you sure sp is setup by default ? in most reset handler s file that is set at very first desite “estack in the vector table” ”

Yes. As I stated in the original post, the application does work. Power-on or hardware reset started the LED blinking at the appropriate rate. The only problem is that the SW4STM32 debugger will not debug the reset handler code, nor does it seem to even execute it.

I’ve successfully compiled and debugged this little program using Atollic TrueSTUDIO v7.0.1, both the “Lite” (free-as-in-beer) and “Pro” (commercially licensed) versions, which also use Eclipse+GCC.

Did you try to reproduce the problem using the file I attached? You will also need my custom linker script, attached below.

Any insight into why the SW4STM32 debugger won’t debug this application will be appreciated. I was interested in learning how to use the SW4STM32 offering because it is referenced in some of STmicro’s literature for software development. I understand that not everyone can budget a commercial software IDE for hobbyist projects, and I thought this one might be a good recommendation for future developers. The feedback I’ve received from this forum has also helped me further my own projects.

Dale