Ethernet and Battery Monitoring Issues After Flashing Custom Image on DSGW-210-B-26 (Using SDK)

Hello Dusun Team,

I’m currently working with a DSGW-210-B-26 gateway and following the SDK instructions provided on your Wiki (DSGW-210 RK3328 Gateway Hub Platform | Dusun wiki for the Debian SDK) to build custom images. I’ve generated images for both Buildroot and Debian option at time of run at build.sh init in the Virtual machine running Ubuntu 18.04 as per the documentation and flashed the device using AndroidTool. However, after flashing with either image, I’m unable to access the gateway via Ethernet as I previously could. Connecting through UART, I see the following log error/warning where it is not detecting the ethernet port anymore:

Net: Net Initialization Skipped
No ethernet found.

Originally, I used the Ethernet port and SSH for local network access, which is crucial for my work. Re-flashing the gateway with the stock image (DSGW-210-Debian_image_RV1.3.3.zip) restores Ethernet functionality, but this stock firmware lacks the driver support I need to monitor battery status on the device, one of the main reasons I used the SDK was for having access to the battery monitoring hardware.

Given that I’m compiling the image with the SDK, I would expect the necessary drivers for Ethernet to be included. Are there any specific configurations or additional steps required to enable the Ethernet driver in the custom SDK images? Any suggestions beyond what’s available in the guides would be greatly appreciated, as they are somewhat limited in scope.

Thanks in advance for any guidance!

logs attached:
DSGW-210_UART_LOGS_PUTTY_No_Ethernet_after_Flash.txt (55.8 KB)

Regards,
Jose

Hi! can I just ask, where did you get the DSGW-210-Debian_image_RV1.3.3 image? Any chance of sharing it?

I have the files for the battery monitoring, but I cannot install it on my gateways as its compiled for an older kernel version…

bq25890_charger.ko (311.2 KB)
bq27xxx_battery.ko (314.7 KB)

Hello @SMARTi, I downloaded it from Dusun’s wiki page wiki.dusuniot.com/iot-gateway-hardware/dsgw-210-rk3328-gateway The ready-to-flash image I used was from the Image Firmware Packaging section, which directs you to Google Drive for download

Thank you @jisea! Found it :slight_smile:
Did you try and install the files I gave you? I’m not sue what kernel version the Debian image is, but its too old for my version of the Debian image that comes pre-loaded

@SMARTi thanks your files worked for me and now I am able to get the battery information in the default image.

@DusunIoT is there any workaround to enable the Ethernet port for an SDK-generated image? I tried looking at menuconfig in Buildroot, but there are no options available there.

can you check whether eth0 port is down?
if it is up , is it assigned with ip address?

Hello @Dusun_Yan,
The DSGW-210 gateway does not seem to enable the eth0 port with the Debian image I generated according to the SDK documentation. I tried both Debian and Buildroot, but the results were the same: no Ethernet connection. I am attaching logs captured via PuTTY over UART when using the Debian SDK-generated image (Logs_flashed_imagen_from_SDK_Debian.txt (55.5 KB)
The logs indicate a message: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready, suggesting that eth0 may not be functional or at least not communicating (gateway LEDs stay red), and I cannot see it on my local network.

In contrast, when I use the stock Debian image available from the ‘Debian Image Firmware Packaging’ section, the gateway is visible on my local network then LEDs turn blue, indicating a connection, and I can connect to it via SSH (Eth0 working). logs: Logs_flashed_imagen_stock_DSGW-210-Debian_image_RV1.3.3.txt (77.9 KB)
).

On another note, while I can view logs over UART, I haven’t been able to use it as a console to send commands, even though the wiring is correctly connected (TP1100 for RX and TP1101 for TX). This limitation makes it essential to restore Ethernet (eth0) functionality to communicate with the DSGW 210.

Regards,
Jose

did you made any modification to the SDK?
I just compiled it and eth port works well.

@Dusun_Yan I built the SDK without any modifications, ensuring all prerequisites were installed on my VM running Ubuntu 18.04:

sudo apt-get install git ssh make gcc libssl-dev liblz4-tool expect libc6-dev libc6-dev-i386 \
g++ patchelf chrpath gawk texinfo chrpath diffstat binfmt-support python3 python3-pip \
python-dev swig live-build bison flex fakeroot cmake gcc-multilib autoconf \
g++-multilib unzip device-tree-compiler ncurses-dev

Could you let me know which version of the SDK you’re using? I used the one available in the Debian SDK section It says DSGW-210-SDK-V1.0

Firmware version: 36.64.6269

actually we are using same SDK
can you check the version

cat /etc/dusun_build

@Dusun_Yan I can’t run ‘cat /etc/dusun_build’ on the DSGW-210 after flashing the image from the SDK because I’m unable to log in using SSH (due to the eth0 issue) or access the console via serial. The serial connection only works for debugging or retrieving logs, not for sending command on my end.

Could you please provide the exact steps you use to compile the image? Additionally, could you share the kernel configuration you’re using and confirm if there’s any specific option in menuconfig that needs to be enabled to support Ethernet functionality?

just follow the guide, cp the debian-rootfs.img to debian/linaro-rootfs.img
then execute ./build.sh init (choose 3) and build.sh
I didn’t make any changes, ethernet is a fundamental feature, it shall be supported by default