Crazyflie 2.0 and ET6I radio compatibility?

[growabeard]

I recently bought one of the ET6I radios on eBay, thinking I could use it with my crazyflie 2.0.

I'm not sure if I'm just having trouble flashing it, but when I try using the firmware listed on this page: https://wiki.bitcraze.io/misc:hacks:et6i, my crazyflie just has one steady blue light after I restart in firmware mode.

I also tried to build the firmware (with the commands listed on the page linked above) on the 0.8 VM, and I get an error

Code: Select all

bin/comm.o: In function 'commInit':
/home/bitcraze/projects/crazyflie-firmware/modules/src/comm.c:50: undefined reference to 'eskylinkInit'
collect2: error: ld returned 1 exit status
scripts/targets.mk:32: recipe for target 'cflie.elf' failed
make: *** [cflie.elf] Error 1
rm version.c

Any help here would be fantastic and much appreciated!

[chad]

The ESky code has not been ported to work with the Crazyflie 2. Since the nRF51 chip is now handling the radio work on the CF2, the ESky code has to be ported to run on that chip.

I also have an ET6i and I miss using it but, after getting a Walkera Devo7e and modding it, I've never looked back.

[growabeard]

Alrighty, I guess I didn't do enough searching and whatnot before buying the Esky radio.

How can I get started in regards to porting the firmware for Esky support? I'd like to get involved and I think I have the ability to help.

I already have the VM, so all is set up there. Which files should I start poking around in?

[tobias]

Welcome to the forum growabeard!

Great that you would like to give the ET6I support a shot! I am myself hacking around to make cheap remotes from like the CX10 usable as those radios can be compatible with the nRF24L01 & nRF51822. I haven't come that far that I'm starting to integrate it into the CF2 architecture though (playing around with a nRF51 dev board).

The code needs to be in the nRF51 and should be integrated somewhere in the mainLoop. The question is if we can have the CRTP (protocol to connect using Crazyradio), BLE and others active at the same time, probably not but would be nice.

The code working for CF1 is here and then needs to be ported to the nRF51 in the CF2. Something like this:
* Setup radio to receive Esky packets
* Decode packet and convert them into a commander packet values
* Assemble commander packet and send over the syslink (what we call the uart link between the nRF51 and the STM32)

Hope the above makes any sense