Hi @Lazar-Demin & @crispyoz, I was able to find the root cause for this issue. I've created a pull request in OnionIoT/source github repository with the fix.

@crispyoz my bad, I should have been more specific.

After issuing the reset pulse, the device becomes 'unresponsive', meaning that it can't be accessed via SSH, it does not respond to ping commands, and if I'm connected over serial, I don't even see the echo to the input characters.

If I power-cycle the device, meaning I power it off and on, it boots normally. It is NOT necessary to run through any recovery process (e.g. u-boot, web recovery, etc).

Thank you for your assistance.

Hi @crispyoz! Thanks for taking care.

I understand that factory reset via the reset button interacts with 'SW_RST' line (aka GPIO38 - pin 4) from Onion Omega. The issue I described is observed when generating a reset pulse on 'HW_RST_N' line (pin 5).

The SW reset works fine, both as a 'normal' reboot or a factory reset. I repeted the test after performing a factory reset and the unit got bricked too when the reset pulse was generated on HW_RST_N line.

Best regards,
Matias

Hi all, I'm experiencing an issue with Hardware Reset on my Onion Omega2 Pro after updating to OpenWrt v23.05.3 based image.

With v0.3.4 (and earlier) images, I sent a reset pulse on CPU_RST line (pin 27 from J2 header) and the device was reset. However, after installing the latest image (onion_omega2p-23.05.3-20250709.bin), the behavior has changed. After sending the same reset pulse (500 ms width), the device gets bricked and becomes unresponsive. The only way to recover it is through a power-cycle.

I wonder if anybody else has observed the same issue and if there is any workaround for it.

Thanks!
Matias

Hi @Lazar-Demin & @crispyoz, I was able to find the root cause for this issue. I've created a pull request in OnionIoT/source github repository with the fix.

@crispyoz thanks for the update. You're correct. The make command does not return an error. However, after it finishes running openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin is generated but not openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin.
When looking into the make command output, the messages shown below are the only reference to the Omega2Pro image.

WARNING: Image file /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin is too big
cp /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin /home/user/onion/source/bin/targets/ramips/mt76x8/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin
cp: cannot stat '/home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin': No such file or directory

Please let me know if you have any new finding.

Thanks in advance,
Matias

@crispyoz good to know that it worked for you.

I've checked the source/target/linux/ramips/dts/OMEGA2PRO.dts and it includes the latest modification pushed by @Lazar-Demin to the source repo.

/dts-v1/;

#include "OMEGA2.dtsi"

/ {
        model = "Onion Omega2 Pro";

        memory@0 {
                device_type = "memory";
                reg = <0x0 0x8000000>;
        };

        new-leds {
                compatible = "gpio-leds";

                wifi {
                        label = "omega2pro:blue:wifi";
                        gpios = <&gpio1 12 GPIO_ACTIVE_LOW>;
                };
        };
};

&firmware {
        reg = <0x50000 0x1f30000>;
};

&system_led {
        label = "omega2pro:amber:system";
        gpios = <&gpio1 11 GPIO_ACTIVE_LOW>;
};

&pinctrl {
        state_default: pinctrl0 {
                uart2 {
                        ralink,group = "uart2";
                        ralink,function = "gpio";
                };
        };
};

BTW, I'm sharing with you the content from source/bin/targets/ramips/mt76x8 directory. Does the Omega2+ image build has the same size than the one you built?

user@ML-PC:~/onion/source/bin/targets/ramips/mt76x8$ ls -lh
total 58M
 -rw-r--r-- 1 user user  12K Feb 22 10:45 config.seed
 -rw-r--r-- 1 user user  18M Feb 22 11:17 openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin
 -rw-r--r-- 1 user user 7.3K Feb 22 11:17 openwrt-ramips-mt76x8.manifest
 -rw-r--r-- 1 user user  41M Feb 22 11:15 openwrt-toolchain-ramips-mt76x8_gcc-7.3.0_musl.Linux-x86_64.tar.bz2
 drwxr-xr-x 1 user user  512 Feb 22 11:18 packages
 -rw-r--r-- 1 user user  429 Feb 22 11:18 sha256sums

Thanks for the support being provided.

Best regards,
Matias

@crispyoz please find the CustomConfig in the following link. https://paste.mozilla.org/qrMwjsZR

Best regards,
Matias

Hi @crispyoz, I'm including below the steps followed to setup the build system and compile it. I started from scratch to make sure that the changes pushed by @Lazar-Demin were included in the build system.

Note: I'm using a Linux System and not the Docker image.

• create an onion folder, navigate into it and download the build system from github.

  mkdir onion
  cd onion
  git clone https://github.com/OnionIoT/source.git -b openwrt-18.06
  cd source
  

• setup the onion feeds.

  sh scripts/onion-feed-setup.sh
  python scripts/onion-setup-build.py
  

• update the image configuration. If I manually chose the packages and target (among other options), I run make menuconfig. However, I usually use an already generated .config file, which has a diff format.

  cp CustomConfig /home/user/onion/source/.config
  cd /home/user/onion/source
  make defconfig
  

• finally, the image is built by running make -j4. If any error is raised, I re run the command with the following syntax to get more information about the error: make -j1 V=s

These bullets summarize the steps followed to build the image. Let me know if there is any way I can share with you the config file.

BTW, when selecting both the Omega2 Pro and the Omega2+ as the Target Devices, binary for Omega2+ is generated but not for the Omega2 Pro. As for the Omega2+, the binary size is 18 MB, and as for the Omega2 Pro, I get the warning message that the image is too big.

Best regards,
Matias

Hi @Lazar-Demin, I've cloned the repo to start from scratch and make sure the latest commit was being used from https://github.com/OnionIoT/source (and also for the new DTS to take effect).
I'm still observing the same issue. Please let me know if there is any extra infromation I can provide you. I'm including below the output for the make command, where the error is raised.

Image Name:   MIPS OpenWrt Linux-4.14.81
Created:      Thu Feb 15 20:37:21 2024
Image Type:   MIPS Linux Kernel Image (lzma compressed)
Data Size:    1617556 Bytes = 1579.64 KiB = 1.54 MiB
Load Address: 80000000
Entry Point:  80000000
mv /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/omega2pro-kernel.bin.new /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/omega2pro-kernel.bin
[ -f /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/omega2pro-kernel.bin -a -f /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/root.squashfs ]
dd if=/home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/omega2pro-kernel.bin >> /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin
3159+1 records in
3159+1 records out
1617620 bytes (1.6 MB, 1.5 MiB) copied, 0.0263151 s, 61.5 MB/s
dd if=/home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/root.squashfs >> /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin
31685+1 records in
31685+1 records out
16222728 bytes (16 MB, 15 MiB) copied, 0.25631 s, 63.3 MB/s
/home/user/onion/source/staging_dir/host/bin/padjffs2 /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin  4 8 16 64 128 256
padding image to 01104000
padding image to 01110000
padding image to 01120000
padding image to 01140000
echo '{  "supported_devices":["omega2pro"], "version": { "dist": "OpenWrt", "version": "18.06.1", "revision": "r7501-928cad900f", "board": "ramips" } }' | fwtool -I - /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin
WARNING: Image file /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin is too big
cp /home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin /home/user/onion/source/bin/targets/ramips/mt76x8/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin
cp: cannot stat '/home/user/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin': No such file or directory

Best regards,
Matias

Awesome, thank you @Lazar-Demin! I'll be waiting for your updated status so I can give it a try.

Best regards,
Matias