px4io can't autostart and can't update

[Evaneee]

several days ago
I use ls /dev can see pwm_output1 in the directory,But now I can not see it again

I found that px4io is not start, so download px4fmu-v5_default.px4 from
[(http://px4-travis.s3.amazonaws.com/Firmware/stable/px4fmu-v5_default.px4)]
and use QGC flash it into pixhawk4
Type px4io update ,there are some error message

Press safety_swith when power on
System console Start message is

[boot] Rev 0x0 : Ver 0x0 V500
[boot] Fault Log info File No 4 Length 3177 flags:0x01 state:1
[boot] Fault Log is Armed
sercon: Registering CDC/ACM serial driver
sercon: Successfully registered the CDC/ACM serial driver
HW arch: PX4_FMU_V5
HW type: V500
HW version: 0x00000000
HW revision: 0x00000000
FW git-hash: ea48cd4970977f4d189c1a9ba82483ac03852299
FW version: Release 1.9.0 (17367295)
OS: NuttX
OS version: Release 7.28.0 (119275775)
OS git-hash: 423371c7d4012e725ac4ca51323a18df64e581b3
Build datetime: May 25 2019 13:55:08
Build uri: localhost
Toolchain: GNU GCC, 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
PX4GUID: 0002000000003839373831385106002f0044
MCU: STM32F76xxx, rev. Z
[hardfault_log] Fault Log is Armed

INFO  [tune_control] Publishing standard tune 1
INFO  [param] selected parameter default file /fs/mtd_params
Board defaults: /etc/init.d/rc.board_defaults
WARN  [rgbled] no RGB led on bus #1
rgbled1 on I2C bus 1 at 0x39 (bus: 100 KHz, max: 100 KHz)
WARN  [blinkm] I2C init failed
WARN  [blinkm] init failed
WARN  [px4io] check CRC failed: -1
INFO  [tune_control] Publishing standard tune 18
ERROR [px4io] Failed to communicate with IO, abort.
ERROR [px4io] driver init failed
WARN  [px4io] px4io is not started, still attempting upgrade
[PX4IO] using firmware from /etc/extras/px4_io-v2_default.bin
[PX4IO] found bootloader revision: 5
[PX4IO] erase...
[PX4IO] programming 57324 bytes...
[PX4IO] verify...
[PX4IO] update complete
INFO  [tune_control] Stopping playback...
INFO  [tune_control] Publishing standard tune 19
Board sensors: /etc/init.d/rc.board_sensors
WARN  [mpu6000] no device on bus #3 (SPI1)
MPU6000 on SPI bus 1 at 0 (1000 KHz)
BMI055_ACCEL on SPI bus 1 at 3 (10000 KHz)
BMI055_GYRO on SPI bus 1 at 2 (10000 KHz)
IST8310 on I2C bus 1 at 0x0e (bus: 100 KHz, max: 400 KHz)
INFO  [ist8310] no device on bus 2
WARN  [hmc5883] no device on bus 1 (type: 2)
WARN  [hmc5883] no device on bus 2 (type: 2)
WARN  [hmc5883] no device on bus 4 (type: 2)
WARN  [qmc5883] no device on bus 1 (type: 2)
WARN  [qmc5883] no device on bus 2 (type: 2)
WARN  [qmc5883] no device on bus 4 (type: 2)
IST8310 on I2C bus 3 at 0x0e (bus: 100 KHz, max: 400 KHz)
ERROR [pmw3901] driver start failed
MS5611_SPI on SPI bus 4 at 0 (20000 KHz)
WARN  [bst] no devices found
INFO  [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B
Starting Main GPS on /dev/ttyS0
Starting MAVLink on /dev/ttyS1
INFO  [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS1 @ 57600B
No autostart ID found
px4flow [206:100]
INFO  [px4flow] scanning I2C buses for device..
INFO  [logger] logger started (mode=all)

NuttShell (NSH)
nsh> 

And this time ls /dev

Use px4io update ,the same error as before
Anyone knows why? Thanks!

[Evaneee]

I found out why this happened!!!!!!!!!!!!!!!!
I use usb to power pixhawk4
change to battery
All of things back!!!!!!