05-07-2019, 02:45 PM
(05-06-2019, 11:36 AM)AZClusterboard Wrote:(05-06-2019, 06:10 AM)WhiteDragon Wrote:(05-05-2019, 03:32 PM)WhiteDragon Wrote: Hey Guys and Gals,Alright. It seemed to have bean the network issue described here: https://forum.armbian.com/topic/9402-eth...ne-module/
So I recently acquired a Clusterboard and wanted to take it for a spin. But no luck so far...
When I tried to start it with a single SoPine inserted nothing happened, so - dismayed - I tried another one and got a response: The lights went on and I got approximately three seconds of Christmas Tree Action. After that: Nothing...
After reading on this Forum I tried a Xenial 3.10 Build and now I get at least a heartbeat on the SoPine I inserted! But still no lights on the switch. Not even a status light on the RJ45 Socket...
Now I am worried that the board might be fried.
Do you have any ideas?
(I'm still waiting for a USB/UART Adapter. Tried it with a DIY Arduino Thingy but that did not work. No UART Signal so far, or none detectable by the Arduino.)
Logged in via a USB-Network Dongle and applied the fix. Didn't work then though. But the switch switched on the moment I pulled the USB-Network Dongle out of the socket.
What version of Armbian are you using?
At the moment I'm using Armbian 5.84 Debian Stretch with a 4.19.38 Kernel I built from source. It didn't work out of the box though.
I had to apply this fix described in the Armbian forums linked above.
I figure that the USB Network Dongle was mapped to a lower Hardware ID and the SoPine can only maintain a single network connection, thus the onboard NIC on the SoPine Module was deactivated. I figured furthermore that the switch on the Clusterboard is only powered, when at least one of the NICs on the SoPine Modules tries to communicate with it (I guess some sort of XOR gate controlling V_in or somesuch nonsense).
Since that did not happen due to the network bug the switch stayed "dark".
