Community

R H133

@Lazar-Demin - Also resolved on the GPIO issue. Using GPIO 23 and 26 allows the Omega to boot just fine even while connected.

R H133

Seems like I just had a similar issue - short cable did not work, longer cable did.

My suspicion is that my shorter cable (pulled from my box of cell phone cables) might just have the power wires hooked up and not have all the wires connected.

R H133

Looks like the Onion Wiki ( https://wiki.onion.io/Home ) is gone now, but Omega 1 docs are available here: https://onioniot.github.io/wiki/

R H133

Looks like the Onion Wiki ( https://wiki.onion.io/Home ) is gone now, but Omega 1 docs are available here: https://onioniot.github.io/wiki/

R H133

I have gone through the process. I even tried doing a full factory reset on the Onion Omega and reinstalled everything fresh. Same problem.

The software is a Ruby script calling the command-line to set / read GPIO pins. I'm in the process of re-writing it in Python, since there's better support in Python.

Let me know if you need more specific information or want me to try something.

R H133

I've been seeing crashes while using Ruby on the Omega. Since I'm using the "screen" utility from my Mac, I'm not able to capture all of the output. It happens consistently within a couple minutes of starting my Ruby script. What additional information can I provide to help debug this? Is anyone else seeing experiencing this instability?

Process memory map:

00400000-00401000 r-xp 00000000 1f:03 447 /usr/lib/ruby/ruby2.2-bin
00410000-00411000 rw-p 00000000 1f:03 447 /usr/lib/ruby/ruby2.2-bin
00972000-00ad9000 rwxp 00000000 00:00 0 [heap]
77ae1000-77b62000 rw-p 00000000 00:00 0
77b62000-77bb9000 r-xp 00000000 1f:02 2650 /lib/libuClibc-0.9.33.2.so
77bb9000-77bc8000 ---p 00000000 00:00 0
77bc8000-77bc9000 r--p 00056000 1f:02 2650 /lib/libuClibc-0.9.33.2.so
77bc9000-77bca000 rw-p 00057000 1f:02 2650 /lib/libuClibc-0.9.33.2.so
77bca000-77bcf000 rw-p 00000000 00:00 0
77bcf000-77be3000 r-xp 00000000 1f:02 2665 /lib/libgcc_s.so.1
77be3000-77bf2000 ---p 00000000 00:00 0
77bf2000-77bf3000 rw-p 00013000 1f:02 2665 /lib/libgcc_s.so.1
77bf3000-77c09000 r-xp 00000000 1f:02 2693 /lib/libm-0.9.33.2.so
77c09000-77c18000 ---p 00000000 00:00 0
77c18000-77c19000 rw-p 00015000 1f:02 2693 /lib/libm-0.9.33.2.so
77c19000-77c1c000 r-xp 00000000 1f:02 2668 /lib/libcrypt-0.9.33.2.so
77c1c000-77c2b000 ---p 00000000 00:00 0
77c2b000-77c2c000 rw-p 00002000 1f:02 2668 /lib/libcrypt-0.9.33.2.so
77c2c000-77c3d000 rw-p 00000000 00:00 0
77c3d000-77c40000 r-xp 00000000 1f:02 2664 /lib/libdl-0.9.33.2.so
77c40000-77c4f000 ---p 00000000 00:00 0
77c4f000-77c50000 r--p 00002000 1f:02 2664 /lib/libdl-0.9.33.2.so
77c50000-77c51000 rw-p 00003000 1f:02 2664 /lib/libdl-0.9.33.2.so
77c51000-77cba000 r-xp 00000000 1f:03 439 /usr/lib/libgmp.so.10.2.0
77cba000-77cca000 ---p 00000000 00:00 0
77cca000-77ccb000 rw-p 00069000 1f:03 439 /usr/lib/libgmp.so.10.2.0
77ccb000-77cde000 r-xp 00000000 1f:02 2689 /lib/libpthread-0.9.33.2.so
77cde000-77ced000 ---p 00000000 00:00 0
77ced000-77cee000 r--p 00012000 1f:02 2689 /lib/libpthread-0.9.33.2.so
77cee000-77cef000 rw-p 00013000 1f:02 2689 /lib/libpthread-0.9.33.2.so
77cef000-77cf1000 rw-p 00000000 00:00 0
77cf1000-77e9b000 r-xp 00000000 1f:03 434 /usr/lib/libruby.so.2.2.0
77e9b000-77eab000 ---p 00000000 00:00 0
77eab000-77eb0000 rw-p 001aa000 1f:03 434 /usr/lib/libruby.so.2.2.0
77eb0000-77eb6000 rw-p 00000000 00:00 0
77eb6000-77ebd000 r-xp 00000000 1f:02 2649 /lib/ld-uClibc-0.9.33.2.so
77ec7000-77ec8000 ---p 00000000 00:00 0
77ec8000-77ecc000 rw-p 00000000 00:00 0 [stack:3322]
77ecc000-77ecd000 r--p 00006000 1f:02 2649 /lib/ld-uClibc-0.9.33.2.so
77ecd000-77ece000 rw-p 00007000 1f:02 2649 /lib/ld-uClibc-0.9.33.2.so
77ece000-77ecf000 rw-p 00000000 00:00 0
7f1b8000-7f9b7000 rw-p 00000000 00:00 0
7fff7000-7fff8000 r-xp 00000000 00:00 0 [vdso]

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

Aborted

R H133

@Lazar-Demin - Also resolved on the GPIO issue. Using GPIO 23 and 26 allows the Omega to boot just fine even while connected.

R H133

Lazar - Thanks for the quick reply.

Filesystem - I did a factory reset and I do not see the issue any more. I'll watch it for a bit to see if it pops up again.

GPIOs - I see the same behavior as the post you referenced, only I'm using GPIO 14 and 23. If they're connected to the Expansion Dock when I plug in the USB (to power it all), the amber light on the Omega will remain dark and not light up. If I disconnect them, the Omega still does not appear to boot. If I unplug the USB and the wires, I can plug the USB back in and boot the Omega without issue.

The side circuit is for a Hall Effect sensor. I'm using the +5v / GND pins from the Expansion dock to power this side circuit.

I also have the Omega hooked up to a Sunfounder 4-relay module, connected to GPIOs 6 and 7, and to the +5v / GND pins. This circuit does not prevent the Omega from booting.

R H133

While working on a short ruby script the other night, I noticed the following message:
ls -l
[ 160.430000] jffs2: warning: (2158) jffs2_do_read_inode_internal: Truncating ino #167 to 1928 bytes failed because it only had 1906 bytes to start with!

Possibly related:

started using Samba server to copy script files to backup
attempted to set Samba to allow write-mode, but was unsuccessful
discovered that the Omega does not boot while hooked up to a small Hall Effect sensor more info here

oupgrade --check

Device Firmware Version: 0.1.4 b330
Checking latest version online...
Repo Firmware Version: 0.1.4 b330
Comparing version numbers
Device firmware is up to date!

opkg update
Package liboniondebug version 0.4-1 has no valid architecture, ignoring.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_base.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/base/Packages.sig.
Signature check passed.
Downloading http://repo.onion.io/omega/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_onion.
Downloading http://repo.onion.io/omega/packages/Packages.sig.
Signature check passed.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_packages.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/packages/Packages.sig.
Signature check passed.
Collected errors:

pkg_state_status_from_str: Internal error: state_status=instaure:
parse_from_stream_nomalloc: Missing new line character at end of file!

On Boot, I'm seeing a few of these messages:

[ 30.940000] jffs2: notice: (340) check_node_data: wrong data CRC in data node at 0x004991a4: read 0x37eea6d, calculated 0xa7519f7c.
[ 31.060000] jffs2: notice: (340) check_node_data: wrong data CRC in data node at 0x00498dfc: read 0xc2ad57a, calculated 0x30f7c754.

R H133

Andrei - I don't know if this helps, but your comments were so helpful I wanted to mention this. I've had ruby installed and didn't see a lot of additional dependencies. I just now installed ruby-irb and saw that opkg installed a whole bunch of ruby-related stuff.

R H133

Seems like I just had a similar issue - short cable did not work, longer cable did.

My suspicion is that my shorter cable (pulled from my box of cell phone cables) might just have the power wires hooked up and not have all the wires connected.

R H133

@R H133

Best posts made by R H133

Latest posts made by R H133