beagleboard / beagleboard/librobotcontrol
[BBBlue] rc_test_drivers broken for linux kernel >=5.x.y.z
- Dominant language
- C
- Stars
- 212
- Forks
- 167
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I have reactivated a BeagleBoneBlue that was catching dust on my shelf and while updating the kernel
via
`sudo /opt/scripts/tools/update_kernel.sh --lts-5_4`
I found out that librobotcontrol seems broken on all kernels after 4.19.94-ti-r73.
```
Kernel: 5.4.106-ti-r41
BeagleBoard.org Debian Buster IoT Image 2020-04-06
Debian: 10.13
PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
ERROR: ti-pwm driver not loaded for hrpwm0
ERROR: ti-pwm driver not loaded for hrpwm1
ERROR: ti-pwm driver not loaded for hrpwm2
ERROR: ti-eqep driver not loaded for eqep0
ERROR: ti-eqep driver not loaded for eqep1
ERROR: ti-eqep driver not loaded for eqep2
PASSED: pru-rproc
PASSED: uart1
PASSED: uart2
PASSED: uart4
PASSED: uart5
ERROR: i2c1 driver not loaded
PASSED: i2c2
ERROR: spi driver not loaded
PASSED: LED
PASSED: ADC iio
Currently running on a:
MODEL_BB_BLUE
Robot Control library Version:
1.0.5
```
Is this a librobotcontrol issue or is this a DeviceTree issue?
https://github.com/beagleboard/bb.org-overlays
claims it is supported.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported failures with rc_test_drivers on the BeagleBoneBlue running kernel 5.4.106-ti-r41, after reviewing the kernel update command and the bb.org-overlays reference. Determine whether the missing ti-pwm, ti-eqep, I2C, and SPI drivers originate in librobotcontrol or the DeviceTree overlays; done means the cause is identified and the affected driver checks work on kernels at or above 5.x.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100