engtore.blogg.se - Build a diy opentx clone frsky transmitter fromscratch

#Build a diy opentx clone frsky transmitter fromscratch update
#Build a diy opentx clone frsky transmitter fromscratch code

Mine looks like this (when running make):Īrm-none-eabi-gcc -x assembler-with-cpp -c -mcpu=cortex-m4 -Wa,-amhls=build/lst/crt0_v7m.lst -DCORTEX_USE_FPU=TRUE -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -mthumb -MD -MP -MF. What could also help is comparing what arguments gcc is ran with. I flash it via make flash, but I never go past the debug console with the message “gui: entering main loop” usr/local/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-gcc -c -O1 -g -I./ -mcpu=cortex-m0 -mthumb -Wl,-Map,openground.map -DHSE_VALUE=12000000 -Idevice -Icore -Iperipheral_lib/inc -Iperipheral_lib/eeprom_emulation/inc -I./src -DSTM32F072 -DUSE_STDPERIPH_DRIVER -DUSE_FULL_ASSERT -DBUILD_TARGET= src/main.c -o src/main.o I’ve tried switching to an older arm-none-eabi-gcc compiler version and still no luck. I’ve tried with a fresh git clone of your repository and have the same problem. Anyway, with OpenGround I’m hitting the same wall as Jonas was below: I cannot get out of the debug window and, if I force the GUI, I see no ADC inputs. Really nice work, I’ve been following your projects for some time and it’s awesome! I’m trying to come around and build your FC and 4-in-1 ESC, but I need to improve my soldering skills first. Just FYI, my PCB reads FS_I6S_V2.4 9 like yours. Forcing config_hw_revision=0 makes channels work as expected.

#Build a diy opentx clone frsky transmitter fromscratch code

Besides, AETR channels were mixed and some of them inverted… So I suspected the Turnigy Evolution detection code and yes, my FS-I6S is detected as a Turnigy Evolution (config_hw_revision=1). Once I had ADC working, I noticed that switching between the console and the GUI happened by toggling SWA (supposedly CH0) instead of SWC (CH3). But as I’m trying to modify the firmware for using the native A7105 module for Flysky and Hubsan protocols, frsky_send_packet was never called and ADC inputs were not processed. By exploring the different commits, the latest was to fix a bug about how often ADC inputs were processed… by moving the call adc_process() from the gui_loop function to the frsky_send_packet function. Ok, I’ve found why I was seeing no ADC inputs and why I could not go into the GUI and got stuck in the debug console.

OpenGround – Part 1 – Components & Pinout ().

OpenGround – Part 2 – FS-i6s DFU Bootloader access ().

OpenGround – Part 3 – SWD/ST-Link debugger ().

OpenGround – Part 4 – running GDB on the STM32F0 ().

OpenGround – Part 5 – driving the HSG12864 Display (ST7567 controller) ().

OpenGround – Part 6 – Using the ADC of the STM32F0 in DMA mode to read multiple channels ().

OpenGround – Part 7 – Using the FT6236 touch controller / I2C on the STM32F0 ().

OpenGround – Part 8 – Buttons, Lazyness, GPIOS, and memory locations on STM32F0 ().

OpenGround – Part 9 – CC2500 & some UI work ().

#Build a diy opentx clone frsky transmitter fromscratch update

OpenGround – Part 10 – Status update & some UI impressions (video) ().OpenGround – Part 11 – CC2500 adapter board ().

OpenGround – Part 12 – Turnigy Evolution – I/O mapping ().OpenGround – Part 13 – switching from the st peripheral lib to libopencm3 ().Once finished this will become the main project page. For now i will write single blog posts and collect them on this page. I am not affiliated with Flysky or FrSky in any way. Unfortunately i only run FrSky gear, this one is FlySky… So what now? I am going to swap the hf module to a CC2500 transceiver module and write my own firmware for the FS-i6s! OpenGround will become the counter-part of my opensource firmware OpenSky that runs on FrSky receivers. When i saw the new FlySky FS-i6S RC transmitter for around $50 i immediately thought it would make a nice “always with me” tx for my TinyWhoop.