@SimonPR Digikey just pushed back my back order for some other components yet again, as well. If both Apple and Samsung have to push back on product releases due to chip shortages, you and I are way back in the queue.

I have 40 Omega2S+ on my shelf but I can't launch a new product until I have a few hundred more, so I'm thinking I could put them up for auction

@Nagarjuna-Reddy Thank you, I live in Sydney Australia so we are pretty safe here these days.

Can you give us the details of what process you are following to perform your testing, I think this is pretty much the same question I always have to ask you. It is easier to help when we have all the information in the beginning, instead of having to ask for it.

#!/bin/sh

while getopts "d:p:" opt;
do
case "${opt}" in
d) device=${OPTARG};;
p) pass=${OPTARG};;
esac
done

if [ -z "$device" ]
then
echo "Ethernet device not set, use parameter -d <device>"
exit 1;
fi

address=$(ping6 -c 1 -i 4 -I $device ff02::1 | grep "64 bytes from " | awk '{print $4}' | cut -d"%" -f1 | awk -F':' '{print $0}')

if [ -z "$address" ]
then
echo "IP v6 address not set, use parameter -a <address>"
exit 1;
fi

if [ -z "$pass" ]
then
echo "Password not set, use parameter -p <password>"
exit 1;
fi

ssh-keygen -f "~/.ssh/known_hosts" -R "$address%$device"

echo "Sending Firmware to device...\n"
sshpass -p$pass scp -6 -o StrictHostKeyChecking=no ~/source/bin/targets/ramips/mt76x8/openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin root@[$address%$device]:/tmp

echo "Executing firmware update...\n"
sshpass -p$pass ssh -6 -o StrictHostKeyChecking=no root@$address%$device sysupgrade -n /tmp/openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin

@haythem search the forum for MCO23017 this is a topic that has been discussed for several years so I am sure you can find something to asist you.

@optech Congratulations.
This was my original advice, because the other methods are really workarounds/hacks/shortcuts. In my experience shortcuts rarely are that.

@optech if you look at the code it doesn't log much at all, regardless of the debug settings.

clean does remove the symlink. This is basically a hack so it's always going to be a pain. This is why my original suggestion was to fork the source and set up your own package so you have control of the code.

@optech I should mention that if all you want to do is turn on the debug options you can just tweak the patch file because this overrides the library.cfg settings. To do this just edit package/feeds/packages/net/lora-gateway-hal/patches/0001-add-cmake-support.patch

Line 126 has the debug options you are looking for, just change the OFF to ON for the required options, then clean and make build again and you'll see the debug options you set are turned on.

SPI_DEV_PATH is set in package/feeds/packages/net/lora-gateway-hal/patches/0002-add-preprocessing-for-SPI_DEV_PATH-and-SPI_SPEED.patch

@optech try this:

make menuconfig
Check "Enable package source tree override" in the "Advanced configuration options (for developers)" menu
exit and save

make package/feeds/packages/lora-gateway-hal/clean V=s
make package/feeds/packages/lora-gateway-hal/prepare USE_SOURCE_DIR=~/lora_gateway-5.0.1 V=s
make package/feeds/packages/lora-gateway-hal/compile V=s

Does Onion have an updated lead time on the Omega2 devices? The latest advice I have seen is "April Timeframe", since it's now May it'd be helpful if we could get an update to assist with planning.

@optech Are you using OpenWrt 18 or 19, your initial message states you are using 18.06 but the directory you refer to is 19. I'll try to duplicate your issue but I want to be sure I am using the correct source pool.

@optech For me the easiest solution is to fork the package then add the forked package to the feeds. Since you're going to have to release the source to your package anyway, you may as well set up the repository.

I personally prefer to use NetBeans for my coding so working with the repository is seamless.

@optech small victories lead to larger ones.

@optech Congratulations. I used this about 2 years ago to get my leds functional but then ended up using LedChain by @luz as my purpose was slightly different.

Did they have leds 15 years ago? I'm a bit young to know

I'm using MCP2200T with 12Mhz oscillator on my custom boards never had any issues.

@optech take a look at the wiki on this topic:

https://oldwiki.archive.openwrt.org/doc/uci/system#wifi_activity

If you are using a custom board with an additional LED, you may need to update the DTS to support this.

@optech that's interesting, I've never needed to make any modification to the boot loader in order to get reliable console access. My guess is you have a hardware issue.

@optech The files in this directory are typically created by a kernel module that's managing those resources.

@optech I have over 500 Omega2 devices deployed and I'm probably ranked >500+ customer of the devices so let's look at the potential causes of your issue. Here is my top 3 things to check:

Baud rate should be 115,200
Ensure your power supply is compliant to the required spec (Number 1 cause of irratic issues)
Please post your putty configuration settings
Use a decent USB cable.

@RandomPerson I still suspect this is power related, a lot of wierd stuff happens when there is insufficient current. When the wifi system starts there is a spike in current draw.

@RandomPerson That's interesting, the boot logging shows the delay before the driver is loaded. I tried commenting out my wifi config and the boot time is no different.