@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.
@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
@jonty I would suggest you use a specific ip address and a sensible port number to listen on.
I would use 127.0.0.1 and port 9090, by doing so you know exactly which ip you are listening on.
What terminal commands are you trying to use to kill processes?
@shironats My guess is your u-boot is failing so the device is crashing, probably caused when your firmware flash failed. Have you connected to a terminal to see what if anything is occuring? I guess you'll need a dock for that so probably not.
@Koos-du-Preez If you have a lot of packages to update maybe you should be use oupgrade to ensure you are on the latest build.
@Andriy-Malyshenko You can download OpenWrt 19.07.5 from the OpenWrt site:
You don't get some of the Onion developed components but you can always install those yourself.
@column-column OpenWrt doesn't have man pages nor a man command. The maintainers have not created man pages for the platform.
@column-column OpenWrt doesn't have man pages, it's designed for minimalist hardware so it doesn't make a lot of sense to fill the device with documentation. Instead you can use the online documentation:
@slx Take a look at the OpenWrt documentation on how to add feeds to your build system. You may run into issues with dependencies however.
https://openwrt.org/docs/guide-developer/helloworld/chapter4
@Alberto-Brosich This is a nice article on debugging wifi issues:
The log should give you more information about what is going on.
If you are associated but not getting an IP it may be an issue with your dhcp client, to confirm this set the proto to static and hard code the ip. After restarting the network see if you can ping your network router and 8.8.8.8 (google dns)
The results of this will provide more info as to where your issue may lie.
@MickPF This depends on how you are doing your development. New players often start off doing some development on their Omega2x device, eventually, you realise this a short term solution since IoT devices are by design resource poor.
The best way to do Omega2x development is to install the build system https://github.com/OnionIoT/source then you will have access to everything you need as well as the cross compiler, so you can use your more powerful desktop/notebook device for your development and then move the completed work to your Omega via scp/ftp.
The headers and libraries you are looking for are on the Onion Github,
Also refer to the docs on how to compile on the Omega:
@tomgrz Onion does not customise the kernel. You can find the source Onion's fork of OpenWRT and u-boot on the Onion GitHub
@Denis-Ber The easy way to understand how to use UCI is try this:
uci show wireless
Look at the result and you should see the wifi password something like this:
wireless.sta.key='b840e8634d3d81e89e442cdbc'
Then use the command:
uci set wireless.sta.key='your new key'
uci commit wireless
service network restart
@JeffZhou Yes kewl I see that now, the problem with very long threads
@JeffZhou if you see my test above I used output mode, but @Moonshiner was showing the issue in output mode according to his test above. Your advice is that the issue in input mode, so it is unclear why @Moonshiner was getting a different result in his test than I did. Has this issue been resolved and only applies to specific production batches?
@Denis-Ber Just check OpenWrt.org for the package I just haven't done it this way but you should be able to find the package there.