silver13/h8mini_blue_board

H8_mini blue board version firmware

H8mini Blue board version###

Specific Blue instructions: https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995

Warning: new blue board version is not compatible with this firmware as it uses an obscure PAN163CX microcontroller with integrated XN297L. To distinguish it from the supported version look through the battery bay to determine the antenna pin location. On older boards it was on the side, on the newer it's centered, see https://www.rcgroups.com/forums/showpost.php?p=40328262&postcount=14761 .

From rcg user kmtam

Hi all, I finally got the h8mini blue board erased and flashed to Silverxxx firmware after zillion times of tried and error. The board's labelled wrong with the CLK and DAT got swapped....

This is how I got it work from the STLINK to the H8mini blue board: SWDIO->CLK GND->GND SWCLK->DAT

Thanks Silverxxx for this wonderful firmware! Cheers!

From rcg user ketsa

Thanks!!! I finally managed to flash my blue board.

It was not straightforward, I tried the suggested connections and was still getting "ST-LINK USB communication error."

I then found a file in my keil directory named "ST-LinkUpgrade.exe" So I Upgraded the FW of my ST-link to "V2.J24.S4 > > > STM32+STM8 Debugger"

Then i was getting a different message : "no target" hmm. progress. but still not flashing. Then I removed the battery, plugged it in and it erased !

I tried to flash : "no target."

Replug battery, and it flashed !

From rcg user silverxxx

I made a blue board quad to see what's happening with the flashes.

So far I found out that it does indeed stop working after the st-link gets disconnected from usb. This seems some software issue, maybe with keil.

The st-link starts working after it is used in some other way , such as: flash another quad with keil(not blue board) , use > the "st-link utility" and connect to a board(even blue), use openocd and connect to a board (even blue).

After the "st-link usb communication error" comes up , you have to disconnect the st-link and reconnect it, or the above > fixes do not work.

Another find was that the nucleo built in st-link does not have this issue. It also does not get detected by the st-link firmware updater. A nucleo board is about $12

I'll have to find a more permanent solution, although openocd could be made a shortcut.

The last 2 posts refer to windows and keil only

This port supports both acro only and dual mode. To enable acro only, an option exist in config.h.

The H8 board - blue version - uses a stm32f030 and a XN297L 3 wire radio. The XN297L is differerent from the XN297 in that is supports 250K rate, and the debug registers are different. XN297L datasheet (use google translate)

Flashing instructions

CG023 instructions: http://www.rcgroups.com/forums/showthread.php?t=2634611

Specific Blue instructions: https://www.rcgroups.com/forums/showthread.php?2721755-H8-blue-board-flashing-instructions#post35501995

Linux/gcc version

The gcc version compiles close to 16k, and may need turning off features in order to make it fit. Read install.md for additional information.

Wiki

http://sirdomsen.diskstation.me/dokuwiki/doku.php?id=start

Updates:

01.12.16

• devo telemetry
• high angle - up to 90 in level mode
• autovdrop
• trims on stock tx for switching

11.08.16

• added tx autocenter for stock tx
• added extra devo channels that were MIA
• bluetooth beacon was added previously

03.07.16

• added updates from cg023 build
• now using hardware i2c for full speed (1 Mhz)

30.05.16

• fixed low rates control issue in yaw+roll

19.05

• added gestures
• changed imu from the experimental one that somehow made it in, to the old one

11.05

• added linux compilation support

10.05

• minor update
• additional protocols now work

h8mini_blue_board's Issues

How do the flips with this firmware?

I flashed this firmware, because I like to have the ability flying with acro mode.

However I was wondering how I can do the flips on level mode again? The method I used with the stock firmware doesn't do anything anymore.

I'm using the stock transmitter.

Target not created.

Hi there,

I think I'm very close. When I click Build target (F7), I get this error in the log:

.\Objects\h8blue.axf: Error: L6218E: Undefined symbol rgb_init (referred from main.o).
Not enough information to list image symbols.
Finished: 1 information, 0 warning and 1 error messages.
".\Objects\h8blue.axf" - 1 Error(s), 0 Warning(s).
Target not created.

I tried other projects and build them, which succeeded fine. :(

Flashing under Linux

Hi There,
Compiling on Ubuntu works like a a charm, but i have trouble flashing the blue H8 board.

I installed the latest openocd 0.9 and now the connection to the board works fine.

Problem is that i need to unlock the processor and can't find the right command to do that on the blue board.

Can anyone point me to the right openocd command to unlock the processor in the blue board?

Thanks
Johannes
http://der-frickler.net/modellbau/planes/garden_racing

Airmode support

Hi there,

I know I read at one point that there was some consideration towards adding airmode support to Silverware.

I haven't taken a close enough look at the firmware PID code (or the 20 or so forks of this repo, at least) to know how complex it would be but I'd still love to know if there is any prior work towards this goal.

If no one else has dug into this, I may try my hand at implementing it.

Thanks!

New blue board support ?

Hello,

Is there any plan to support the new blue board ? Or do you know someone that managed to flash it ?

Thanks in advance for your answer ;-)

Target voltage too low

Trying to flash a board that has one dead motor (even after replacement), I figured I have nothing to lose before I dump it.

Getting this on the unlock step:

$ openocd -f /usr/share/openocd/scripts/interface/stlink-v2.cfg -f /usr/share/openocd/scripts/target/stm32f0x.cfg -c init -c "reset halt" -c "stm32f0x unlock 0" -c "reset run" -c shutdown
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v24 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 1.204813
Error: target voltage may be too low for reliable debugging
Error: init mode failed (unable to connect to the target)
in procedure 'init' 
in procedure 'ocd_bouncer'

The board boots and binds to the controller, just can't fly due to one dead motor, so I would assume I can at least flash it with this firmware. Am I doing anything wrong?

Getting the same error no matter what pin / power combination I try.

I'm using https://www.banggood.com/ST-LINKV2-ST-LINK-V2CN-STLINK-Debugger-Emulator-Download-Manager-STM8-STM32-p-1099119.html

telemetry on a taranis X9D

Hello is it possible to have telemetry on a taranis X9D + with the blue version of the card?

Unable to unlock using openocd on linux

Hi,
I'm trying to flash using Ubuntu and openocd 0.9.0

I copied unlock commad from non-blue board readme, changing the CPU id to the right one:

`vinz@bookz:~/H8mini_blue_board/bin$ openocd -s /usr/share/openocd/scripts -f /usr/share/openocd/scripts/interface/stlink-v2.cfg -f /usr/share/openocd/scripts/target/stm32f0x.cfg -c init -c "reset halt" -c "mww 0x40022004 0x45670123" -c "mww 0x40022004 0xCDEF89AB" -c "mww 0x40022008 0x45670123" -c "mww 0x40022008 0xCDEF89AB" -c "mww 0x40022010 0x220" -c "mww 0x40022010 0x260" -c "sleep 100" -c "mww 0x40022010 0x230" -c "mwh 0x1ffff800 0x5AA5" -c "sleep 1000" -c "mww 0x40022010 0x2220" -c "sleep 100" -c "mdw 0x40022010" -c "mdw 0x4002201c" -c "mdw 0x1ffff800"

Open On-Chip Debugger 0.9.0 (2015-09-02-10:42)

Licensed under GNU GPL v2

adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v21 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.232718
Info : stm32f0x.cpu: hardware has 4 breakpoints, 2 watchpoints
target state: halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0xc1000003 pc: 0xfffffffe msp: 0xfffffffc
`
But it's not working.

I tried to flash anyway but i got errot:

`vinz@bookz:~/H8mini_blue_board/bin$ openocd -f /usr/share/openocd/scripts/interface/stlink-v2.cfg -f /usr/share/openocd/scripts/target/stm32f0x.cfg -c init -c "reset halt" -c "flash write_image erase h8blue_keil_devo.bin 0x08000000" -c "verify_image h8mini 0x08000000" -c "reset run" -c shutdownOpen On-Chip Debugger 0.9.0 (2015-09-02-10:42)
Licensed under GNU GPL v2

adapter speed: 1000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v21 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.226877
Info : stm32f0x.cpu: hardware has 4 breakpoints, 2 watchpoints
target state: halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0xc1000003 pc: 0xfffffffe msp: 0xfffffffc
auto erase enabled
Info : device id = 0x10006444
Info : flash size = 16kbytes
Error: stm32x device protected
Error: failed erasing sectors 0 to 10
`
Can you help me and insert in the readme the linux command line to flash this blue version?

H8 mini blue board flashing problem

Hi, I was succesfull at flashing 2 H8 mini blue boards. Then I never touched any of the needed software for over 2 months. A friend also wanted to upgrade his H8 mini and I thought it would be no problem to do that. So when I now open The Silverware throu KeilU i get the following error: registered ARM Compiler Version not found in path: ARMCC. Update the configuration of multiple ARM compiler in Manage Project Items. So I checked the Pack Installer if any software is missing but everything is up to date. Please help me to solve this issue because it is so frustrating that it doesnt work after not even using the programs. Thanks