@jonty Sorry I missed part of your original post where you mentioned you are connecting from a windows machine.

127.0.0.1 is a local only ip which means while your omega can listen on that IP no other machine can connect to it, so instead you need to bind to the public ip on the omega. I assume you are connecting via wifi, so type ifconfig on the omega and find the apcli0 interface and record the IP, probably something like 192.168.x.x or 10.x.x.x. Now change your server code to bind to that IP. On the client machine connect to that IP.

If the client on your windows machine still won't connect you may need to check your windows firewall is not blocking the port.

@slx Please provide more information about the issue. What errors are you receiving? What modifications have you made? Which document are you referring to.

@UFD I hit this issue some time ago, I use a hotplug script to achieve a similar outcome to what you require.

Here is my script:

#!/bin/sh

File: 40-setup

Author: chris

Created on 24 Jun. 2019, 1:07:07 am

#!/bin/sh

Place me in /etc/hotplug.d/iface/40-setup

WIFI_INTERFACE="wwan"
m1=$(cat /sys/class/net/ra0/address | awk -F':' '{ print $3$4$5$6 }' | awk '{print toupper($0)}')

echo "Starting interace hotplug ${DEVICE} Action: ${ACTION} Interface: ${INTERFACE}" >> /tmp/cblog
if [ "$ACTION" = "ifup" -a "$INTERFACE" = "wwan" ]; then
echo "IFUP ${DEVICE}" >> /tmp/cblog
rm -f /etc/hotplug.d/iface/40-setup
echo "Run script for device: ${DEVICE}" >> /tmp/cblog
echo "nameserver $(ip -o -4 a s apcli0 | awk '{ print $4 }' | cut -d/ -f1)" >> /etc/resolv.conf

//## Insert command to use MAC
fi

@Walter-Filho The relevant information has been included in the current documentation:

https://docs.onion.io/omega2-docs/extending-omega-memory.html

@sannin The header file is available as part of the sqlite3-dev package but you'll need to set up the build system to access it. Alternatively, you could download the header from the sqlite3 GitHub repository, but I expect you'll hit some other issues if you take this course.

If you are developing C/C++ code for any IoT device with limited resources you really should set up the build system so you can cross compile and thereby have access to a huge range of development resources.

@Nagarjuna-Reddy I can't test this right now, but first I think you need to remove the sdcard module as it will likely be managing the registers:

rmmod mtk_sd

Then I expect you can use the GPIO like so:

gpioctl dirout-high 22
gpioctl get 22
gpioctl dirout-low 22
gpioctl get 22

cat /sys/class/gpio/gpio22/value

@shironats Sorry I am a man of many faults and failure to attach attachments is one of them

https://community.onion.io/topic/2595/how-to-flash-uboot-after-full-erasing?_=1610672742832

@shironats Check out this thread, it's a bit extreme but might be useful. Personally, I think a dock is the best option, when you're doing experimental stuff you break things, so it's important to have the right tools at your disposal to be able to fix stuff.

Being able to use the serial console is pretty important because it helps you understand exactly what is happening.

@Nagarjuna-Reddy Check out the doc here

https://docs.onion.io/omega2-docs/pin-multiplexing.html

@jonty So your server is now bound correctly, so now look at the client. Did you update the client code to use the specific port 9090?

lsof is not installed by default, you need to install it:

opkg install lsof

If this fails then you need to update your distfeeds. Edit /etc/opkg/distfeeds.conf uncomment lines 2 and 5. Run opkg update; opkg install lsof

But since your server will now bind correctly you don't need lsof