collin80 / SavvyCAN

QT based cross platform canbus tool
MIT License
986 stars 275 forks source link

Use with PocketBeagle? #234

Open pdp7 opened 4 years ago

pdp7 commented 4 years ago

@collin80 I was just asked by KC of the Car Hacking Village if the Macchina P1 (cape for the PocketBeagle) would work with SavvyCAN.

The PocketBeagle will show up on the host computer over USB as both a virtual serial port and a network interface. The host will see the PocketBeagle as:

The PocketBeagle is a 1GHz ARM Cortex A8 (TI Sitara AM3358) with 512MB RAM running Debian armhf. I think it would tough to compile run SavvyCAN directly on it and it would require X11 forwarding as the PocketBeagle has no HDMI.

Do you think there is a way to expose the Linux SocketCAN interfaces (can0 and can1) on the PocketBeagle to the host running SavvyCAN?

collin80 commented 4 years ago

Hmm, that's an interesting question. For comparison, I have compiled SavvyCAN for the RaspberryPi4 and I'm aware of multiple people doing so on the rPI3B+ units. In each case, it worked fine. It's a little bit small if you're using an 800x480 touchscreen on the rPi but it works. So, conceptually the idea of running it on smaller embedded hardware isn't so far fetched. SavvyCAN will use socketcan devices on linux so I think the answer is that compiling it and running it would expose the socketcan interfaces for use. You're right, it might be rather tough to make it work on a pocketbeagle since it has no native video. It is possible that maybe X11 forwarding or virtual VNC could work. It appears that QT does support embedded linux and that people have compiled QT programs on a Beaglebone board. So, while difficult, it does seem possible.

Entropy512 commented 4 years ago

@pdp7 - Do you want to interact with it in real time using SavvyCAN, or just view logs?

At least in the interim, you could log on the P1, and open the logs in SavvyCAN.

I have a P1 on order myself. Hoping it gets here by the weekend, but unlikely.

pdp7 commented 4 years ago

@Entropy512 thanks, copying the logs from the Beagle might be sufficient (it was someone else who was asking me so I'll have to check on their use case)