Posts made by dixit

@crispyoz will that button long press work anytime during the board is up or I need to power-up the board with the button pressed?

Okay @crispyoz so it mean that pressing SW_RST button(Connected to GPIO38 internally) for more than 10 sec will factory reset the board correct?

@crispyoz I don't have any dock with me. Is there any other solution?

Thank you @crispyoz I got your point.
One more thing, in trials I did ifdown wlan command on the board with the expectation that it will bring down the AP interface but it resulted differently. Now I am not able to access the board over any network. Per my understanding, rebooting the board should bring up all the configured interface back alive but this does not seem to be working here. I want to access the board and get wifi interface up and running, I know we can get access over serial console but is there any other way to factory reset the board to bring back the default configuration?
Thanks,

Hi,

I want to disable the access-point hosted by Omega once board is able to connect with the configured wifi network. How can we do that using hotplug or uci?
Also, I want to enable AP again when a gpio button is pressed.
I am unable to find system commands to on/off access point interface on the omega board. please help me with that.

Thanks,
Dixit

@luz Thanks. 5100ns Maxretries value(default suggested for ws2812 on readme Github) by this I meant the same as you said, could not convey though.
I checked the hardware design, we dont have level-shifter emplied. I will try with level shifter and let you know here.
I appreciate your prompt attention. Thank you @crispyoz @luz .

@crispyoz What do you mean by What configuration parameters have you set for the ledchain module?
I am using p44-ledchain driver as it is and providing the above mentioned parameter while inserting the module.
Which means;
use ledchain0(pwm0) in non-inverted mode, for 5 leds in chain, ws2812 ledtype, 10 retries, 5100ns Maxretries value(default suggested for ws2812 on readme Github)
Let me know what other information would be helpful?

@luz Sorry to dragging you back in the past to remind you about this beautiful creation of yours!
I am using p44-ledchain on the Omage 2+ on the pwm0(Pin 18) with 5 ws2812 LEDs with my Custom PCB board.
I used the below command line to insert the driver(as mentioned in the readme);

insmod p44-ledchain ledchain0=0,5,1,10,5100

Here the issue I am facing is that when i give command to update all 5 LEDs, it does not control all five LEDs. Sometimes it glows 3 and sometime 2.
Eg. To glow all 5 LEDs in Bright Blue color; I applied below command but it turned on only first 3 LEDs in Green, 1 bright blue, 1 dim blue.

echo -e "\x00\x00\xFF\x00\x00\xFF\x00\x00\xFF\x00\x00\xFF\x00\x00\xFF" > /dev/ledchain0

I am pretty sure that the driver if okay in terms of controlling the LEDs.
Can you help me to make this work by pointing to the points I might have missed.

TAI

@luz @crispyoz
I have successfully ported ws2812_draiveris (https://github.com/plan44/ws2812-draiveris-openwrt-package) on our Omega2+.
The LED is working fine by echo'ing 3 bytes per LED. The below cause all 5 LED to turn on in Blue color.

insmod ws2812.ko gpios=18 leds_per_gpio=5
echo -e "\x00\x00\xFF\x00\x00\xFF\x00\x00\xFF\x00\x00\xFF\x00\x00\xFF" > /dev/ws2812

But at time, with the same echo command only 2 LEDs gets affected and after that event those LED behaves like that only. Even after giving command to turn off all the LED, 2 LEDs stays on. The command to turn On 5 LEDs in Green, only takes effect for these 2 LEDs, remaining LEDs stays off. Even re-inserting the driver doesn't help.

Does anyone know, if there is any glitch in the driver? or somehing to be related to hardware. I dont' have any doubts on hardware as its working fine at times.

TIA

Hi All,

I have ported https://dev.gentoo.org/~blueness/eudev/eudev-3.2.9.tar.gz eudev on Omega 2+ to enable udev support for USB device detection. This is a stripped version of udev pakcage as openwrt 18.04 has dropped the udev official support.
After porting I got to know that the udevadm -u monitor only shows USB kernel events and not any udev events.
I read few threads over internet and found that udev events are generated by the udevd(udev daemon).
Since this version of udev does not have udevd, it won't generate udev events.
Few questions;

1. Is my understanding correct?
2. Is there udev package available which can be port in Omega which supports full udev functionality?

Note: I understand that udev is replaced by hotplug that could be an alternative but I want to try my best to port udev for backward compatibility.

TIA

@crispyoz Thanks. removing postfix package resolved the issue. appreciate all the help.

@crispyoz Thank you so much!
I hope this one is the last query for you; I followed above steps and started the compilation.
It failed with the below error;

[src/util]
make: Entering directory '/home/dixit/work/projects/omega2/local_build/source/build_dir/target-mipsel_24kc_musl/postfix-3.3.0/src/util'
mipsel-openwrt-linux-musl-gcc -DNO_NIS -DUSE_TLS -DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I/home/dixit/work/projects/omega2/local_build/source/staging_dir/target-mipsel_24kc_musl/usr/include/sasl -DHAS_LDAP -DHAS_CDB -DNO_DB -DHAS_SQLITE -I/home/dixit/work/projects/omega2/local_build/source/staging_dir/target-mipsel_24kc_musl/usr/include/ -DHAS_PCRE -I/home/dixit/work/projects/omega2/local_build/source/staging_dir/target-mipsel_24kc_musl/usr/include/ -DNO_EAI -DDEF_DB_TYPE=\"cdb\"  -g -O -I. -DLINUX5 -c alldig.c
cc1: note: someone does not honour COPTS correctly, passed 0 times
In file included from alldig.c:29:0:
./sys_defs.h:1257:2: error: #error "unsupported platform"
 #error "unsupported platform"
  ^~~~~
./sys_defs.h:1320:2: error: #error "define HAS_FCNTL_LOCK and/or HAS_FLOCK_LOCK"
 #error "define HAS_FCNTL_LOCK and/or HAS_FLOCK_LOCK"
  ^~~~~
./sys_defs.h:1324:2: error: #error "define DEF_MAILBOX_LOCK"
 #error "define DEF_MAILBOX_LOCK"
  ^~~~~
./sys_defs.h:1328:2: error: #error "define INTERNAL_LOCK"
 #error "define INTERNAL_LOCK"
  ^~~~~
./sys_defs.h:1336:2: error: #error "define USE_STATFS or USE_STATVFS"
 #error "define USE_STATFS or USE_STATVFS"
  ^~~~~
In file included from alldig.c:29:0:
./sys_defs.h:1347:57: error: unknown type name 'SOCKADDR_SIZE'
 extern const char *inet_ntop(int, const void *, char *, SOCKADDR_SIZE);
                                                         ^~~~~~~~~~~~~
Makefile:187: recipe for target 'alldig.o' failed
make: *** [alldig.o] Error 1
make: Leaving directory '/home/dixit/work/projects/omega2/local_build/source/build_dir/target-mipsel_24kc_musl/postfix-3.3.0/src/util'
Makefile:92: recipe for target 'update' failed
make[4]: *** [update] Error 1
make[4]: Leaving directory '/home/dixit/work/projects/omega2/local_build/source/build_dir/target-mipsel_24kc_musl/postfix-3.3.0'
Makefile:265: recipe for target '/home/dixit/work/projects/omega2/local_build/source/build_dir/target-mipsel_24kc_musl/postfix-3.3.0/.built' failed
make[3]: *** [/home/dixit/work/projects/omega2/local_build/source/build_dir/target-mipsel_24kc_musl/postfix-3.3.0/.built] Error 2
make[3]: Leaving directory '/home/dixit/work/projects/omega2/local_build/source/feeds/packages/mail/postfix'
Command exited with non-zero status 2
time: package/feeds/packages/postfix/compile#0.19#0.03#0.38
package/Makefile:107: recipe for target 'package/feeds/packages/postfix/compile' failed
make[2]: *** [package/feeds/packages/postfix/compile] Error 2
make[2]: Leaving directory '/home/dixit/work/projects/omega2/local_build/source'
package/Makefile:103: recipe for target '/home/dixit/work/projects/omega2/local_build/source/staging_dir/target-mipsel_24kc_musl/stamp/.package_compile' failed
make[1]: *** [/home/dixit/work/projects/omega2/local_build/source/staging_dir/target-mipsel_24kc_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/dixit/work/projects/omega2/local_build/source'
/home/dixit/work/projects/omega2/local_build/source/include/toplevel.mk:216: recipe for target 'world' failed
make: *** [world] Error 2

Which I think same as https://community.onion.io/topic/4568/docker-build-env-make-issues/6?_=1654410911792
I followed those/below steps to get rid of the error but when I do that feed update & install, .config.02 gets modified where a lot of packages are removed(Means the =y gets replaced with ' is not set')

./scripts/feeds clean
./scripts/feeds update -a
./scripts/feeds install -a
sh scripts/onion-feed-setup.sh
ln -s .config.O2 .config
make menuconfig
In "Target System" select "MediaTek Ralink MIPS"
In "Sub Target" select "MT76x8 based boards"
In "Target Profile" select "Multiple Devices"
In "Target Devices" select your Onion Omega model, or models

exit and save

make clean
make -j4

I believe the solution to this build error has to be something else as well apart from what is provided on that thread.

Can you please help me get going in this!

@crispyoz Any references of correct way to add packages in to the build and have the generated artifacts to be part of final generated .bin.?

@crispyoz Thank you! This seems similar to that standard process. I will try setup new codebase following this.

@crispyoz I followed this https://github.com/OnionIoT/source to setup the build on my Ubuntu machine and followed the make method to generate build same as it released by Onion releases.
I did run below commands to have all the release packages in onion release in my custom release;

python scripts/onion-setup-build.py -c .config.O2
make clean
make

As I have Omega 2S+ board I flashed openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin from bin/targets/ramips/mt76x8/ directory.

Let me know if I missed anything to build custom OS which left me in this issue.

@crispyoz Yes I tried, the problem is still there.
I have expansion dock.
Moreover I got access the board via serial console and from that I got to know that the firmware I flashed is not having all the utilities/tools that are provided with the stock Omega build(even wifisetup binary is also not there).
The ifconfig output looks like below;

br-lan    Link encap:Ethernet  HWaddr 40:A3:6B:C0:27:84  
          inet addr:192.168.100.1  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fd1d:48c4:7633::1/60 Scope:Global
          inet6 addr: fe80::42a3:6bff:fec0:2784/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1784 (1.7 KiB)

eth0      Link encap:Ethernet  HWaddr 40:A3:6B:C9:09:B2  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:3413 (3.3 KiB)
          Interrupt:5 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2080 (2.0 KiB)  TX bytes:2080 (2.0 KiB)

In my understanding, there should have been interface for WiFi AP.
So the issue what I think is that the .config which I built is not having all the options needed for Omega2+ to work like stock Omage build. Let me know if you think this not the actual problem.
Can you help me how I can setup the same build as stock Omaga?

Thanks

@crispyoz thank you.
I added the eudev package in to the Omega source ans recompiled the OS.
I tried updating the OS on the board by following manual upgrade process using sysupgrade command but the board seem bricked. Because after the flash I can't see wifi AP via which I was accessing it. Any suggestions to recover the board?
I am new to Omega so this is first time I am going through all of this.

@crispyoz thanks. Incase I want to use udev with mentioned go library, can I port the eudev package ? If yes, I would really appreciate any references to achieve it. Thanks

Hello,

I have developed custom application for my Omega 2s+ board in the Go. For usb stuff I am using go-udev (https://github.com/pilebones/go-udev) library.
On the latest image it seems that, the udev is not present. I read couple of threads mentioning udev is not available for openwrt. I am missing the conclusion that, whether we can use udev on Omega boards or not. If yes, I would appriciate assistance in porting it. If No, what is the alternative.

TIA

@luz I got it from there only, Thanks.