After some frustration, I have the smallest amount of progress, and thought I'd post it. Others may have similiar issues.
I've been having issues with the bootloader which can be configured to automatically reset the STM32 chip in flash mode, without the need to change the chip from bootload mode to flash mode and then push the reset button. In my case, a lot of the times after my code changes, the chip doesn't boot from the bootloader, and I have to change to flash mode and reset.
I'm pretty sure that the problem is with the C "linker" that was default for my project, so I've been looking off an on over the last several days for the linker script file, which is supposed to tell the C compiler where the different variables, constants, RAM based and Flash based code should be put within the STM32's 4 GB potential address space.
In my project, there is a default link file enabled, and I searched on it a couple of times, trying to find it so I could check the file contents and settings. Alas, it was reported not found by windows file search program.
Today, I did a more exhaustive manual directory search, and found some of the Raisonance sample projects have a normal link file, and some have a .elf.ld link file. This will be due to the different memory usages ofthe different Raisonance code samples.
I kept looking, and found a generic script file that was almost the same as that in the project defaults, only with the second and third letters of the file name transposed.
Just one small, but infuriating little error. I don't know that I would have the patience to develop on a platform like this if I was younger, and had not had the winning experiences I've had with assembler in 8-bit microcontroller platforms, but I don't loose sight of the promise at the end of this project. The C language itself is not bad, it makes a lot of use of symbols in a tightly packed manner, and so you can end up having an extremely dense piece of code fitting into one line, but then you can end up surrounding it with a { on the preceeding line, and a } on the line following to tidy the look of your code. Weird.
So, I now know where the linker configuration file is, and what it's real name is, I can move it to my project directory and fiddle with it. There's a lot of waffle in it...*
skip to main |
skip to sidebar
The SysTick interrupt gets busy:
I've done a big tidy up of my initialization code today, covering the APB bus clocks, after finding an error in my code.
The STM32 has two internal pheripheral buses, and when you enable a pheripheral, you have to manually set up software to enable the clock to that pheripheral as well.
After tidying up, making the code cleaner, and consolidating what I'd learnt so far about the pheripherals, the library, and C, my PWM started working reliably, including the dither PWM modulation and the throttle down of coil current when any axis has reached it's target.
Inspired by this success, and my tidier, more straightforward code, I went on today to implement servo drive signals and PWM control of my darlington pull down outputs.
This is what's going now:
4 x axis stepper motor control, smooth.
5 x channels PWM Transistor drive.
5 x servo motor drive (chunky resolution until I relocate code to a faster interrupt)
LCD, multi line.
2 x status LEDS.
The STM32 has two internal pheripheral buses, and when you enable a pheripheral, you have to manually set up software to enable the clock to that pheripheral as well.
After tidying up, making the code cleaner, and consolidating what I'd learnt so far about the pheripherals, the library, and C, my PWM started working reliably, including the dither PWM modulation and the throttle down of coil current when any axis has reached it's target.
Inspired by this success, and my tidier, more straightforward code, I went on today to implement servo drive signals and PWM control of my darlington pull down outputs.
This is what's going now:
4 x axis stepper motor control, smooth.
5 x channels PWM Transistor drive.
5 x servo motor drive (chunky resolution until I relocate code to a faster interrupt)
LCD, multi line.
2 x status LEDS.
No comments:
Post a Comment