Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pixhack v5 does not boot config related #11223

Closed
tops4u opened this issue Jan 15, 2019 · 1 comment
Closed

Pixhack v5 does not boot config related #11223

tops4u opened this issue Jan 15, 2019 · 1 comment

Comments

@tops4u
Copy link
Contributor

tops4u commented Jan 15, 2019

Describe the bug
After installation of Stable 1.8.2 (though it identifies itself as 1.8.1) I changed some Parameters. Now the Boot Process stops (see log below). I have installed Current Master today in order to retrieve the Config. Current Master boots but has a Problem with IO.

Log Files and Screenshots
Check attached Configuration (read with 1.9.0alpha) Pixhackv5_Bootfreeze.params.zip

Boot log as follows:

INFO  [drivers_board] Rev 0x5 : Ver 0x1 V551
[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: PX4FMU_V5
HW type: V551
HW version: 0x00000001
HW revision: 0x00000005
FW git-hash: 82aa24adfca29321cfd1209e287eab6c2b16780e
FW version: Release 1.8.1 (17302015)
OS: NuttX
OS version: Release 7.22.0 (118882559)
OS git-hash: 63775322bf25adb406594f8e610122fe0cef2f7a
Build datetime: Oct 20 2018 00:16:26
Build uri: BUILD_URI
Toolchain: GNU GCC, 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
MFGUID: 3833393330385108001b0024
MCU: STM32F76xxx, rev. Z
UID: 1B0024:30385108:38333933
[hardfault_log] Fault Log is Armed

INFO  [tune_control] Publishing standard tune 1
INFO  [param] selected parameter default file /fs/mtd_params
rgbled on I2C bus 1 at 0x55 (bus: 100 KHz, max: 100 KHz)
nsh: rgbled_pwm: command not found
MS5611_SPI on SPI bus 4 at 0 (20000 KHz)
WARN  [bst] no devices found
MPU6000 on SPI bus 1 at 1 (1000 KHz)
INFO  [mpu6000] accel cutoff set to 30.00 Hz
INFO  [mpu6000] gyro cutoff set to 80.00 Hz
MPU6000 on SPI bus 1 at 0 (1000 KHz)
INFO  [mpu6000] accel cutoff set to 30.00 Hz
INFO  [mpu6000] gyro cutoff set to 80.00 Hz
BMI055_ACCEL on SPI bus 1 at 3 (10000 KHz)
BMI055_GYRO on SPI bus 1 at 2 (10000 KHz)
HMC5883_I2C on I2C bus 1 at 0x1e (bus: 100 KHz, max: 400 KHz)
WARN  [hmc5883] no device on bus 2 (type: 2)
WARN  [hmc5883] no device on bus 4 (type: 2)
INFO  [ist8310] no device on bus 1
INFO  [ist8310] no device on bus 2
IST8310 on I2C bus 3 at 0x0e (bus: 100 KHz, max: 400 KHz)
ERROR [sf1xx] driver start failed
INFO  [commander] Mission #2 loaded, 9 WPs, curr: 0
INFO  [load_mon] stack check enabled
@tops4u
Copy link
Contributor Author

tops4u commented Jan 28, 2019

Closo: Probably due to faulty extras.txt on SD Card from another Controller HW.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant