Omega Onion 2 pro SSID Issues after flashing custom image

Antony

I installed the Warp Core drivers using: ./scripts/feeds install wifi-warp-core, but it did not seem to resolve the issue.

I am customizing the image using the latest git repo: https://github.com/OnionIoT/source/tree/openwrt-18.06 and following the instructions provided in the README section.

After downloading this repository I am changing the rc.local file and adding two scripts to the root directory.

Thank you!

crispyoz

@Antony ./scripts/feeds install wifi-warp-core only makes the driver available when you run make menuconfig you still need to select warp core for it to be included in the build.

Antony

Thanks @crispyoz !

In the make menuconfig, I searched through all the folders for this and could not find wifi-warp-core. Does wifi-warp-core just extract all different kinds of wireless drivers for one to choose from, because I found many different versions of wireless drivers.

Thanks again!

crispyoz

@Antony you an always use / to search inside make menuconfig, the warp core option is inside Onion->WiFi

An easy way to reset your configuration is follow these steps:

rm .config
ln -s .config.O2 .config

This resets back to the standard Omega2 configuration.

Lazar Demin

You'll also need to make sure the Onion package repo is in your feeds.conf file.

See: https://github.com/OnionIoT/source/blob/openwrt-18.06/feeds.conf#L5

Antony

Thanks, I will try this.

I was able to serially connect to this created image and I see the following where there are no characters after the dash in Omega-.

Is this related?

Thank you!

Lazar Demin

@Antony We use a uci-defaults script to set the hostname based on the mac address
See it here: https://github.com/OnionIoT/source/blob/openwrt-18.06/files/etc/uci-defaults/13_hostname

Antony

Hi @Lazar-Demin

I am still running into the built omega2pro image failing to broadcast an SSID.

I am unable to ssh into the omega onion pro2 after flashing with built image so instead I connect serially.

Using PUTTY I typed wifi in the terminal prompt and its says the following:

radio0(ralink): Interface type not supported

Is this the reason why there is no SSID being broadcasted?

Thank you!

Lazar Demin

@Antony Judging by the radio0(ralink): Interface type not supported message and your previous posts in this thread, I'm guessing the wifi driver isn't installed.

You can check by running opkg list-installed | grep wifi on the device. If nothing shows up, then the wifi driver isn't installed.

If you can't find the wifi driver in the menuconfig, then there's probably something up with your build system.

Try doing Step 4 from the following link to update and set up your package feeds correctly: https://github.com/OnionIoT/source#option-a-using-the-docker-image

(Then consider setting up the the minimal build configuration to reduce your compile time: https://github.com/OnionIoT/source#reducing-compile-time-with-the-minimal-build-configuration)

Now try looking for wifi-warp-core in menuconfig

Antony

Hi @Lazar-Demin

In the make menuconfig, I have wifi-warp-core to be included in the build.

I ran opkg list-installed | grep wifi
on the device and it appears that the driver is in fact not installed. I tried the steps suggested and that didn't seem to fix the issue.

Lazar Demin

@Antony Does wifi-warp-core have a * or an M in the menuconfig in the build system? It should be a * so that it's included in the firmware.

Since opkg list-installed | grep wifi returns nothing, we know for a fact the driver is not included in the firmware you're building.

I would suggest:

Start with a fresh copy of the build system
Try to build firmware with no changes (just follow steps 1 and 2 from the readme in OnionIoT/source, and do the minimum build)
Confirm the firmware works as expected on the device (and includes the wifi driver)
Then carry out your firmware customizations in the build system and build your customized firmware
Test that your firmware works as expected on the device

Antony

Thank you @Lazar-Demin!!!!