# Cannot Upload Firmware to Pixracer? **URL:** \ **Category:** Uncategorized\ **Created:** [October 4, 2017, 1:08pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586 "2017-10-04T13:08:13Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 4, 2017, 1:08pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/1 "2017-10-04T13:08:13Z")
Hi all , I bought a new Pixracer yesterday and tried to upload the latest Firmware to Pixracer but failed!! I used command `make px4fmu-v4_default upload ` to upload program to it and finally got error as following : ![](https://discuss.px4.io/uploads/default/original/2X/a/a5b5096e3f135a2e082e356f58f8d414c395b5ee.jpg) what happened to my Pixracer? Ubuntu PC Environment: `gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609` `arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release)` ---
**Author:** ![Nicolas](https://discuss.px4.io/user_avatar/discuss.px4.io/nicolas/32/4467_2.png) [@Nicolas](https://discuss.px4.io/u/Nicolas)\ **Post date:** [October 5, 2017, 8:37am UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/2 "2017-10-05T08:37:07Z")
From the screenshot you shared it looks like the upload worked. What makes you think it didn’t work? ---
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 5, 2017, 9:02am UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/3 "2017-10-05T09:02:45Z")
hi @Nicolas , I’m not sure ,I had upload firmware to my pixhawks serveral months ago and If it run successfully , the message should end with `[100%] Built target upload` . ---
**Author:** ![Nicolas](https://discuss.px4.io/user_avatar/discuss.px4.io/nicolas/32/4467_2.png) [@Nicolas](https://discuss.px4.io/u/Nicolas)\ **Post date:** [October 5, 2017, 4:04pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/4 "2017-10-05T16:04:09Z")
I don’t see an error in that screenshot. Have you confirmed that the firmware running on the device is still old? ---
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 5, 2017, 4:27pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/5 "2017-10-05T16:27:02Z")
Hi @Nicolas , I used Qgroundcontrol to check the version of Pixracer aftering upload PX4-V4 Firmware and I got `Unknown Version` just as the following : ![](https://discuss.px4.io/uploads/default/original/2X/5/5b3e0268152bf84e240542d7526930e73c07b32f.jpg) ---
**Author:** ![Nicolas](https://discuss.px4.io/user_avatar/discuss.px4.io/nicolas/32/4467_2.png) [@Nicolas](https://discuss.px4.io/u/Nicolas)\ **Post date:** [October 6, 2017, 1:06pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/6 "2017-10-06T13:06:18Z")
After flashing, you can check the firmware version, including the git hash, in a terminal using the `ver` command. ---
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 8, 2017, 1:10pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/7 "2017-10-08T13:10:35Z")
hI @Nicolas , Thank you for your advice! I have upgraded my pixracer to the latest version successfully. Now , I’ve got an another problem: The RGB LED on my pixracer is always flashing green even though I calibrated sensors ,radio ,power until no warning in Qgroundcontrol. Is my pixracer working fine? ---
**Author:** ![Nicolas](https://discuss.px4.io/user_avatar/discuss.px4.io/nicolas/32/4467_2.png) [@Nicolas](https://discuss.px4.io/u/Nicolas)\ **Post date:** [October 9, 2017, 11:55am UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/8 "2017-10-09T11:55:10Z")
Yes, sounds fine. You’ll know there are problems if you try to arm or switch modes and you get warnings. ---
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 11, 2017, 3:30pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/9 "2017-10-11T15:30:39Z")
Hi @Nicolas, I think my safety button is wired wrong or broken because I connect the safety button to my pixracer and pushed it and there is no reaction . However, I can use these following commands to change flight mode or arm motors and the safety button changed mode at the same time. ```auto roslaunch mavros px4.launch rosrun mavros mavsafety arm / disarm rosrun mavros mavsys mode -c MANUAL / OFFBOARD / STABLIZED ``` any ideas? thanks ---
**Author:** ![Nicolas](https://discuss.px4.io/user_avatar/discuss.px4.io/nicolas/32/4467_2.png) [@Nicolas](https://discuss.px4.io/u/Nicolas)\ **Post date:** [October 11, 2017, 3:46pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/10 "2017-10-11T15:46:55Z")
What do you observe when trying to arm (in manual mode) with an RC? Depending on the airframe selected, the safety switch is not needed (i.e. off by default). ---
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 12, 2017, 1:55am UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/11 "2017-10-12T01:55:22Z")
Hi @Nicolas, Thank you for your reply!! The airframe that i used is ix5-210 . i couldn’t find airframe related to ix5-210 in QGC ,so I choose `Generic 250 Racer` instead of `Generic 210`. Eventhough I reconnected the Futaba S.Bus to my pixracer and recalibrated the joystick in mode 2 , I still couldnot arm the drone in manual mode . I saw the safety switch still blinking fastly that meant my drone was not ready to arm . [https://www.amazon.com/iFlight-Ultimate-Moulding-Racing-Landing/dp/B071NY1FDD/ref=sr\_1\_1?ie=UTF8&qid=1507772368&sr=8-1&keywords=ix5+210](https://www.amazon.com/iFlight-Ultimate-Moulding-Racing-Landing/dp/B071NY1FDD/ref=sr_1_1?ie=UTF8&qid=1507772368&sr=8-1&keywords=ix5+210) BTW , What parameter should I modify if I want to enable / disable safety switch? ---
**Author:** ![Nicolas](https://discuss.px4.io/user_avatar/discuss.px4.io/nicolas/32/4467_2.png) [@Nicolas](https://discuss.px4.io/u/Nicolas)\ **Post date:** [October 12, 2017, 8:04am UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/12 "2017-10-12T08:04:37Z")
The “Generic 250” frame has the safety switch bypassed/disabled. So your arming problems aren’t due to the safety switch. Do you have telemetry to QGC when trying to arm? You should see a message telling you why it’s not arming. ---
**Author:** ![pinxian](https://discuss.px4.io/letter_avatar_proxy/v4/letter/p/85f322/32.png) [@pinxian](https://discuss.px4.io/u/pinxian)\ **Post date:** [October 13, 2017, 4:57pm UTC](https://discuss.px4.io/t/cannot-upload-firmware-to-pixracer/4586/13 "2017-10-13T16:57:38Z")
Hi @Nicolas, Thanks for your help and you’re right . Today , I flew my drone indoor without safety switch successfully. I used mocap system to feedback pose data and the performace was very good. However , I tried to use RC joystick to arm motors and there is still no reaction. I guess that I use the wrong way to arm the drone , because there was no warnning message in QGC when trying to arm motors. Any idea?