Part Number: AM3359
Tool/software: Linux
We are trying to port the G3 PLC DC code to AM335X module
1. Complied u-boot
2. compiled Linux core varsomam33 4.12.10-bone3 #1 Mon Sep 4 12:54:28 MSK 2017 armv7l GNU/Linux ipv6
3. Created dtbs with required COM ports and GPIO lines
4. Compiled FS via Yocto, guided with http://variwiki.com/index.php?title=VAR-SOM-AM33_Yocto_Krogoth_Build (core-image-minimal).
5. Complete and tested loading FS image via network, through nfs.
We have a following problem: while g3plc software starts, interface can’t be created.
eth0 Link encap:Ethernet HWaddr D0:FF:50:B6:99:63
inet addr:192.168.22.23 Bcast:192.168.22.255 Mask:255.255.255.0
inet6 addr: fe80::d2ff:50ff:feb6:9963%132976/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23703 errors:0 dropped:0 overruns:0 frame:0
TX packets:12839 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21484150 (20.4 MiB) TX bytes:1947625 (1.8 MiB)
Interrupt:177
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%132976/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:306 errors:0 dropped:0 overruns:0 frame:0
TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21201 (20.7 KiB) TX bytes:21201 (20.7 KiB)
ie the interface wasn’t created tunX.
The software (when it starts) writes to the console:
root@varsomam33:~# /opt/plc/g3_dc_AM335X_aes_msb_loadng.exe -c /dev/ttyS3 -P 49163 -F 0 -M 0 -A 1 -L 001B:5016:0001:0001
#########################################################################
################# G3 Data Concentrator Version 4.7.0.6 ##############
#########################################################################
ERROR -1 from sched_setscheduler!
Original System Information from device ...
*** SYSTEM INFORMATION ***
Firmware Version.................... 7.7.7.4
Device Type......................... G3
Device Mode......................... MAC
Hardware Revision................... pre Rev. D
Host Port........................... SCI-A
Diag Port........................... SCI-B
Apply RPY........................... no
Auto Mode........................... no
G3 Address Type..................... 0
G3 Long Address..................... 001b501600010001
G3 Short Address.................... 0
G3 MAC Segment Length............... 0
Pausing to allow device to reset.
DEV_shutDown_Handler: SHUT_DOWN returned success.
DEV_setSysConfig_Handler: LOAD_SYSTEM_CONFIG returned success.
System Information of device has been set to...
*** SYSTEM INFORMATION ***
Firmware Version.................... 7.7.7.4
Device Type......................... G3
Device Mode......................... MAC
Hardware Revision................... pre Rev. D
Host Port........................... SCI-A
Diag Port........................... SCI-B
Apply RPY........................... no
Auto Mode........................... no
G3 Address Type..................... 0
G3 Long Address..................... 001b501600010001
G3 Short Address.................... 0
G3 MAC Segment Length............... 0
DEV_setInfo_Handler: HCT_MSG_TYPE_SET_INFO returned success.
DEV_setInfo_Handler: HCT_MSG_TYPE_SET_INFO returned success.
Network started successfully
Connected to PSK Server.
Please pay your attention to the red line above (ERROR -1 from sched_setscheduler!)
Unfortunately TI software doesn’t show a error code (errno), so we can’t see the reason why it is so.
There is no info in the logs too.
I suppose
any parent process couldn’t change (get higher or lower) priority of some child processes and couldn’t start them(it).
So PLC network works, tun interface doesn’t exist.
Will be glad to any help.
