Another problem compiling with CrossWorks 3.3

[HeliHenkie]

Hi all,

I encountered another problem compiling my own firmware with CrossWorks 3.3.
Compiling stops at the following point in the process: Compiling stm32f4xx_cryp.c.

Did anyone encounter this problem and have a solution?

Best regards,

Jan Willem
The Netherlands

[LPR]

Read this recent thread. i might help.

viewtopic.php?f=31&t=3946&p=27852#p27847

Larry

[Max]

Don't need _cryp.c, exclude it from build (find in CW file list, r-click, exclude).

-Max

[HeliHenkie]

@Max: Thanks for your reply. Why is this file in the project file if it isn't needed? What does it do?

Best regards,

Jan Willem
The Netherlands

[Max]

[HeliHenkie]

@Max: Thanks for your clear answer. You state you don't use CW very often. Does that mean there is another way to compile the firmware? I've read about people trying to use alternative software on the forum, but I always thought this was without success.

Best regards,

Jan Willem
The Netherlands

[Max]

Hi Jan. Yes, you can build from a command line w/out using the CW GUI. Angel describes it pretty well here: viewtopic.php?f=31&t=3114 You'll also need the zip file attached here: viewtopic.php?f=31&t=44&start=80#p17041 Also read the comments in the Makefile.

All the automated builds on our FTP server are scripted using `make Makefile`. I use Eclipse as my IDE, and configure build profiles I can launch for different configs (hw type, etc), which simply run `make Makefile` with various options.

BTW, in case you are trying to build a custom Quatos version (as per the other thread), you won't be able to w/out the (unreleased) quatos library file.

-Max

[HeliHenkie]

@Max: Your assumption is spot on. I'd like to compile a custom Quatos version. I build the reference 400 quadcopter presented by Angel. My flight controller is a brand new AQ6 board with DIMU and 4 KISS esc's. I've read that it should be possible to adapt the code so that regular esc's can be used instead of the ESC32's. Apparently I've missed the part that a quatos lib file is required.
Will a firmware version with this modification be put on the FTP server?

Best regards,

Jan Willem

[Max]

Jan, I'm not very clear on what is needed for non-ESC32 with Quatos. I know Steve and Menno have had some success with this, but the information is scattered or incomplete. Definitely some bleeding-edge stuff. Hopefully someone else will chime in on that on your original thread in the Quatos forums. Sorry I don't have more info for you.

-Max

[Kisssys]

Hi Jan,

Menno and I have been playing with this for a few month's with good success. It unfortunately had not been incorporated in the regular builds. Since the quatos library is not openly available even if you can compile the code your still missing the the most important part Quatos.

Hopefully these changes can be made in the near future.

The basic idea is to use the AQ to calibrate the esc's and then run a test program that steps the pulse width of the motor output from 1000 to 1950 us in 100 us steps. As it steps up we record the thrust available at each pw setting. From that we can plot a second order polynomial that represents the thrust for a given pw setting. The regular Quatos uses a rpm setting to the closed loop esc reference the thrust. Where we used to put the maximum RPM of the motor in MOT_VALUE_SCAL we use 950 since we plot the thrust curve from 0 to 950 us.

This is a 250 machine with Kiss esc's that fly's very well.


Cheers
Steve