OK bit of a code post
First open a terminal to start up the listener so i can program the board
$ cd stlink.git/
$ sudo ./gdbserver/st-util fu bar
next to send a program to the board in a new terminal
cd ~/stlink.git/example/blink
make CONFIG_STM32F4_DISCOVERY=1
$ arm-none-eabi-gdb
(gdb) target extended localhost:4242
(gdb) load blink.elf
(gdb) continue
Control-C stops the program
and quit ends and starts the program on the board automagicly.
Now this is just with an example and using the post below to get my build environment up and running.
Had no issues with programing or anything but when i reset - i.e unplugged the board the program was not running. Firing up the gdb and repeating these commands
$ arm-none-eabi-gdb
(gdb) target extended localhost:4242
(gdb) continue
and only one led blinks. Not the 4 in the center of the board.... More to follow as i figure this out.
Might help if i program the flash not the ram eh?
./flash/flash write path/to/file_name.bin 0x8000000
works just fine! With my ability to program the board and upload code to both the flash and the ram, I am all set not to go back to windows and have to finish deployment from there to the target boards. Next on the chopping block to is to gleam out how to do proper usb identification for my device. I.E a usb CNC Machine with Serial Communications. Which hopefully is not that hard. Seems someone has do a bit of CNC gcode converting software for stm32 already so after i figure out this usb crap i am going to have a look at that.
First open a terminal to start up the listener so i can program the board
$ cd stlink.git/
$ sudo ./gdbserver/st-util fu bar
next to send a program to the board in a new terminal
cd ~/stlink.git/example/blink
make CONFIG_STM32F4_DISCOVERY=1
$ arm-none-eabi-gdb
(gdb) target extended localhost:4242
(gdb) load blink.elf
(gdb) continue
Control-C stops the program
and quit ends and starts the program on the board automagicly.
Now this is just with an example and using the post below to get my build environment up and running.
Had no issues with programing or anything but when i reset - i.e unplugged the board the program was not running. Firing up the gdb and repeating these commands
$ arm-none-eabi-gdb
(gdb) target extended localhost:4242
(gdb) continue
and only one led blinks. Not the 4 in the center of the board.... More to follow as i figure this out.
yep i am stupid
Might help if i program the flash not the ram eh?
./flash/flash write path/to/file_name.bin 0x8000000
works just fine! With my ability to program the board and upload code to both the flash and the ram, I am all set not to go back to windows and have to finish deployment from there to the target boards. Next on the chopping block to is to gleam out how to do proper usb identification for my device. I.E a usb CNC Machine with Serial Communications. Which hopefully is not that hard. Seems someone has do a bit of CNC gcode converting software for stm32 already so after i figure out this usb crap i am going to have a look at that.
No comments:
Post a Comment