Community

Arek Z

Hi guys,

I have some communication problems with my omega. Here is a situation: I use one omega to communicate with another omega. UART1 of first one is connected to UART0 of another one. When I look on the serial output during boot, this is what I see:

  ____       _             ____
  / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
 / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 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
f�X.
    j�n]Vk��rY�-���,��YWk� Z����r
                                 CVˑ ��X.K]�5T��2Y
                                                  �*��HUK�i��   �d�(�   ��i����a]��e��Z�˵e���H��=�O���=O��K�j��-K�j��Z-K�j��-K�j��Z-K�j��Z-K�j�� �C��j���8�A ��K�5�Kr�nY%��%5 ���o�Y�� L&&�J�t.J�ݥd��HL��D%
                                                                                                 5 �].��@bZ��D��a��[V��y��L&5     y�Y.�dŅs�����o�Y�� *U
                                             2�a.K�D
                                                    �e�j� L'$S��Q�mY�ӓ���`5�C���z=O���z=O���=O���z=O���z=OZ���� ��:M&&    ��y.����i�Y.�3��K]��l��MӲ)5d���� ��:�M  ��y.����i�Y.�3��K]��l�&ӓ)�U$��q�O�Ӫ�5�Z�C��i[,W�
                                                                                                        ԕ�o�^��K� O�&5�y�Y.�$U�e��Z�M���ၠHVI��I�ZW+�i�Z�M���၎PR
                                                     ��s�Y�R5)
                                                              C%IR��*��%IR��T*��J%IR��T*��J%IR��T
                                                                                                 C%�d��Y��b]�n��K�mK� 
            �i�� ��C%IR��T*��J%IR��*��%IR��T*��J%IR��T
                                                      C�HԤj�o��SZ�� ����F�X.
                                                                            r= �Q��IE�U�I�4�    �o�Z�i[�V
                                                 
�f1�S��2��LK�-��x��Zk�r��H\,���P1��LM&&�        �mJ�.W��s�K&SH���`.�S��� ��LN&� �n[�pZk�r��H���d����rY�Wk� �Z
   ��Pi+¥��r��g��� �W
                     ��� �YWk� ��LN&�   �n[5
                                            +           r��8M��j�kK�W
                                                                     ���`5��L   �m��Q.�K��p��^-�sY�n    ��vY�W��i�ցbX����[��HH&I���e4W����a��HN�z��j5��Y�˕r��MH�K�s��R��
                                                              +�i��+5�b�YVH�[��HH&i���9�W����o�Y�+�S�W$Vk�b�YVH���`.&�S��u@1��LL,���r��ZWK��y*R��MS�
                                          ���0��L,      )�q�O$&b���sY%�u��O$����a)�Z.R)���`AC�[    0.315704] console [ttyS0] enabled
[    0.315704] console [ttyS0] enabled
[    0.322701] bootconsole [early0] disabled
[    0.322701] bootconsole [early0] disabled
[    0.331373] 10000d00.uart1: ttyS1 at MMIO 0x10000d00 (irq = 29, base_baud = 2500000) is a 16550A
[    0.340872] 10000e00.uart2: ttyS2 at MMIO 0x10000e00 (irq = 30, base_baud = 2500000) is a 16550A
[    0.351461] spi-mt7621 10000b00.spi: sys_freq: 193333333
[    0.361493] m25p80 spi32766.0: using chunked io (size=31)
[    0.366990] m25p80 spi32766.0: w25q256 (32768 Kbytes)
[    0.372207] 4 ofpart partitions found on MTD device spi32766.0

At the beginning, everything is ok. When Omega switches to 87f60000, I see garbage. After that, when bootloader finishes its job and passes control to the kernel, I see normal output again.

My best bet is missing terminfo definitions. This is what is present on the system:

# ls -R /usr/share/terminfo/
/usr/share/terminfo/:
a  d  l  r  s  v  x

/usr/share/terminfo/a:
ansi

/usr/share/terminfo/d:
dumb

/usr/share/terminfo/l:
linux

/usr/share/terminfo/r:
rxvt          rxvt-unicode

/usr/share/terminfo/s:
screen

/usr/share/terminfo/v:
vt100  vt102

/usr/share/terminfo/x:
xterm           xterm-256color  xterm-color

However, I have no idea what terminal definition should I use to read correct output from the Omega's bootloader. Can you help?

Arek Z

@Caio-Mehlem

It is binary kernel module:
https://github.com/OnionIoT/OpenWRT-Packages/tree/master/wifi-warp-core/bin

Based on this, Wifi seems to work on the custom build. I haven't checked, however.

@Stephane-Foloppe said in Wifi not working after building customized image:

hi,

I just build my own firmware and wifi is working !

( I just have to manually select Coreutils to make the wifi drivers appears in onion/wifi )

Arek Z

Forget totally about compiling it on the omega. You have to cross compile it using this repo: https://github.com/OnionIoT/source.

Arek Z

I am using this makefile for node v8.9.4 without any additional patches.

include $(TOPDIR)/rules.mk

PKG_NAME:=nodejs
PKG_VERSION:=v8.9.4
PKG_RELEASE:=1

PKG_SOURCE:=node-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://nodejs.org/dist/${PKG_VERSION}/

PKG_BUILD_DIR:=$(BUILD_DIR)/node-$(PKG_VERSION)
PKG_BUILD_PARALLEL:=1
PKG_BUILD_DEPENDS:=
PKG_USE_MIPS16:=0

include $(INCLUDE_DIR)/package.mk

define Package/nodejs
  DEPENDS:=+libpthread +librt +libstdcpp +libopenssl +zlib
  SUBMENU:=Node.js
  SECTION:=lang
  CATEGORY:=Languages
  TITLE:=Node.js v8.9.4
  URL:=https://nodejs.org/
endef

define Package/nodejs/description
Event-driven I/O server-side JavaScript environment based on V8
endef

define Package/npm
  DEPENDS:=+nodejs
  SUBMENU:=Node.js
  SECTION:=lang
  CATEGORY:=Languages
  TITLE:=Node.js Package Manager
  URL:=https://npmjs.org/
endef

DEST_CPU=$(ARCH)



CONFIGURE_ARGS = --dest-cpu=$(DEST_CPU) --dest-os=linux \
  --shared-openssl --shared-openssl-includes="$(STAGING_DIR)/usr/include" --shared-openssl-libpath="$(STAGING_DIR)/usr/lib" \
  --shared-zlib --shared-zlib-includes="$(STAGING_DIR)/usr/include" --shared-zlib-libpath="$(STAGING_DIR)/usr/lib" \
  --with-intl=none \
  --v8-options="--max_old_space_size=30 --initial_old_space_size=4" --without-snapshot


CONFIGURE_ARGS += \
--with-mips-arch-variant=r2 --with-mips-fpu-mode=fp32 --with-mips-float-abi=soft


define Package/nodejs/install
	mkdir -p $(1)/usr/bin
	$(INSTALL_BIN) $(PKG_BUILD_DIR)/out/Release/node $(1)/usr/bin/node
endef

define Package/npm/install
	mkdir -p $(1)/usr/lib/node_modules
	$(CP) $(PKG_BUILD_DIR)/deps/npm $(1)/usr/lib/node_modules
	mkdir -p $(1)/usr/bin
	ln -sf /usr/lib/node_modules/npm/bin/npm-cli.js $(1)/usr/bin/npm
endef

$(eval $(call BuildPackage,nodejs))
$(eval $(call BuildPackage,npm))

However, node v8 uses builtin inspector for debugging purposes. That inspector depends on icu module and the icu is quite big - full is 22,5 MB, small ~8MB (as far as I can remember). I wasn't able to compile node with small-icu and full-icu is too big for the omega. I end up using node without debugging features temporarily.

Reference to NodeJS configure script:
https://github.com/nodejs/node/blob/master/configure#L1406

  disable_inspector = (options.without_inspector or
                       options.with_intl in (None, 'none') or
                       options.without_ssl)
  o['variables']['v8_enable_inspector'] = 0 if disable_inspector else 1

Arek Z

They are indeed very close (15h ago):
https://github.com/OnionIoT/OpenWRT-Packages/commit/1b4280a7b51bc835de22288edd142dfaf7084c2c

@EDIT
Actually, they are done with it:

@Maximilian-Gerhardt said in Omega2 current defects:

OnionIoT has released a new firmware version b176 in https://onion.io/2bt-march-27-2018/ in which it is stated that:

a new WiFi driver "WiFi Warp Core" has been released, which fixes problems with:

general WiFi performance

Automatic Network Switching

Automatic Network Encryption Detection in wifisetup

Support for Hidden SSIDs

SPI Improvements

maximum transfer sizes increased to 4096 bytes

MSB corruption fixed for "some" devices ("We’ve observed that some SPI devices still show data corruption but others do not")

new python-spidev package for writing user-space programs with SPI (apparently different from old pyOnionSpi)

Will re-test and recompile older programs to see how much it improved. Main post updated.

Arek Z

Openzwave is actually available in the newer LEDE release. Onion uses 17.01, which does not have the package.
However, looking at the Makefile, it seems that it can be easily backported.

Here is the link to the package definition: https://github.com/openwrt/packages/blob/master/utils/openzwave/Makefile

Arek Z

Even though you may have glib, udev, d-bus on the omega, for sure you do not have headers (*.h) for these on the omega. On the bigger linux devices, you always have extra packages available for these headers, for example build-essentials or libbluetooth-dev on the debian. You need to cross compile using LEDE or install headers locally on the Omega.

Arek Z

@cas If you look at https://github.com/OnionIoT/source, you can read in the description:

"Due to incompatibilities with recent kernel updates, building a firmware with the Ralink APSoC WiFi SoftAP driver will cause a kernel panic during boot".

The official firmware runs on 4.4.46 and I bet that reason for that is WiFi kernel module. You can try to go back with LEDE to 4.4.46 or try to use open source driver (mt76?). I'd rather recommend going with closed source driver (open source driver seems to be buggy). To be precise, you can take a look on commits to kernel-version.mk (https://github.com/OnionIoT/source/commits/lede-17.01/include/kernel-version.mk). The 4.4.46 was introduced with b786a5ffc39539d55cf74ebd43edde9051b4682d (https://github.com/OnionIoT/source/commit/b786a5ffc39539d55cf74ebd43edde9051b4682d#diff-9e2e0c0e43d2d4ab7bf91e5fdd11cf2a). However, I didn't build this kernel yet so I am not sure if you will face other problems.

Arek Z

@Pavel-Metrokhin Thank you Pavel, we know this. However, web recovery is not available when u-boot is damaged. User wdu confirmed that it is possible to flash with SPI when you are unable to use web recovery.

Summary:

If you have working u-boot - use web recovery https://docs.onion.io/omega2-docs/Firmware-Flashing-Web-Recovery.html
If you damaged u-boot - You do not have to unsolder memory for flashing with external hardware. You are able to flash the bootloader with SPI (not a trivial thing, however). To be able to flash the memory, you need to keep Omega's processor in reset state.

Arek Z

@wdu Awesome, thank you so much. This is the confirmation I needed!

Arek Z

@Arek Z

Best posts made by Arek Z

Latest posts made by Arek Z