Hi Community.
My first entry here.
New to UNO Q, I've choosed it to try to develop an HMI interface for my CAN ecosystem.
All my HW is STM32F3 native, with CAN messaging and control, but it lacks a nice HMI, so I begin to explore the option to do it with UNO Q.
The issue is that I want to read all CAN data with MCU, compile it, perform some tasks with it, and send data to/receive from main processor running Linux and showing data on a screen.
The later part is not yet in scope, just beginning, but the first thing I would like to have is the ability to read CAN telegrams and prompt them by Serial.println or similar.
But I can't see how to use CAN or how to find a CAN library for UNO Q on board STM32.
Besides that, I would prefer to work directly with Zephyr and HW debug STM32..
Is there any way to do that, or should I switch to BeagleBoard + C?
Thanks in advance,
Beamspot.
You can use an STM32 MCU with Built-In FDCAN such as- Nucleo-G431KB / Nucleo-G474RE.
I’m not completely sure but as far as I can tell the UNO Q doesn’t expose any CAN support on the STM32 side yet The hardware has CAN, but Arduino hasn’t provided drivers or a way to access it and you also can’t load your own Zephyr build onto the MCU
So at the moment you can’t really use the UNO Q as a CAN interface If CAN is essential a board that lets you access the MCU directly (like an STM32 with Zephyr or an ESP32 + external CAN transceiver) might be a safer choice for now
Hi everybody.
Thanks for the reply.
Actually I'm using STM32F429 Nucleo-144 onto a dev board I've developed with dual CAN and other "thingies".
It works without any OS, and sends back data to PC by USB/VCP, but simple CSV data collection.
Probably I will develop some GUI or HMI with simple imputs under Processing language (good at showind graphics and similar, but really bad at handling user inputs).
There is still some time to go before I move to the User side, since the control algos and overall functionality of the prototype are not defined.
Since some of the real processing has to be done somewhere else, right now it seems that I will keep things this way, and perform data processing and algorithms in the STM32F429 and/or distributed among the network (this application mades this easy to do).
Probably I will move from bare metal to FreeRTOS or even give a try to Zephyr or even Azure (and TCP/IP server from the same STM).
Anyway, I will keep an eye on the evolution of UNO Q.
Thanks for the support!
Guillem.