Hi John, Do you see support for both CAN0 and CAN1? Need both and our pins for CAN1 are E17 and E18 in the TI pinmux tool. Found the pad names and pins in uboot pinmux for CAN0 after this post. Haven’t found pad names associated with E17/E18 yet in uboot pinmux. Will look at the kernel dts today.
My question I guess will CAN1 be available when plugging in the CANUSB and where do you see CAN1 indicated? If supported, it will appear as /dev/ttyUSB1? Or, as a different device on the BBB? Eventually may need as many as four CAN0-3. Thx, Tracy > On Oct 31, 2017, at 8:00 PM, John Dammeyer <[email protected]> wrote: > > The CANUSB from Lawicel is a standard USB device that looks like a serial > port since it can use the FTDI driver. > > On my MachineKit Debian Beagle 2.0 when I plug in the CANUSB I find I have a > /dev/ttyUSB0 device. > I installed putty and connected to /dev/ttyUSB0 > In the terminal window > V with a CR returns > V1011 > An S5 sets 250kbps > An O opens the port. > t12327788 with a CR again of course sends SID=123, DLC=2, Data 0x77 0x88 > With nothing connected to the CANUSB the red LED goes on. (or if bitrate is > wrong). > A C closes the port. > An F prints the error flags and shuts off the red led. > > It’s a good idea to have auto line feed set in putty so that each received > message is on a new line. > John Dammeyer > > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Tracy Smith > Sent: October-31-17 3:42 PM > To: BeagleBoard > Subject: [beagleboard] Re: BBB- DCAN1 problems using latest debian image > > Hi John, > > I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have a > custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2. > > The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for the > BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names > for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 > (pin E18), > > 1. Did I miss the names for these pins in u-boot? > > 2. If u-boot does not support these pins, should they be added to u-boot, > and/or added to the kernel to support these pins? > > Should these pins be pinmuxed in both uboot and the kernel, or only in the > kernel dts? Checking now to see if the kernel has support for these pins. > > thx, Tracy > > On Wednesday, April 8, 2015 at 8:20:29 AM UTC-5, Mark Irwin wrote: > Hi, > > I have been trying to build a proof of concept system using two beaglebone > black units with there DCAN1 (pins P9_24 and P9_26) and two can transcievers > TI SN65HVD251P. > The can transceivers are powered from the same 5V bench supply as both of the > beaglebone blacks. the canh and canl pins are terminated at both ends by 120R > resistors to ensure the 60R bus impedence. > > I was following the instructions in other posts about updating to the latest > debian version and then upgrading the kernel to 3.14. This i have done. > uname -a > Linux beaglebone 3.14.35-ti-rt-r56 #1 SMP PREEMPT Sun Mar 29 01:13:05 UTC > 2015 armv7l GNU/Linux > > I added dtb=am335x-boneblack-can1.dtb to the uEnv.txt > > I have also installed the canbus tools within the image so i can attempt a > cangen can0 and candump can0. > > On system boot i am doing the following: > > modprobe can > modprobe can-dev > modprobe can-raw > > ip link set can0 type can bitrate 125000 triple-sampling on > ifconfig can0 up > > however if i use candump can0 and cangen can0 within two seperate putty > sessions i dont see anything. > > If I create a vcan bus i do see the messages in loopback. > sudo modprobe vcan > sudo ip link add dev vcan0 type vcan > sudo ifconfig vcan0 up > > Previously I was using an older debian image and found that when i ran cangen > can0 that the buffer would give me an error that it was full. however now > with the latest image i am not getting the bufer full message but still not > seeing anything on the candump. What should i expect to see here? > > Can anyone see where I have gone wrong or a step i am missing? > > Thanks in advance. > > Mark > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the Google > Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/_9u1B6ZkgCU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/e6297438-0999-4320-916e-f41d74671533%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the Google > Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/_9u1B6ZkgCU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/003001d352ac%24d3f24980%247bd6dc80%24%40autoartisans.com. > For more options, visit https://groups.google.com/d/optout. -- 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/48C2AA15-9F29-44DD-BE79-5122B54449C2%40gmail.com. For more options, visit https://groups.google.com/d/optout.
