John Brooks

Members
  • Content count

    5
  • Joined

  • Last visited

  1. Armbian for OrangePi PC2, AllWinner H5

    Thanks for the links jernej. Looking at the lowlevel BSP src files, the DE system sure has a lot of registers and functionality. With a footprint of 4 megs, it consumes more address space than any other H5 subsystem. It looks like the H5 support for 4.11 expects a simple framebuffer passed in from uboot, but it looks like the new uboot is passing an HDMI device entry to 4.13 instead of a framebuffer? It makes sense to have Linux create it's own framebuffer when HDMI is detected/activated instead of being a one-time event at boot. -JB @JBrookSBSI
  2. Armbian for OrangePi PC2, AllWinner H5

    I built the mainline 'next' branch today (not dev) using the compile.sh UI option and targeting the OPIZP2-H5 board. It built and booted up fine using serial tty, though there were 2-3 boot log errors. The CPU was running at 768MHz and did not seem to scale with CPU load or thermals. With a heat sink attached to the H5, I was able to change the clock speed to 1200MHz via CCU reg 0 and it appeared to stick (ie, not altered by linux). Performance was about 33% faster at 1200MHZ compared to 768MHZ. FWIW, all 4 cores share one clock, so no per-core speed control on the H5. Wifi is working now on the Zero-H5. The missing items I noticed today compared to 4.11 were no HDMI console, and no /dev/sda* for mounting USB flash drives. It looks like the HDMI console is handled differently in the new uboot & kernel 4.13 (ie, no framebuffer@x device, but rather an HDMI device). Thanks for the rapid improvements on kernel 4.13. Impressive work. -JB @JBrooksBSI
  3. Armbian for OrangePi PC2, AllWinner H5

    How do I select that branch during the Armbian build? I am currently using "./compile.sh BOARD=orangepizeroplus2-h5" which selects the icenowy 4.13 branch. -JB @JBrooksBSI
  4. Armbian for OrangePi PC2, AllWinner H5

    That is why I was thinking of building the 4.11 version from source so I might compare its working wifi & HDMI console to the inoperative versions in 4.13. My expertise is more embedded systems/C/asm, so I didn't spot anything obvious in the shell scripts. All the --menu args appeared to correctly have 5 parameters. I am not sure where to find the source & OPIZP2-H5 config for that version. Can someone point me in the right direction? I saw another distro forum talking about an A0 and A1 firmware version for the AP6212. Any idea which version the OPIZP2-H5 needs and if that could be part of the problem? Can the (working) 4.11 driver be used with 4.13 or is there a compatibility issue? Other questions/findings: 1) I can't seem to find register info for the Allwinner Display Engine (DE) 2.0 in either the H3 or H5 TRM. I did find a reasonable description of the DE 1 registers in the A33 TRM, but it is a generation out of date and of questionable value. Anyone have tips on where to find DE 2 info? 2) FYI: I'm pretty sure there is a hardware bug in the H5 (and probably H3) SPI controller when configured in slave mode. The bug is that when the H5 empties the Tx FIFO, instead of sending bytes of zeroes on subsequent master-initiated transfers, it sends a repeating 4-byte pattern of zero bytes alternating with some of the last bytes the app wrote to the Tx FIFO - ie, Tx register is not properly cleared at FIFO empty which then causes retransmitted 'garbage' slave data. My current workaround is to end each SPI slave transfer with an extra 4 bytes of zeroes. Thank you for your help and pointers guys. -JB @JBrooksBSI
  5. Armbian for OrangePi PC2, AllWinner H5

    I am interested in evaluating the work-in-progress Armbian for OrangePiZeroPlus2-H5 using the mainline kernel. The binary image "ARMBIAN 5.27.170614 nightly Ubuntu 16.04.2 LTS 4.11.1-sun50iw2" has worked well for me for several weeks and I would like to try building it from source. Any tips/pointers on where to grab the source and configuration for that version or is it just github master branch as of 5.27.17? I have pulled and built the latest in-progress 4.13 kernel version "ARMBIAN 5.32 user-built Ubuntu 16.04.3 LTS 4.13.0-sun50iw2", and would prefer to evaluate and contribute to fixing this codebase if possible. The head builds fine using the config "./compile.sh BOARD=orangepizeroplus2-h5" and the resulting image does boot. Here are the issues I've seen so far testing the master branch for OPIZP2-H5: 1) Boot errors: [ OK ] Started Login Service. Starting LSB: set CPUFreq kernel parameters... [FAILED] Failed to start LSB: Patch firmware for ap6212 adapter. See 'systemctl status ap6212-bluetooth.service' for details. [ OK ] Started LSB: set CPUFreq kernel parameters. root@orangepizeroplus2:~# systemctl status ap6212-bluetooth.service ● ap6212-bluetooth.service - LSB: Patch firmware for ap6212 adapter Loaded: loaded (/etc/init.d/ap6212-bluetooth; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-09-11 18:17:48 UTC; 3min 53 Docs: man:systemd-sysv-generator(8) Process: 575 ExecStart=/etc/init.d/ap6212-bluetooth start (code=exited, status Sep 11 18:17:48 orangepizeroplus2 ap6212-bluetooth[575]: /etc/init.d/ap6212-blue Sep 11 18:17:48 orangepizeroplus2 ap6212-bluetooth[575]: /etc/init.d/ap6212-blue Sep 11 18:17:48 orangepizeroplus2 ap6212-bluetooth[575]: sh: echo: I/O error Sep 11 18:17:48 orangepizeroplus2 ap6212-bluetooth[575]: Can't get port settings Sep 11 18:17:48 orangepizeroplus2 ap6212-bluetooth[575]: Can't initialize device Sep 11 18:17:48 orangepizeroplus2 ap6212-bluetooth[575]: Can't get device info: Sep 11 18:17:48 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Control Sep 11 18:17:48 orangepizeroplus2 systemd[1]: Failed to start LSB: Patch firmwar Sep 11 18:17:48 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Unit ent Sep 11 18:17:48 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Failed w 2) HDMI console is not working. U-boot draws text to the HDMI console at power up, but there is no output from linux afterward and the display reports no HDMI output signal. I'm using a serial tty console for now. 3) WiFi is not working. This is the major blocker for me to do more testing with the H5 & 4.13 kernel. root@orangepizeroplus2:~# nmcli g STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN disconnected none enabled enabled enabled enabled Armbian config reports errors on the UI: I'd appreciate any tips on how to proceed and/or how I might contribute to fixing things. Thanks! -JB @JBrooksBSI