Henrik Larsson

Where can I read more about "power management support for the entire Allwinner family"?

I have gotten Oops a few times, now this morning I got it again I can see that is says "Segmentation Fault". I could still issue sudo armbianmonitor -u so I included those logs. Since I was also connected to both via SSH, where I was running "armbianmonitor -m" and logged in via serial I include the output of those windows below: SSH output: ... Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 00:56:54: --- 0.00 0% 0% 0% 0% 0% 0% 40.1°C 0/15 00:57:00: --- 0.08 1% 1% 0% 0% 0% 0% 40.1°C 0/15 00:57:05: --- 0.07 1% 0% 0% 0% 0% 0% 40.1°C 0/15 00:57:10: --- 0.06 1% 1% 0% 0% 0% 0% Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5328.561638] Internal error: Oops: 5 [#1] SMP THUMB2 Segmentation fault Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.810048] Process armbianmonitor (pid: 1569, stack limit = 0x74377ca1) chip@nanopiair:~$ Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.890232] Stack: (0xca84beb0 to 0xca84c000) Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.942338] bea0: c0efb38c ca853a80 c0e24f14 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.040202] bec0: d63a7280 00000000 00000000 00000000 00000000 c0efb784 ca853d94 ffffe000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.138066] bee0: d069cfa0 ce638788 c0a1363c c0e04d48 000a0001 ce638600 ce638780 c0124d8f Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.235930] bf00: ffffe000 c0124d8f ca850430 00000000 00000000 00000000 ca84f334 039bb874 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.333794] bf20: 00000004 01200011 00000000 c0e04d48 00000000 00000000 ca84a000 00000078 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.431658] bf40: 00000000 c011a5e1 00000000 00000000 ffffffff 00000051 ca84bf7c be8d82c4 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.529523] bf60: 00000000 be8d82c4 00000008 039bb874 c0e04d48 b6ffd238 b6ffd690 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.627385] bf80: 00000078 c0101224 ca84a000 00000078 00000000 c011a921 b6ffd238 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.725251] bfa0: b6ffd238 c0101001 b6ffd238 b6ffd690 01200011 00000000 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.823114] bfc0: b6ffd238 b6ffd690 00000000 00000078 be8d82c4 00000000 b6ffd1d0 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.920978] bfe0: 00000078 be8d8208 b6f11253 b6eb3746 200f0030 01200011 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5331.018852] Code: 0f04 9800 bf08 b081 (e88d) 1ffe On the serial console: chip@nanopiair:~$ [ 5328.389678] Unable to handle kernel NULL pointer dereference at virtual address 00000004 [ 5328.486540] pgd = 363f637e [ 5328.518886] [00000004] *pgd=00000000 [ 5328.561638] Internal error: Oops: 5 [#1] SMP THUMB2 [ 5328.619983] Modules linked in: zstd lima gpu_sched sun8i_codec_analog sun4i_i2s snd_soc_simple_card sun8i_adda_pr_regmap ttm snd_soc_simple_card_utils snd_soc_core snd_pcm_dmaengine snd_pcm sun4i_gpadc_iio snd_timer industrialio snd soundcore sun8i_ths cpufreq_dt thermal_sys uio_pdrv_genirq uio zram usb_f_acm u_serial g_serial libcomposite brcmfmac brcmutil cfg80211 ip_tables x_tables pwrseq_simple [ 5329.042410] CPU: 2 PID: 1569 Comm: armbianmonitor Not tainted 4.19.64-sunxi #5.93 [ 5329.131953] Hardware name: Allwinner sun8i Family [ 5329.188229] PC is at __dabt_svc+0x10/0x80 [ 5329.236175] LR is at copy_process.part.5+0x327/0x13e4 [ 5329.296599] pc : [<c0101990>] lr : [<c01193fb>] psr: 200f01b3 [ 5329.371582] sp : ca84beb0 ip : ca853f78 fp : 0000c350 [ 5329.434086] r10: 00000000 r9 : 00000000 r8 : 00000000 [ 5329.496591] r7 : 00000000 r6 : c0e04d48 r5 : 01200011 r4 : ca853a80 [ 5329.574695] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : c0efb38c [ 5329.652801] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA Thumb Segment none [ 5329.741303] Control: 50c5387d Table: 4a8e806a DAC: 00000051 [ 5329.810048] Process armbianmonitor (pid: 1569, stack limit = 0x74377ca1) [ 5329.890232] Stack: (0xca84beb0 to 0xca84c000) [ 5329.942338] bea0: c0efb38c ca853a80 c0e24f14 00000000 [ 5330.040202] bec0: d63a7280 00000000 00000000 00000000 00000000 c0efb784 ca853d94 ffffe000 [ 5330.138066] bee0: d069cfa0 ce638788 c0a1363c c0e04d48 000a0001 ce638600 ce638780 c0124d8f [ 5330.235930] bf00: ffffe000 c0124d8f ca850430 00000000 00000000 00000000 ca84f334 039bb874 [ 5330.333794] bf20: 00000004 01200011 00000000 c0e04d48 00000000 00000000 ca84a000 00000078 [ 5330.431658] bf40: 00000000 c011a5e1 00000000 00000000 ffffffff 00000051 ca84bf7c be8d82c4 [ 5330.529523] bf60: 00000000 be8d82c4 00000008 039bb874 c0e04d48 b6ffd238 b6ffd690 00000000 [ 5330.627385] bf80: 00000078 c0101224 ca84a000 00000078 00000000 c011a921 b6ffd238 00000000 [ 5330.725251] bfa0: b6ffd238 c0101001 b6ffd238 b6ffd690 01200011 00000000 00000000 00000000 [ 5330.823114] bfc0: b6ffd238 b6ffd690 00000000 00000078 be8d82c4 00000000 b6ffd1d0 00000000 [ 5330.920978] bfe0: 00000078 be8d8208 b6f11253 b6eb3746 200f0030 01200011 00000000 00000000 [ 5331.018852] Code: 0f04 9800 bf08 b081 (e88d) 1ffe [ 5331.076160] ---[ end trace 0b97daa0d7e18c3e ]--- Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5328.561638] Internal error: Oops: 5 [#1] SMP THUMB2 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.810048] Process armbianmonitor (pid: 1569, stack limit = 0x74377ca1) Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.890232] Stack: (0xca84beb0 to 0xca84c000) Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5329.942338] bea0: c0efb38c ca853a80 c0e24f14 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.040202] bec0: d63a7280 00000000 00000000 00000000 00000000 c0efb784 ca853d94 ffffe000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.138066] bee0: d069cfa0 ce638788 c0a1363c c0e04d48 000a0001 ce638600 ce638780 c0124d8f Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.235930] bf00: ffffe000 c0124d8f ca850430 00000000 00000000 00000000 ca84f334 039bb874 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.333794] bf20: 00000004 01200011 00000000 c0e04d48 00000000 00000000 ca84a000 00000078 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.431658] bf40: 00000000 c011a5e1 00000000 00000000 ffffffff 00000051 ca84bf7c be8d82c4 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.529523] bf60: 00000000 be8d82c4 00000008 039bb874 c0e04d48 b6ffd238 b6ffd690 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.627385] bf80: 00000078 c0101224 ca84a000 00000078 00000000 c011a921 b6ffd238 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.725251] bfa0: b6ffd238 c0101001 b6ffd238 b6ffd690 01200011 00000000 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.823114] bfc0: b6ffd238 b6ffd690 00000000 00000078 be8d82c4 00000000 b6ffd1d0 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5330.920978] bfe0: 00000078 be8d8208 b6f11253 b6eb3746 200f0030 01200011 00000000 00000000 Message from syslogd@localhost at Aug 18 00:57:21 ... kernel:[ 5331.018852] Code: 0f04 9800 bf08 b081 (e88d) 1ffe I don't know much how to read these log files and outputs so any help in understanding them would be appreciated. /Henrik

Ok, I got it working using these commands sudo wget http://goo.gl/vewCLL -O /etc/apt/sources.list.d/rpimonitor.list sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 2C0D3C0F sudo apt-get update sudo armbianmonitor -r Thanks again, rpimonitor is a great tool so I am happy to have it working!

Yes, apt update and apt ugrade is all I literally have done before trying to install rpimonitor. However now that I understand that it only installs the package from apt then I will try follow this to add a repository with rpimonitor: https://rpi-experiences.blogspot.com/p/rpi-monitor-installation.html Thank you for your help!

This is the output: chip@nanopiair:~$ apt list | grep rpimonitor WARNING: apt does not have a stable CLI interface. Use with caution in scripts. chip@nanopiair:~$

Running "sudo armbianmonitor -r" fails with this output: Installing RPi-Monitor. This can take up to 5 minutes. Be patient pleaseE: Unable to locate package rpimonitor /usr/bin/armbianmonitor: line 694: /usr/share/rpimonitor/scripts/updatePackagesStatus.pl: No such file or directory Now patching RPi-Monitor to deal correctly with H3 Now you're able to enjoy RPi-Monitor at http://192.168.11.149:8888 It isn't possible to access RPi-Monitor on http://192.168.11.149:8888. The folder /usr/share/rpimonitor does not exist. This is on a Nano PI Neo Air board with freshly installed "buster". (would have included armbianmonitor -u output but that gives this error since yesterday "(52) Empty reply from server") Any idea or fix to the RPi-Monitor install issue?

@dony71 I compiled it for nanopi neo air and put it here: https://github.com/henla464/WiRoc-StartupScripts/blob/master/devmem2 @maracuja You may also want to read this post:

@Larry Fox@triglm I started over with a Debian image and also got the initialization timeout error... By running the hciattach command a second time it kind of initialized, it gave an error message about not finding the firmware but still initialized. However I googled around a bit and found this: http://www.blog.willandnora.com/2017/08/11/bluez-5-46-hciuart-configuration-changes/ and this patch https://github.com/OpenELEC/OpenELEC.tv/blob/6b9e7aaba7b3f1e7b69c8deb1558ef652dd5b82d/packages/network/bluez/patches/bluez-07-broadcom-dont-set-speed-before-loading.patch So I decided to try to patch and recompile bluez by following https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/ This seems to fix the firmware loading issue!

On my NanoPi Neo Air it seems there is no pull up resistors on I2C (SDA, SCL). Is it possible to enable pull-up on these pins in a DTS overlay (either the standard i2c dtb or in a user overlay)? If so could anyone give me an example of how to do that...I have tried to understand the dts files but failed.

Thanks for your reply, some good points there! The extent of my Bleno/ BLE testing was to start it up, see that I could connect and list the characteristics. So I have no idea if it is stable or not. The bluetooth default address might not be registered but as long as it is 'reasonably' unique it is probably good enough for me.

Maybe this thread is of help:

I have tested Bluetooth Low Energy using bleno to implement a BLE peripherals ( https://github.com/noble/bleno ) and it appears to work! I have a requirement to have a unique bluetooth mac address for each board. And one that stays the same over reboots and flashes of new images. I tested running this: # hciattach /dev/ttyS3 bcm43xx 115200 flow omitting the bdaddr $MAC_OPTIONS part. This still works and it sets a BT mac address. It set the same BT mac address after rebooting. And when trying on my second NanoPi Neo Air it was set to another BT mac address. My guess is that it uses a unique BT mac address of the ap6212 chip. Does that sound right? But why do armbian set a fixed BT mac address? A clue can be found in /etc/default/ap6212: # Default it is called to be uncertain wich MAC address the chipset has. # Therefore it is recommendable to set the MAC address manually. # This can be done by setting the variable MAC_ADDR with a chosen value. # If this variable is empty or not set the default 11:22:33:44:55:66 will be chosen. But I don't understand this comment. Does anyone else?

I had the same problem with NanoPi Neo Air and bluetooth as mantabernd hciconfig -a didn't show any device and hciattach timed out: hciattach /dev/ttyS3 bcm43xx 115200 flow bdaddr 43:29:B1:55:01:01 bcm43xx_init Initialization timed out. The other replies here by Larry Bank and thc013 helped me solve it. uname -a Linux nanopiair 4.14.52-sunxi #581 SMP Fri Jun 29 10:05:07 UTC 2018 armv7l armv7l armv7l GNU/Linux I first used armbian-config to install BT support. Then I edited the /boot/armbianEnv.txt to add uart3 overlay and param_uart3_rtscts=1 to enable rts and cts. Since I was unsure if it was supposed to be uart1 or uart3 I looked at the schematic here and saw it was connected tu uart3: http://wiki.friendlyarm.com/wiki/images/9/98/NanoPi-NEO-Air-1608-Schematic.pdf My armbianEnv.txt: verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 param_uart3_rtscts=1 overlays=uart3 usbhost1 usbhost2 rootdev=UUID=91977eb8-39b7-4db4-ac8b-2eb075f6eef2 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Then I edited /etc/default/ap6212 to change from ttyS1 to ttyS3: # # Default it is called to be uncertain wich MAC address the chipset has. # Therefore it is recommendable to set the MAC address manually. # This can be done by setting the variable MAC_ADDR with a chosen value. # If this variable is empty or not set the default 11:22:33:44:55:66 will be chosen. MAC_ADDR=43:29:B1:55:01:01 # PORT=ttyS3 After a restart I run these commands: # rfkill unblock all # echo "0" > /sys/class/rfkill/rfkill0/state # echo "1" > /sys/class/rfkill/rfkill0/state # echo " " > /dev/ttyS3 # devmem2 0x1f00060 b 1 # echo 205 > /sys/class/gpio/export # echo out > /sys/class/gpio/gpio205/direction # echo 0 > /sys/class/gpio/gpio205/value # echo 1 > /sys/class/gpio/gpio205/value # hciattach /dev/ttyS3 bcm43xx 115200 flow bdaddr 43:29:B1:55:01:01 # hciconfig hci0 up From the schematic I found that BT_RST_N is connected to GPIOG13. I didn't find any documentation (anyone know where it is?) saying which gpio number GPIOG13 maps to but I found that GPIOG11 maps to 203 ( http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air ). After running above commands hciconfig -a returns this: # hciconfig -a hci0: Type: Primary Bus: UART BD Address: 43:29:B1:55:01:01 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:983 acl:0 sco:0 events:46 errors:0 TX bytes:2719 acl:0 sco:0 commands:46 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'nanopiair' Class: 0x000000 Service Classes: Unspecified Device Class: Miscellaneous, HCI Version: 4.0 (0x6) Revision: 0x6a LMP Version: 4.0 (0x6) Subversion: 0x2209 Manufacturer: Broadcom Corporation (15) The last step will be to add the script to /etc/init.d/ap6212-bluetooth (same as above but with the variables for port and mac_option) : rfkill unblock all echo "0" > /sys/class/rfkill/rfkill0/state echo "1" > /sys/class/rfkill/rfkill0/state echo " " > /dev/$PORT devmem2 0x1f00060 b 1 echo 205 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio205/direction echo 0 > /sys/class/gpio/gpio205/value echo 1 > /sys/class/gpio/gpio205/value sleep 0.1 hciattach /dev/$PORT bcm43xx 115200 flow bdaddr $MAC_OPTIONS hciconfig hci0 up