Try to debug autoquad source code -> fails

[MaPa]

Hi all,

I try to compile autoquad sourcecode and for debugging I use STM32F4discovery board.

Compiling the project is fine, i got no errors
I connect only USART1 (PA9 and PA10) to a FTDI/RS232 Converter and the Comport is used in AutoquadGroundStation.

I receive no clear messages in AQGS or HyperTerminal, only 0x00 0x92 ....
Baudrate is correct, but I also changed it to lower speed -> 9600.

Which functions can I use to send a message to usart1?
I tried AQ_NOTICE, AQ_PRINTF

Have I set a flag to get clear messages to USART1?

Have I to consider anything?


Thanks,
MaPa

[Mike Barton]

I *think* your problem is that USART1 has flow control enabled so you will need to connect up CTS + RTS wires
unfortunately, they are not available of F4-Disco board - thay are only available thru CN5 - the micro USB

the dev release has USB support (you will need to enable it in the code) but needs the correct driver to work but I cannot confirm this!

[Max]

Hi MaPa, welcome to AQ forums.

Assuming everything is running correctly and with default AQ settings, you should be getting Mavlink protocol out of USART1 at 115,200 bps, no flow control. Mavlink is not plain text, you need to decode it. AQ also has its own serial protocol which can be enabled on USART1 or 2 -- but there are no docs for that except the code itself (also some in ground tools folder).

I can't really tell what you're trying to do though. For a true debugging setup you'll want to use the ST-LINK SWD interface built-into the STM32 disco board and a compatible IDE/debugger.

-Max

[Mike Barton]

ah yes - pls ignore what i wrote
yes, appears to work ok without flow control, I initially had a problem connecting via usart and thought this was the solution

if you're using a Disco board, then the code will invariably hang at some point so there's not much point unless you get an aq board or diy your own....

[MaPa]

[MaPa]