I believe it’s the same as the v2700 that I see mentioned, and that is sold byTarget, but, from what I can tell it has a part number of v1849. It appears to have all the functionality of the original v2450, but I’m not sure that it’s 100% compatible.
I’ve compiled the v2450 firmware from ArduPIlot github. Is it okay to flash that?
And for what it’s worth I’m having issues building Ardupilot for that target. It errors out like this…
[7/96] ChibiOS: Compiling chprintf.c
In file included from ../../modules/ChibiOS/os/hal/ports/STM32/STM32F4xx/hal_lld.h:33:0,
from ../../modules/ChibiOS/os/hal/include/hal.h:122,
from ../../modules/ChibiOS/os/hal/lib/streams/chprintf.c:31:
../../modules/ChibiOS/os/hal/ports/STM32/STM32F4xx/hal_lld_type1.h:1776:2: error: #error "STM32_PLLI2SVCO outside acceptable range (STM32_PLLVCO_MIN...STM32_PLLVCO_MAX)"
#error "STM32_PLLI2SVCO outside acceptable range (STM32_PLLVCO_MIN...STM32_PLLVCO_MAX)"
^~~~~
make: *** [modules/ChibiOS/obj/chprintf.o] Error 1
Make sure you made updates of modules
git submodule update recursive
And take note that building new firmware for the Journey breaks the receiver. I opened issue but no answer yet. You can fly using joystick connected to Mission Planner or you cam revert to skyviper firmware
Thanks for the additional info. I"m not seeing the same error as @John_Orthoefer by using the default arm compiler installed in Ubuntu (rather than the lauchpad version).
That’s strange that the receiver would be broken. I’ve read in places that it’s a standard DSM receiver. Is that right?
My next step was to try to use a standard Tx,…
Edit: I should add that this is a fresh checkout of the repo, so the submodules should be up to date.
Build-essentials was the first think I thought of, but I use this machine for development, so, of course, that wasn’t it.
It would be good to figure out which compiler to use, since I had to install the lauchpad compiler to get the v2450 firmware to build. I don’t know why that compiler doesn’t work for the f412 target.
I’m still unable to build skyviper-f412. Still erroring out at…
[6/95] ChibiOS: Compiling chprintf.c
In file included from ../../modules/ChibiOS/os/hal/ports/STM32/STM32F4xx/hal_lld.h:33:0,
from ../../modules/ChibiOS/os/hal/include/hal.h:122,
from ../../modules/ChibiOS/os/hal/lib/streams/chprintf.c:31:
../../modules/ChibiOS/os/hal/ports/STM32/STM32F4xx/hal_lld_type1.h:1776:2: error: #error "STM32_PLLI2SVCO outside acceptable range (STM32_PLLVCO_MIN...STM32_PLLVCO_MAX)
Okay I’ve had some time to debug the issue… And I’m not sure where to go from here.
in modules/ChibiOS/os/hal/ports/STM32/STM32F4xx/hal_lld_type1.h
STM32_PLLI2SVCO for f412 seems to be defined as ((STM32_I2SCKIN_VALUE / STM32_PLLI2SM_VALUE) * STM32_PLLI2SN_VALUE) which have values of ((0/4)*192) which means it is infact out of range as defined by STM32_PLLVCO_MIN and STM32_PLLVCO_MAX
now tracing down why STM32_I2SCKIN_VALUE is zero I get to the following…
/**
* @brief I2S external clock value, zero if not present.
* @note Not all devices have this setting.
*/
#if !defined(STM32_I2SCKIN_VALUE) || defined(__DOXYGEN__)
#define STM32_I2SCKIN_VALUE 0
#endif
Do I open the ticket against ChibiOS or Ardupilot code base? I know enough about building software to track down the issue, but I don’t know enough about Skyrocket f412 architecture to know how to fix it.
Yes confirmed , master is broken , you can go directly in the chibios room https://gitter.im/ArduPilot/ChibiOS and report
Note that I already reported = I will update here
as I wrote before, … note that building new firmware for the Journey breaks the receiver. I opened issue but no answer yet. You can fly using joystick connected to Mission Planner or you cam revert to skyviper firmware