@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