# PX4IO problem on Pixhawk 2.1 **URL:** \ **Category:** PX4 Autopilot\ **Created:** [January 8, 2017, 8:09am UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127 "2017-01-08T08:09:54Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![6ilmendoza](https://discuss.px4.io/letter_avatar_proxy/v4/letter/6/977dab/32.png) [@6ilmendoza](https://discuss.px4.io/u/6ilmendoza)\ **Post date:** [January 8, 2017, 8:09am UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/1 "2017-01-08T08:09:54Z")
I’m using a pixhawk 2.1 flashed with Firmware 1.5.3. I first noticed that the RC inputs were not recognized by the board (I’m using a spektrum receiver connected into the spkt/dsm port. I’m sure that the RC and the receiver are porperly bound) but then I looked at the NSH console to see messages while booting and I now think that the entire px4io module is not working properly. I’m attaching the log of messages I got. Does anyone have a clue how to solve this issue? sercon: Registering CDC/ACM serial driver sercon: Successfully registered the CDC/ACM serial driver WARN [param] selected parameter default file /fs/mtd\_params WARN [rgbled] no RGB led on bus #2 WARN [blinkm] I2C init failed WARN [blinkm] init failed WARN [px4io] check CRC failed: -22 INFO [px4io] default PWM output device [PX4IO] using firmware from /etc/extras/px4io-v2.bin [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bootloader not responding WARN [px4io] check CRC failed: -22 INFO [dataman] Power on restart, data manager file ‘/fs/microsd/dataman’ size is 47640 bytes MS5611\_SPI on SPI bus 4 at 2 (20000 KHz) MS5611\_SPI on SPI bus 1 at 3 (20000 KHz) WARN [bst] no devices found INFO [ver] match: PX4FMU\_V2 HMC5883\_I2C on I2C bus 1 at 0x1e (bus: 100 KHz, max: 400 KHz) LIS3MDL bad ID: 3cWARN [lis3mdl] no device on bus 2 WARN [hmc5883] no device on bus 1 WARN [mpu6000] no device on bus 3 WARN [mpu6000] no device on bus 4 WARN [mpu6000] no device on bus 4 MPU9250 on SPI bus 4 at 1 (1000 KHz) L3GD20 on SPI bus 4 at 4 (11000 KHz) LSM303D on SPI bus 4 at 3 (11000 KHz) WARN [mpu6000] no device on bus 3 WARN [mpu6000] no device on bus 4 MPU9250 on SPI bus 1 at 4 (1000 KHz) HMC5883\_SPI on SPI bus 1 at 5 (11000 KHz) WARN [hmc5883] no device on bus 3 ERROR [meas\_airspeed] no MS4525 airspeed sensor connected ERROR [meas\_airspeed] no MS4525 airspeed sensor connected ERROR [ets\_airspeed] no ETS airspeed sensor connected ERROR [ets\_airspeed] no ETS airspeed sensor connected SF1XX disabled. ERROR [sf1xx] driver start failed WARN [commander] No RGB LED found at /dev/rgbled0 INFO [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS1 @ 57600B INFO [mavlink] mode: OSD, data rate: 1000 B/s on /dev/ttyS2 @ 57600B INFO [ver] match: PX4FMU\_V2 px4flow [208:100] WARN [px4flow] scanning I2C buses for device… INFO [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B ERROR [mixer] can’t open /dev/pwm\_output0 ERROR [mixer] failed to load mixer ERROR [init] Error loading mixer: /etc/mixers/quad\_+.main.mix INFO [lib\_\_ecl] EKF IMU buffer length = 21 INFO [lib\_\_ecl] EKF observation buffer length = 16 NuttShell (NSH) nsh\> WARN [mavlink] Disabling hardware flow control INFO [lib\_\_ecl] EKF using pressure height - commencing alignment WARN [mavlink] Disabling hardware flow control WARN [commander\_tests] Not ready to fly: Sensors not set up correctly INFO [lib\_\_ecl] EKF alignment complete ---
**Author:** ![Bart](https://discuss.px4.io/letter_avatar_proxy/v4/letter/b/f19dbf/32.png) [@Bart](https://discuss.px4.io/u/Bart)\ **Post date:** [January 8, 2017, 10:31am UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/2 "2017-01-08T10:31:16Z")
I’ve seen this a couple of times on Pixhawk 1. Usually re-flashing helps. ---
**Author:** ![vvid](https://discuss.px4.io/user_avatar/discuss.px4.io/vvid/32/8440_2.png) [@vvid](https://discuss.px4.io/u/vvid)\ **Post date:** [January 8, 2017, 3:20pm UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/3 "2017-01-08T15:20:56Z")
It often happens to me if IO is updated and for some reason the startup script fails to flash it. Just run `px4io forceupdate 14662 /etc/extras/px4io-v2.bin` in console and it flash the IO. ---
**Author:** ![6ilmendoza](https://discuss.px4.io/letter_avatar_proxy/v4/letter/6/977dab/32.png) [@6ilmendoza](https://discuss.px4.io/u/6ilmendoza)\ **Post date:** [January 8, 2017, 4:15pm UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/4 "2017-01-08T16:15:45Z")
Thank you for answering, I tried just now to run ‘px4io forceupdate 14662 /etc/extras/px4io-v2.bin’ in console but I got the same result. nsh\> px4io forceupdate 14662 /etc/extras/px4io-v2.bin WARN [px4io] px4io is not started, still attempting upgrade [PX4IO] using firmware from /etc/extras/px4io-v2.bin [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bootloader not responding nsh\> Any other ideas? ---
**Author:** ![vvid](https://discuss.px4.io/user_avatar/discuss.px4.io/vvid/32/8440_2.png) [@vvid](https://discuss.px4.io/u/vvid)\ **Post date:** [January 8, 2017, 4:31pm UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/5 "2017-01-08T16:31:42Z")
Do you have sufficient power? How are you powering your pixhawk? Make sure your main servo power rail has stable 5V. ---
**Author:** ![Mzahana](https://discuss.px4.io/user_avatar/discuss.px4.io/mzahana/32/3790_2.png) [@Mzahana](https://discuss.px4.io/u/Mzahana)\ **Post date:** [January 16, 2017, 1:24pm UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/6 "2017-01-16T13:24:36Z")
Hi all, I am getting same problem. This is the output of Pixhawk2.1 console: sercon: Registering CDC/ACM serial driver sercon: Successfully registered the CDC/ACM serial driver WARN [param] selected parameter default file /fs/mtd\_params WARN [rgbled] no RGB led on bus #2 nsh: blinkm: command not found WARN [px4io] check CRC failed: -22 INFO [px4io] default PWM output device [PX4IO] using firmware from /etc/extras/px4io-v2.bin [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bad sync 0xff,0xff [PX4IO] bootloader not responding WARN [px4io] check CRC failed: -22 INFO [dataman] Power on restart, data manager file ‘/fs/microsd/dataman’ size is 47640 bytes MS5611\_SPI on SPI bus 4 at 2 (20000 KHz) MS5611\_SPI on SPI bus 1 at 3 (20000 KHz) WARN [bst] no devices found INFO [ver] match: PX4FMU\_V2 WARN [hmc5883] no device on bus 2 read\_reg failWARN [lis3mdl] no device on bus 2 WARN [hmc5883] no device on bus 1 WARN [mpu6000] no device on bus 3 WARN [mpu6000] no device on bus 4 WARN [mpu6000] no device on bus 4 MPU9250 on SPI bus 4 at 1 (1000 KHz) L3GD20 on SPI bus 4 at 4 (11000 KHz) LSM303D on SPI bus 4 at 3 (11000 KHz) WARN [mpu6000] no device on bus 3 WARN [mpu6000] no device on bus 4 MPU9250 on SPI bus 1 at 4 (1000 KHz) HMC5883\_SPI on SPI bus 1 at 5 (11000 KHz) WARN [hmc5883] no device on bus 3 ERROR [meas\_airspeed] no MS4525 airspeed sensor connected ERROR [meas\_airspeed] no MS4525 airspeed sensor connected ERROR [ets\_airspeed] no ETS airspeed sensor connected ERROR [ets\_airspeed] no ETS airspeed sensor connected nsh: sf1xx: command not found WARN [commander] No RGB LED found at /dev/rgbled0 INFO [sensors] Baro sensor switch from #-1 INFO [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS1 @ 57600B INFO [mavlink] mode: OSD, data rate: 1000 B/s on /dev/ttyS2 @ 57600B INFO [ver] match: PX4FMU\_V2 px4flow [204:100] WARN [px4flow] scanning I2C buses for device… INFO [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B ERROR [mixer] can’t open /dev/pwm\_output0 ERROR [mixer] failed to load mixer ERROR [init] Error loading mixer: /etc/mixers/quad\_x.main.mix INFO [lib\_\_ecl] EKF IMU buffer length = 21 INFO [lib\_\_ecl] EKF observation buffer length = 16 NuttShell (NSH) nsh\> INFO [lib\_\_ecl] EKF using pressure height - commencing alignment WARN [mavlink] Disabling hardware flow control WARN [mavlink] Disabling hardware flow control INFO [lib\_\_ecl] EKF alignment complete WARN [commander] Not ready to fly: Sensors not set up correctly Does that indicate that the IO board fried?? Please advise! ---
**Author:** ![vvid](https://discuss.px4.io/user_avatar/discuss.px4.io/vvid/32/8440_2.png) [@vvid](https://discuss.px4.io/u/vvid)\ **Post date:** [February 3, 2017, 6:05pm UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/7 "2017-02-03T18:05:36Z")
Apply enough power to all the rails and execute this in console: `px4io forceupdate 14662 /etc/extras/px4io-v2.bin` ---
**Author:** ![proficnc](https://discuss.px4.io/user_avatar/discuss.px4.io/proficnc/32/6905_2.png) [@proficnc](https://discuss.px4.io/u/proficnc)\ **Post date:** [February 8, 2017, 5:12am UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/8 "2017-02-08T05:12:02Z")
Please try the suggestion of vvid first, and if that doesn’t work… try loading Ardupilot, see if it works, then Reload PX4. ---
**Author:** ![whyscience](https://discuss.px4.io/letter_avatar_proxy/v4/letter/w/a3d4f5/32.png) [@whyscience](https://discuss.px4.io/u/whyscience)\ **Post date:** [June 30, 2017, 1:22am UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/9 "2017-06-30T01:22:42Z")
refer to this: [https://pixhawk.org/users/flash\_px4io](https://pixhawk.org/users/flash_px4io) If you still have an older firmware on your PX4IO, auto-updating might fail after you flashed the latest PX4 firmware on your FMU. In this case, hold down the safety switch while powering up the system. PX4IO will then boot into bootloader mode which allows the FMU to properly update its firmware. You only need to do this once. Following upgrades of the PX4 firmware will successfully perform an auto-update again. ---
**Author:** ![Joheart](https://discuss.px4.io/user_avatar/discuss.px4.io/joheart/32/3235_2.png) [@Joheart](https://discuss.px4.io/u/Joheart)\ **Post date:** [April 5, 2019, 9:13am UTC](https://discuss.px4.io/t/px4io-problem-on-pixhawk-2-1/2127/10 "2019-04-05T09:13:34Z")
Hi, I know this is old but I am wondering if you found a way to solve your problem, I have similar issues