The engine monitor is on the back burner again. I want to build an IMU, since I have this board. If I can build an IMU, I should be able to build a little glass cockpit type display, similar to the Dynon or other EFIS app for the Android. The discovery board doesn't have any pressure sensors, but has a 3 axis gyro, a compass, 3D accelerometer, and a bunch of LEDs.
Using the gyro's, compass and accelerometers I should be able to build an accurate atitude indicator, a turn coordinator, a directional gyro indicator. If I can add pressure sensors, I should be able to build the whole "6-pack" from a standard instrument panel.
The secret to OpenOCD was at this site. Don't build the ftdi stuff, unless you have the ftdi dongle. If you are talking to the Discovery board, all you need is "stlink" that has been in OpenOCD since version 6.1.
The open pilot site has some resources for the discovery f3. There is a quad copter built using one.
Life is funny sometimes. Telnet, something I rely on, it is just there on all systems, old DOS (with some network kit), windows, all the unix systems I've used, mac and linux. For some reason, it isn't part of the default installation of Mandriva linux. How does one do anything without telnet. A simple urpmi and I have it, but weird!!
Anyway, I don't know if I added a link to this page, but it has a very high level set of instructions for building and loading software on the board, including using OpenOCD. He does:
openocd -f /usr/local/share/openocd/scripts/board/stm32f3discovery.cfg & telnet localhost 4444 reset halt flash erase_sectors 0 0 127 flash write a.out 0x8000000
To make that work, you really need to use the '&' to put open OCD in the background or use another terminal to do the telnet. Then you need to use different commands (maybe he had another version):
openocd -f /usr/local/share/openocd/scripts/board/stm32f3discovery.cfg & telnet localhost 4444 reset halt flash erase_sector 0 0 127 flash write_image imu.elf
I havn't figured out what offset to write the image yet. There is another version of write:
flash write_bank bank_id filename offsetWrite binary data from file to flash bank, starting at specified
byte offset from the beginning of the bank.
I think that will be something to play with in the future. The test_image shows it at 0x0800000, which may have been a typo from the initial site.
test_image imu.elf address 0x08000000 length 0x000004cc address 0x080004cc length 0x00000028 verified 1268 bytes in 0.000318s (3893.966 KiB/s)The darn GDB doesn't work though. It was built expecting libncurses.so.4, and I only have that version in /usr/lib64. I'll probably have to build that too, now. The demo code only increments a value by 5. Probably keeps the CPU pretty busy! Good way to test the debugger once I get that running.
The JXD S5110...
Well, it lived a hard life. It isn't dead, but well on the way. Today it was dropped, and the screen broke. This seems to have rendered the touch screen completely useless. I cannot figure out how to make the touch screen usable. The emulated games to work though. They mostly relied on the buttons around the screen, and they still work! The buttons emulate certain screen inputs, so you can unlock the device, and navigate the icons to select the games. It is funny, you know it is android, and you want to touch it, but that doesn't work. The joystick on the side does most of the driving, and the select button selects things. If someone made a good bumper for it, I'd probably buy another one.