Search found 5 matches
- Sat Sep 27, 2014 1:20 pm
- Forum: Software
- Topic: Harakiri aka multiwii port to stm32
- Replies: 1502
- Views: 576846
Re: Harakiri aka multiwii port to stm32
It's a little confusing from just reading the thread, but I have used all of them ( KVOSD, WMOSD, and MinimOSD). I think Harakari detects whether you are using the MW protocol or Mavlink. My biggest issue is getting all the info to show correctly (RSSI, Flight Modes, etc).
- Thu Sep 25, 2014 12:04 am
- Forum: Software
- Topic: Harakiri aka multiwii port to stm32
- Replies: 1502
- Views: 576846
Re: Harakiri aka multiwii port to stm32
Mr-Fiero wrote:No battery means impact or something...you still might have other issues.
Nope, never even had a hard landing with this one, just poor assembly I guess, and yes if I waited 5 minutes it worked great.
- Wed Sep 24, 2014 11:05 pm
- Forum: Software
- Topic: Harakiri aka multiwii port to stm32
- Replies: 1502
- Views: 576846
Re: Harakiri aka multiwii port to stm32
So, I was wondering why GPS Hold went from great to terrible, so I started to take everything apart and rewire... DOH!, no battery! https://lh5.googleusercontent.com/-LN_uzqnC5y8/VCM9OLHB-DI/AAAAAAAABC4/jxUGWmsu_2g/w800-h452-no/bad.jpg @ Mr-Fiero, will your code work with the LEA-6H? I know you disa...
- Wed Sep 24, 2014 12:13 pm
- Forum: Software
- Topic: Harakiri aka multiwii port to stm32
- Replies: 1502
- Views: 576846
Re: Harakiri aka multiwii port to stm32
I just followed these instruction, and I didn't use Yagarto, because I didn't see very many people using it. m The only other thing I had to add under the "Cross ARM Linker->Miscellaneous->Other linker Flags" setting was "--specs=nosys.specs". This fixes an unresolved reference t...
- Wed Sep 24, 2014 2:32 am
- Forum: Software
- Topic: Harakiri aka multiwii port to stm32
- Replies: 1502
- Views: 576846
Re: Harakiri aka multiwii port to stm32
Quick code question: (Ha) I've built the git source(T3) in eclipse with out any problems, but the release hex is too big to flash (0x08027354 > 0x08020000, optimized for size -Os). What can I remove from the build to trim it down, or is there some other symbol table I need to strip from the binary? ...