Upload myFirmware with Missionplanner to VRuBrain5.1

[Günther Pleschutznig]

Guten Tag.

Hi.

My eniviroment to avoid requests.

Hardware:Gigabyte i7, 16GB Ram, a lot of HD's

OS Windows7_x64, Kubuntu 10.04

Relevante Software:

                Arduino 1.03, 1.5

                Visual Studio's

                Atmel Studio 6.2

                IDE PX4

                Missionplanner latest

                STM DFU

                IDE VRBRAIN

Controllers: ArduMega 2560, APM2.5, PX4FMU/IO, china clone apm2.5,

                    last but not least VRuBrain 5.1

Tools: AVR-Dragon, AVR-MkII, usb-scope

ToFly: lot of planes, copter,

Upload to VRuBrain the official Firmware with Missionplanner  OK

Connect GPS, Compass, Receiver OK

Problem: Firmware is not build For RC-Channel-Map of my transmitter.

Changed mapping with Missionplanners Patameterlist.(with write params like amp/px4).

Restart, No effect. mapping not changed

Downloaded from web variante xxxx_pwm.vrx.

The same.

Downloade Sources and compiled.

Got xxx.hex, xxx.bin .......

Tried upload with Missionplanner xxx.hex(like apm); Miisionplanner not accepts my hex.

Converted .hex to .dfu, Upload with STM-Tool OK.

But the bootloader is destroyed, Missionplanner can't connect.

I could cross the wires in pwm, but I think the is not a smart solutiom.

Help.

HOWTO build myFirmware.xxx accepted and uploading by Missionplanner.

Missionplaner accepts Firmeware.vrx downloaded from web.

How can I build myFirmware.vrx or myFirmware.???.

[Günther Pleschutznig]

Hi Luca

Done; it works !

THX

ple

[Micheletti Luca Angelo]

Hi,

what IDE are you using for buid firmware? IDE VRBRAIN or IDE PX4?

IDE VRBRAIN is ok for all firmwares without NuttX OS (until VRBrain 4.5). For build the firmware for VR Micro Brain 5 you need:

1. IDE PX4

2. Download repository virtualrobotix/ardupilot and virtualrobotix/vrbrain_nuttx

3. Import this two projects into Eclipse

4. Into tab Make Target, ardupilot's project, you must create a new target in folder ArduCopter "configure". Launch this target and check the file created "config.mk": in this file the path specified in VRBRAIN_ROOT must point to "ardupilot's project" and the path specified in VRBRAIN_NUTTX_SRC must point to "ardupilot's project/NuttX/nuttx". For example, if the name of your ardupilot's project is "ardupilot" and the name of your nuttx' project is vrbrain_nuttx you must insert these definitons:

    VRBRAIN_ROOT=../vrbrain_nuttx
    VRBRAIN_NUTTX_SRC=../vrbrain_nuttx/NuttX/nuttx

5. Into tab Make Target, ardupilot's project, you must create a new target in folder ArduCopter "vrubrain-v51". Launch this target to build the firmware

Try it and let me know

Luca

[Günther Pleschutznig]

Hi Luca.

Sorry no success.

added make target vrubrain-v51

build reports: no rules to build this target

Günther

[Micheletti Luca Angelo]

Hi Günther,

when you upload the firmware with dfu, DfuSe first erase the flash and then upload the new firmware. Unfortunately with this method it's not possible to upload only the firmware but it's necessary to combine (Multi bin function to create dfu) the bin of bootloader (start flash at 0x08000000) and the bin of firmware (start flash at 0x08004000). After this operation it's possible to upload the new dfu on board.

To restore the situation you must:

1. download our repository virtualrobotix/VRX_Binary from GitHub. In this repository there is a forlder "bootloader" where you can find the bootloader for your board. There is also dfu.

2. With DfuSe upload the bootloader on your board. On start the board will stop at bootloader (the blue led is flashing).

3. To upload the firmware you can first update it to official release with Mission Planner as you have already done and then you can upload your custom firmware always with Mission Planner with tool "Load custom firmware" that is located in the tab Install Firmware. With this tool it's possible to search a vrx firmware and to upload on board directly with Mission Planner. The tool "Load custom firmware" is new for VR Micro Brain: make sure you have updated Mission Planner to version 1.3.7.

In this way you should be able to restore your board.

To compile a new custom firmware you must select (in Eclipse) the target "vrubrain-v51" in tab Make Target (normally on the right of interface) in the folder ArduCopter of ardupilot's project. The new firmware (ArduCopter-vrubrain-v51.vrx) will generate in the same folder (Ardupilot Project/ArduCopter). You can upload this new firmware with tool "Upload custom firmware" of Mission Planner.

I hope to be helpful to you.

Best

Luca