Problem after firmware upgrade

[Prashant Kamdar]

@crispyoz

During the above boot I was able to "f + enter" to go into the failsafe mode.
From there, I ran the following commands:

firstboot -y
sync
reboot

But now, on the serial window, my Omega2+ is continously doing the following:

/ _ `/_
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 W H A T  W I L L  Y O U  I N V E N T ? /___/"

Board: Onion Omega2 APSoC DRAM:  128 MB
relocate_code Pointer at: 87f60000
flash manufacture id: c2, device id 20 19
find flash: MX25L25635E

[crispyoz]

@Prashant-Kamdar how are you powering your device? The error where it was rebooting when displaying the Warp Core logo makes me think that there is insufficient power.

[Prashant Kamdar]

@crispyoz I am powering the device using the FTDI's output of 3v3 which is connected to the PC.

I am able to get into the failsafe mode. What can I do now?

[crispyoz]

@Prashant-Kamdar I would use mount_root command, then once root is mounted, type service network disable

Then reboot

If you have the same issue then use firstboot -y again

[Prashant Kamdar]

@crispyoz that worked!

The Onion2+ just gave me a wifi AP and after connecting to it, it also showed up the new setup window on the http wizard!

Can you tell me what had happened and how did disabling the network solve it?

[crispyoz]

@Prashant-Kamdar I don't think you have sufficient power/current to power the device. When you started without the network enabled you avoid the spike in current draw which I think is what is causing your device to keep rebooting.

[Prashant Kamdar]

@crispyoz Understood

I don't know why, though since after following your steps, it works well even after a couple of reboots.

One last question, the firmware repo shows the latest firmware is omega2p-v0.3.3-b253.bin, but on the onion, it already shows I am on the latest (my firmware is higher than the latest?)

Is this ok?

[crispyoz]

@Prashant-Kamdar I think since you had just upgraded there were probably other things going on in the background that exacerbated the issue. WiFi scanning is a big hit on the system so temporarily avoiding it allowed things to complete. Trust me, your power supply is insufficient, it will rear its ugly head some time down the track.

Firmware 0.3.2 (b233) is the latest stable release, 0.3.3 (b251) is the latest release.

The upgrade function looks at https://api.onioniot.com/firmware/omega2p/stable

You can use your browser to check it and see the JSON response, then if you try https://api.onioniot.com/firmware/omega2p you will see the stable status of all the firmware versions.

[Prashant Kamdar]

@crispyoz thank you very much!

I agree with your point about insufficient power supply and will ensure to provide enough current for stable usage of op2+

[Prashant Kamdar]

@crispyoz sorry to bother again.
But I just realised that every time I reboot the omega2+, it resets the web console like it did earlier with 'firstboot'

Earlier when I said it was rebooting fine, it was... but I was only connected to the serial console and didn't realise that it was disconnected from my internet connection every time I rebooted.

What may be this issue?

[crispyoz]

@Prashant-Kamdar You need to reactive the network service:

service network enable

[Prashant Kamdar]

@crispyoz no dice
I did both enable and start and then connected to internet and rebooted, and still it came up like firstboot.
Next time it booted, I connected to internet and then enabled and started network and then reboot; still the same.

Did both the above a couple of times.

service network enable
service network start

[crispyoz]

@Prashant-Kamdar service network start is starting the network ok, correct? It's just not starting automatically when you boot?

[Prashant Kamdar]

@crispyoz this is correct

But hey, never mind this problem.
I reflashed the firmware and the problem went away

$ sysupgrade omega2p-v0.3.2-b218.bin

Thank you for your help!

[crispyoz]

@Prashant-Kamdar for future reference, the start file will be in /etc/rc.d the file is named S20Network the 'S' means it is called at startup, '20' is the order in which it starts, 'network' is the service name of course. There will also be a corresponding KxxNetwork which is the script called to shutdown the service.

A long time ago I had an issue where disabling and enabling a service did not always remove and then replace these files reliably. I never found out why, I just replaced the file and all was good. Never happened again.

[Prashant Kamdar]

@crispyoz this tracks!
I will add this in my (personal) wiki about the board