Have AP 4.1.7 working on RevoMini with I2C and SD card here.
But now I found, that in 4.3.0dev there is an add. hwdef.dat.sd, which combines I2C and SD card support.
Just build the firmware with AP 4.2.2 and this hwdef.dat.sd and on my delta test rig seems to work fine …
I know, that the RevoMini is out of production and I don’t know, how many are still around. But in my eyes, that FC is ideal for small airplanes, I my self have four of those.
Hi nostromo1232, I would like to use the OPLink port of my fc revo mini for an SPI peripheral (external SD card). This would be essential for me to record the logs. I’m currently using the I2c revo firmware. Could you please help me? How can I use the hwdef.dat.sd ?
Thank you very much.
willliam
Search my notes. I started adding the sd-card with AP 4.1.7. Had to get me a building environment to create the firmware from source. Last time I messed around with the revo-mini, sd-card was in 2022 with AP 4.3.1.
I loaded the source into the building environment, modified the ‘hwdef_revo-mini_4.3.1.dat’ file in the code, build the firmware and uploaded the firmware to the board. The complicated part was getting the building environment working. I used Linux. I am not an expert on that The modifications in hwdef_xxx_dat were not so complicated, just had a look into hwdef_xxx_dat of flight controllers, which came with an sd-card.
But the problem now is, I don’t have any idea, how the situation is now with AP 4.4.4?
Would have to create a new building environment, have a close look at the code, make modifications to the configuration files ‘hwdef_xxx_dat’ if necessary and generate the firmware …
William, I created a new building environment under Debian bullseye here and build successfully the revo-mini firmware under AP4.4.4!
But only for revo-mini and for revo-mini-i2c. But there is a 3rd configuration package revo-mini-sd, which brings some modifications to use the SD card.
AUTOBUILD_TARGETS
include …/revo-mini-i2c/hwdef.dat
The building has to be done in conjunction with the revo-mini-i2c, but at the moment I don’t have the slightest idea, what command is needed.
With my fresh building environment I successful build and tested revo-mini-sd firmware with the sources AP 4.3.1! I knew before, that 4.3.1 was working!
With AP 4.4.4 I successful build and tested revo-mini, revo-mini-i2c.
But all my attempts to generate here the revo-mini-sd under 4.4.4 failed.
There are exactly 10 version in between 4.3.1 and 4.4.4. Question is, when did this issue showed up?
Thank you very much nostromo 123 for your kind reply. Only now did I notice your instructions. Now I’ll get to work. I really appreciate your help. Thanks again…
Reinhard, is that you? Most are happy now with the SpeedyBee F405 Wing, you introduced in your workshop on www.frsky-forum.de, but some are still searching desperately the ‘complete parameter list’ for clues or hints
About that link to the Aliexpress FC. You have on of those on your workbench? What components are on that board, any further documentation, this is a clone of which fc?
But at the moment, I am busy with that issue here. See you elsewhere …
The F4WSE FC uses the firmware from the MatekF405-TE but is not a direct copy because it is built differently. IMHO it is currently one of the smallest FCs and inexpensive.
