On Oct 26, 2017 1:34 AM, "William" <[email protected]> wrote:

Hello,

The scope of my project is to get CAN messages from CAN bus and display
some information on an LCD.

The HW components used:
- BeagleBone Black
- CAN cape https://www.waveshare.com/rs485-can-cape.htm
- LCD cape gen4-4DCAPE-43T http://www.4dsystems.com.au/product/gen4_4DCAPE/
SW: Debian 9.2 2017-10-10 4GB SD IoT

I installed bb.org-overlays.

root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots
 0: P---L-   0 4D 4.3 LCD CAPE - 4DCAPE-43T,00A1,4D Systems,BB-BONE-4D4R-01
 1: PF----  -1
 2: PF----  -1
 3: PF----  -1

When I try to enable the CAN cape:
echo BB-CAN1 > /sys/devices/platform/bone_capemgr/slots
-bash: echo: write error: File exists


I also tried to enable the cape from uEnv.txt file:
cape_enable=bone_capemgr.enable_partno=BB-CAN1
[    3.557591] bone_capemgr bone_capemgr: slot #4: BB-CAN1 conflict P9.26
(#0:BB-BONE-4D4R-01)
[    3.566124] bone_capemgr bone_capemgr: slot #4: Failed verification
[    3.586720] bone_capemgr bone_capemgr: loader: failed to load slot-4 BB-
CAN1:00A0 (prio 0)

In BB-BONE-4D4R-01-00A1.dts device tree source file, pin P9.26 on BBB
UART1_RX is used by LCD cape.
So far, I am able to use one cape at a time.

How can I change the device tree files in order to be able to use both
capes simultaniously?
Since CAN cape provide a UART selection, can other UART be configured as
CAN interface?

Being in this stuck point for some time, any idea is very appreciated.
Thank you.


P9.26 is the touchscreen interrupt pin. So if you don't mind losing that
feature of the LCD.

Regards,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjHtY0QFxwX8hBpwH211p5jFYfhHCzTc_q8o65L4ao%3DXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to