Changes between Version 20 and Version 21 of v2x

Timestamp:

10/22/2025 07:01:24 PM (3 days ago)

Author:

Ryan Erbstoesser

Comment:

add som352 section

v2x

@@ -4 +4 @@
 V2X is a technology to allow a vehicle to communicate with other items. This uses a special RF Radio. 
 
-More details are provided in the [https://www.gateworks.com/vehicle-v2x/ Gateworks V2X Guide]
+More V2X generics are provided in the [https://www.gateworks.com/vehicle-v2x/ Gateworks V2X Guide]
 
 [[Image(som301.png,200px)]]
@@ -54 +54 @@
 == GPS PPS Signal
 The GPS PPS Signal uses pin 49.
-
-== SOM-301x Datasheet / Manual
- * [https://www.unex.com.tw/products/v2x/v2xsolution/v2xmodule]
- * [https://www.unex.com.tw/guide/SOM-301x.pdf Manual]
 
 == UART Information for GW73xx
@@ -101 +97 @@
 
 If the V2X support requires a kernel driver then it will need a device-tree binding of its own in which case one can use a dt overlay or customize the device tree.
+
+= SOM-352
+
+Unex has released a newer V2X Radio, SOM-352. Link: [https://unex.com.tw/en/product/som/]
+
+NOTE: This requires at minimum a 5V modification to the Gateworks SBC to power the card. Please see details above on this page. 
+
+Instructions for use:
+
+1. This device appears as a USB RNDS network device to the Linux OS running on the Gateworks SBC. It seems that the Ubuntu OS struggles with network naming related to enumerating this device. Therefore, in the Gateworks SBC u-boot, remove the following:
+{{{
+print bootargs
+bootargs net.ifnames=0
+setenv bootargs #CLEAR THE VARIABLE
+saveenv
+boot
+}}}
+1. Boot the Gateworks SBC and check to see if the radio is detected with the lsusb command and the following 3 devices:
+{{{
+Bus 001 Device 014: ID 0424:3803 Microchip Technology, Inc. (formerly SMSC) 
+Bus 001 Device 015: ID 04d8:00dd Microchip Technology, Inc. MCP2221(a) UART/I2C Bridge
+Bus 001 Device 016: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget
+
+}}}
+1. Verify the radio interface was created with the ifconfig -a command: (something like enx162408f5cc4c below)
+{{{
+root@noble-venice:~# ifconfig -a
+end0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
+        ether 00:d0:12:8a:f8:35  txqueuelen 1000  (Ethernet)
+        RX packets 0  bytes 0 (0.0 B)
+        RX errors 0  dropped 0  overruns 0  frame 0
+        TX packets 0  bytes 0 (0.0 B)
+        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+
+enx162408f5cc4c: flags=4098<BROADCAST,MULTICAST>  mtu 1500
+        ether 16:24:08:f5:cc:4c  txqueuelen 1000  (Ethernet)
+        RX packets 0  bytes 0 (0.0 B)
+        RX errors 0  dropped 0  overruns 0  frame 0
+        TX packets 0  bytes 0 (0.0 B)
+        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+
+lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
+        inet 127.0.0.1  netmask 255.0.0.0
+        inet6 ::1  prefixlen 128  scopeid 0x10<host>
+        loop  txqueuelen 1000  (Local Loopback)
+        RX packets 28504  bytes 2050016 (2.0 MB)
+        RX errors 0  dropped 0  overruns 0  frame 0
+        TX packets 28504  bytes 2050016 (2.0 MB)
+        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+
+
+}}}
+1. Bring up the interface and assign an IP:
+{{{
+ifconfig enx162408f5cc4c up
+ifconfig enx162408f5cc4c 192.168.1.1
+}}}
+1. The radio itself has an IP of 192.168.1.3 (even though the interface is 192.168.1.1). Try to ping 192.168.1.3. NOTE: If an ethernet cable is connected to the Gateworks SBC, disconnect it for this test to avoid any network confusion. 
+{{{
+root@noble-venice:~# ping 192.168.1.3
+PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
+64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=1.05 ms
+64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.552 ms
+^C
+--- 192.168.1.3 ping statistics ---
+2 packets transmitted, 2 received, 0% packet loss, time 1002ms
+rtt min/avg/max/mdev = 0.552/0.801/1.050/0.249 ms
+root@noble-venice:~# 
+}}}
+1. SSH into the V2X radio from the Gateworks SBC (root is username, no password)
+{{{
+root@noble-venice:~# ssh root@192.168.1.3
+root@autotalks:~# 
+}}}
+1. Run the V2X example command while SSH'd into the radio, signified by the autotalks command prompt:
+{{{
+root@autotalks:~# v2x-example
+Found file /usr/bin/sw_config_internal.txt
+Platform without TEE support
+Found file /usr/bin/sw_config.txt
+Using default value log_level_host=3
+ivn_service_broadcast_disable and v2x_service_broadcast_disable will affect only server application
+Device on M3 
+Shared memory ll_init done, memory size is 4096[bytes], rx size 2048[bytes], tx size 2048[bytes]
+ll_interface_init done - app_role 2
+GNSS device source config: internal poti disable = 1 internal baud rate = 0 internal 1Hz cycle ender = 0 internal poti type = 1 internal poti message format 1
+           external baud rate = 0 external device=1 external port = 0 external 1Hz cycle ender = 0 external poti type = 1 external poti message format 1
+GNSS device source config: offset seconds = 0
+Device and services are registered and initialized
+Device is alive
+Using default value lmac_rf_config_file_location=1
+Using default value force_csk_generate=0
+Using default value log_level_device=3
+Using default value log_burst_size=10
+Using default value lmac_loopback_enable=0
+Using default value lmac_phy_loopback_enable=0
+Using default value lmac_trace_verbose=0
+Using default value swc_version=1
+Using default value lmac_ranging_enable=0
+Using default value lmac_dcc_indication_enable=1
+Using default value physical_interfaces_in_use=0
+Using default value lmac_diversity_enable=0
+Using default value lmac_tx_q_descriptors_count=8
+Using default value lmac_rx_q_descriptors_count=8
+Time sync is disabled for application role CLIENT Or not main process
+WDM frequency for channel A: 5880 MHz
+Could not attach interface 0
+
+________________
+Going to send: 'Hello No. 1'
+
+---TX Socket Statistics---
+Successfully sent: 1
+Failed to be sent : 0
+Total sent: 1
+Successfully received: 0
+Dropped: 0
+Total received: 0
+Previous packet tsf usec : 0
+________________
+
+
+root@autotalks:~# 
+
+}}}
+
+=== Troubleshooting SOM-352
+1. Verify the device is seen on lsusb:
+{{{
+Bus 001 Device 014: ID 0424:3803 Microchip Technology, Inc. (formerly SMSC) 
+Bus 001 Device 015: ID 04d8:00dd Microchip Technology, Inc. MCP2221(a) UART/I2C Bridge
+Bus 001 Device 016: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget
+
+}}}
+1. Verify the RNDIS driver found the radio and created a network interface:
+{{{
+root@noble-venice:~# dmesg | grep rndis
+[   18.009833] rndis_host 1-1.1.1.1:1.0 eth0: register 'rndis_host' at usb-ci_hdrc.0-1.1.1.1, RNDIS device, 22:ee:ea:b0:1c:91
+[   18.009989] usbcore: registered new interface driver rndis_host
+[   18.030099] rndis_host 1-1.1.1.1:1.0 enx22eeeab01c91: renamed from eth0
+
+}}}
+1. Verify the RNDIS module is seen:
+{{{
+root@noble-venice:~# lsmod | grep rndis
+rndis_host             24576  0
+cdc_ether              20480  1 rndis_host
+usbnet                 57344  2 rndis_host,cdc_ether
+}}}
+1. Cannot ssh into 192.168.1.3? Be sure all other network interfaces are removed (unplug ethernet cables, unplug !WiFi cards, etc)