Omega2 boot loop
-
Device Firmware Version: 0.1.9 b150
it's all that I could copy
[ 0.501075] mt7621_wdt 10000120.watchdog: Initialized
[ 0.507722] NET: Registered protocol family 10
[ 0.516240] NET: Registered protocol family 17
[ 0.520913alive
[ 1.576696] init: - watchdog -
complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
vents driver (C) Jiri Kosina
[ 10.719893] Bluetooth: Core ver 2.21
[ 10.723627] NET: Registered protocol family 31
[ 10.728132] Bluetooth: HCI device and connection manager initialized
[ 10.734629] Bluetooth: HCI socket layer initialized
[ 10.739588] Bluetooth: L2CAP socket layer initialized
[ 10.744738] Bluetooth: SCO socket layer initialized
[ 10.753817] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.759270] Bluetooth: BNEP filters: protocol multicast
[ 10.764579] Bluetooth: BNEP socket layer initialized
[ 10.776223] usbcore: registered new interface driver btusb
[ 10.785737] usbcore: registered new interface driver cdc_acm
[ 10.791564] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 10.803391] Bluetooth: HCI UART driver ver 2.3
[ 10.807913] Bluetooth: HCI UART protocol H4 registered
[ 10.813185] Bluetooth: HCI UART protocol BCSP registered
[ 10.822711] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 10.828809] Bluetooth: HIDP socket layer initialized
[ 10.836880] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 10.858101] nf_conntrack version 0.5.0 (949 buckets, 3796 max)
[ 10.887779] Bluetooth: RFCOMM TTY layer initialized
[ 10.892823] Bluetooth: RFCOMM socket layer initialized
[ 10.898058] Bluetooth: RFCOMM ver 1.11
[ 10.909720] spidev spi32766.1: buggy DT: spidev listed directly in DT
[ 10.916266] ------------[ cut here ]------------
[ 10.921035] WARNING: CPU: 0 PID: 475 at drivers/spi/spidev.c:720 init_module+0xf33c/0xfdec spidev
[ 10.930390] Modules linked in: spidev(+) snd_usbmidi_lib slhc rfcomm nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hidp hid_generic hci_uart crc_ccitt cdc_acm btusb btintel bnep bluetooth snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 videobuf2_vmalloc videobuf2_memops videobuf2_core hid v4l2_common videodev evdev snd_soc_core ralink_gdma virt_dma mt76x8 ralintrig_morse ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables msdos snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat ntfs configfs autofs4 nls_utf8 nls_iso8859_1 nls_cp437 regmap_i2c dma_shared_buffer ecb cmac mmc_block usb_storage sdleds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache exfat usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 11.037276] CPU: 0 PID: 475 Comm: kmodloader Not tainted 4.4.42 #0
[ 11.043553] Stack : 803680f4 00000000 00000001 803b0000 83920284 803b0d83 80349a58 000001db
80403438 0000000b 0000001a 024000c0 800661d4 8004adf4 8034ef54 803b0000
00000003 0000000b 8034d358 83177b4c 800661d4 80048d60 00000000 00000000
00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
[ 11.079714] Call Trace:
[ 11.082252] [<800661d4>] module_sect_show+0x0/0x18
[ 11.087119] [<8004adf4>] vprintk_default+0x24/0x30
[ 11.092008] [<800661d4>] module_sect_show+0x0/0x18
[ 11.096869] [<80048d60>] printcf2c>] spi_match_device+0x38/0xa8
[ 11.165382] [<801b8afc>] __driver_attach+0x7c/0xb4
[ 11do_one_initcall+0x1e8/0x214
[ up+0x24/0x48
[ 11.245886] [<833ef000>] init_module+0x0/0xdc [spidev]
[ 11.251133] [<80034404>] call_usermodehelper_exec+0xdaWhat i can do to run this device?
I can run failsafe mode but there i had error "Failed to connect to ubus"
-
This post is deleted!
-
After message
[ 18.768343] EEPROM:Read from [factory] offset 0x0,length 0x400.go reboot
-
@Andrey-Shafray said in Omega2 boot loop:
After message
[ 18.768343] EEPROM:Read from [factory] offset 0x0,length 0x400.go reboot
Power to the Omega 2 is probably inadequate. The next boot message after "EEPROM: . . ." is when the wifi turns on and there is a surge in current draw. Instead the processor has rebooted before that message can be output.
-
I use lm1117 3.3v to power omega.
-
@Andrey-Shafray Do you have input and output caps? The lm1117 specsheet does recommend you to have a 10uF cap on the input and 100uF cap on the output, if my memory serves.
-
@WereCatf Yes i have 10u input and 100u output
-
What is the source of power to the LM1117? I'd recommend something with 1 Amp or greater rating to eliminate that as a potential issue, though 0.5 Amps is probably enough.
It's also important that the wiring from the regulator to the Onion be short to minimize induction and of sufficiently heavy gauge wire to minimize resistance loses.
Tantalum capacitors have better high frequency performance than other electrolytic capacitors so they are preferred on the LM1117 output.
My working breadboard configuration is a USB power supply (nominally 5 volts) to an LM1117 essentially on the connector to the Onion with a 22 uF tantalum bypass capacitor on the LM1117 output. I've successfully run with a 0.7 Amp USB wall wart but tested initially with a 2.0 Amp unit.
-
now my omega is dead. It doesn't blink and response over uart. it produces peep and heats up(it use 0.24 amp)
-
.24 amps (240 mA) is well within the range of power consumption for common operational phases, especially when the time averaging of your measurement is unstated.
-
@Chris-Stratton
I not understand. My omega is not dead?
-
@Andrey-Shafray said in Omega2 boot loop:
@Chris-Stratton
I not understand. My omega is not dead?All that can be said is that your current measurement does not by itself indicate much.
If you could log instantaneous current over time and compare to the startup of a functioning board it might be possible to learn something. And that other person who measured more than an amp had in their measurement a clear indication of a problem, but your measurement is not outside the expected range, at least until its trend over time is considered in detail.
Note that it is not out of the question that connection of an unspecified ammeter inline could prevent the system from properly functioning.
