Bitcraze Forums

2013.12.14
commit 7aa4f06c551ad9a1969158d98781d765ac0fb6e7
Fix address bug in log/param module

DerShu wrote:I assume that all that is necessary is to get the new scatter file from your github account?

Thank you very much for your work!

yes, just get scatter file and set the options to use it.

Add cloader support

Good luck!
Just remember, now the bin is started from 0x08000000.
Later, I will release a version for CLoader.

That's easy. Actually, you can use ARM tools "fromelf" to convert a .axf file to .bin. Now I have updated the script for this convert. Please get the latest project code. But please note: You should modify the fromelf tools path according to your install path. The setting is in "Optio...

I have worked through all warning, and suppress them. Don't worry, I checked these warnings, it should be OK. And I found an issue in eskylink.c function "eskylinkDecode" static CRTPPacket crtpPacket; float pitch, roll, yaw; uint16_t thrust; pitch = ((packet[2]<<8) | packet[3])-PPM_ZERO; i...

Now, the warning seems OK for the main function.
But I don't have crazyflie HW, so I can't tested it.
The linker options make it run at 0x08000000 (like make CLOAD=0), this means it can't support CLoader.
Next step, I will make it support cloader. Maybe just change scatter loader file.

Hi DerShu: Thanks for your suggestion. Yes, I will fix all the warning if possible. The first version should be functional OK. Most of the warning can be suppressed and I did some in the linker command line settings. I am a software engineer, and not strong at HW. If you are interested in quadcopter...

Hi, I have made a version of crazyflie firmware support both keil and gcc compile environment. If you are interested in it, get it from https://github.com/wwfiney/crazyflie_firmware_keil_gcc I use my own board(not crazyflie nano quadcopter), and it can work under Keil uVision4. The porting version i...

marcus wrote:Hi,

The problem might be that some code is missing from the I2C2 implementation. If you have a look in the i2croutines.c file there's some implementation that is there for I2C1 but not for I2C2.

thanks marcus, I'll debug it.

I found that there was even no I2C2 interrupt handler. lol