2023-03-31, 05:12 PM
So as long as you run pypilot from the same folder it works after editing the file?
Are you really using icm20948 over SPI bus? I wrote the icm20948 driver and never used it with anything besides i2c.
It is impractical to probe all spi busses including spi bus 5 without some kind of hint, normally I put an eeprom on the gpio header which creates a config file available on:
/proc/device-tree/hat/custom_0
Currently it autodetects the mpu ignoring this hint but this is where it would be expanded from to specify spi bus 5. This way if you had a board for orange pi, it would have the eeprom programmed to specify that hardware setup, eventually even which gpio pins to use for keys if any.
the lcd and arduino hints are already used.
Are you really using icm20948 over SPI bus? I wrote the icm20948 driver and never used it with anything besides i2c.
It is impractical to probe all spi busses including spi bus 5 without some kind of hint, normally I put an eeprom on the gpio header which creates a config file available on:
/proc/device-tree/hat/custom_0
Code:
{"mpu":{"driver":"icm20948",
"port":"/dev/i2c-1"},
"lcd":{"driver":"jlx12864",
"port":"/dev/spidev0.0"},
"arduino":{"device":"/dev/spidev0.1",
"resetpin":26,
"hardware":0.35}
}Currently it autodetects the mpu ignoring this hint but this is where it would be expanded from to specify spi bus 5. This way if you had a board for orange pi, it would have the eeprom programmed to specify that hardware setup, eventually even which gpio pins to use for keys if any.
the lcd and arduino hints are already used.