Cannot enable UART on Beaglebone

Hi,

I’m trying to get the IO ports working on a BeagleBone running the latest resinOS (2.15.1+rev1). I’m trying to use the Bonescript library in a NodeJS runtime on the resin/beaglebone-black-node:8 base image.

I want to enable and use UART4, which does not work out of the box. I need to enable it with some command in my Dockerfile/starter script. I tried to follow the solution listed here but am encountering errors.

Whenever I run echo BB-UART4 > slots, a ton of journal errors are spit out at me. Relevant ones are below:

root@14f4739:/sys/devices/platform/bone_capemgr# echo BB-UART4 > slots

Broadcast message from systemd-journald@14f4739 (Wed 2018-10-17 23:21:59 UTC):

kernel[544]: [  463.501752] Internal error: Oops: 17 [#1] PREEMPT SMP ARM


Broadcast message from systemd-journald@14f4739 (Wed 2018-10-17 23:21:59 UTC):

kernel[544]: [  463.606348] Process bash (pid: 1425, stack limit = 0xd182e218)

When I inspect dmesg to see what happened, I see the following error(s):

[  463.415231] bone_capemgr bone_capemgr: part_number 'BB-UART4', version 'N/A'
[  463.434656] bone_capemgr bone_capemgr: slot #4: override
[  463.444639] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[  463.458779] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-UART4'
[  463.475911] Unable to handle kernel NULL pointer dereference at virtual address 0000000c
[  463.485388] pgd = da670000
[  463.492973] [0000000c] *pgd=9a561831, *pte=00000000, *ppte=00000000
[  463.501752] Internal error: Oops: 17 [#1] PREEMPT SMP ARM

This is in contrast to what should be in dmesg based on the post linked above.

So, I am stuck. This would seem to be an incompatibility with the kernel itself. Any help is greatly appreciated!

Hi @freako987!

It appears as though capemgr is in the process of deprecation upstream in the Beaglebone linux fork, in favor of u-boot. We are tracking the fix for that here, and will let you know when it is merged.

Hope this helps!

Hi there,

Just to update you that the issue has been fixed in BalenaOS v2.29.2+rev1 and above. Let us know in case you are still facing the same issue.

Regards,
Steve

Hi there,
Just to update you that the issue has been fixed in BalenaOS v2.29.2+rev3 and above. Let us know in case you are still facing the same issue.
Regards,
Steve