markbirss

The type of remote control does not matter as long as it operates near the 38kHz carrier frequency and a suitable rc_keymap.toml is loaded. The reason I used the RC-100 is because I'm using the SD card I originally set up for my NanoPC-T4, and there this remote was configured for rc-empty. Therefore, it worked out of the box.
Went on to 5.19.0-rc3. And with the Enable-JPEG-Encoder-on-RK3566-RK3568.patch, a JPEG encoder is also available (videoX-infos.log). MGLRU is also pulled in again but only to see if it does not cause regressions with Odroid M1.

Ok, I went on to 5.19.0-rc1. I was able to skip a lot of mainline commits from tobetter's tree because they landed, and for the remaining WIP commits, I switched to more recent ones. Some of the WIP commits are already in staging and will land sooner or later.
For those who are interested, I have attached glmark2 logs. The performance is not yet overwhelming, only the basic functionalities have just landed. But the graphical desktop works pretty decently. So the fine-tuning season is open.
And with the hantro decoder wired up, hardware-accelerated video decoding of H.264 and VP8 works up to 1080p. See fluster-run.log for reference.
Went on to 5.19.0-rc2. And with the ir-receiver wired up, my RC-100 works out of the box.
Rant: Why doesn't editing allow spoilers to be created with sections of code?
glmark2-wayland-odroid-m1.logfluster-run.log

Have been exploring Dingleberry Pi 2
 
QC/Atheros IPQ4019 - more relevant here for the ARM folks - IPQ4019 is a quad core Cortex-A7@800MHz
 
Buys us GigE on WAN/LAN ports, along with ATH10K for dual-band 802.11 a/b/g/n/AC Wave2 along with USB3.0 for the USB user facing port.
 
BOM cost is higher, as it manf. costs with more layers, and more power needs - and numbers there do not make sense for an affordable board for this community - $100 GOGS there...

Quick update on DingleBerry Pi...
 
Schematics - done - It's essentially a respin of the QC/Atheros reference design into a Pi board form factor.
Layout/Gerbers - done - 4 layer board, single sided - nice to have a friend with an Orcad license from Cadence.
 
Specifics
MIPS24kc @ 650Mhz - big endian 802.11n - ATH9K driver - 2*2:2 for 300Mbps at 2.4GHz (wide channels) - PCB trace antennas Two 100Base-2 Ethernet - WAN dedicated port, LAN on switched port One USB-A for peripherals MicroUSB for Power/Console 32MB SPI-NOR flash - uboot and OS 128MB SPI-NAND flash - extending FS for application and user space 64MB DDR2 RAM SW - OpenWRT Master on the ATH79 target Bootloader - uboot with Pepe2K mods (web server fail-safe)  
The 4351 does have PCIe, but I've decided not to implement
 
Performance Targets:
Reference board is good for 100Mbps WiFi and NAT LAN/WAN performance so fairly balanced there. Power - 5V5DC, 1000ma for PS - right now with everything active on reference design, we're around 850ma at max load.  
BOM is reasonable, COGS says we're around $50USD to cover the NRE and breakeven with 1K boards with kits (box, cables, boards, ac adapter)
 
I will not build/ship at a loss... So the next step before doing the engineering sample boards it to gauge the potential market interest.

Hi,
First of all i'm NOT a software developer and i have NO one skill on this kind of board's hardware...
I've a good soldering skill, so just for fun i've bought a new RAM module for my OrangePi Zero Board...

I've bought a K4B4G1646E-BYMA RAM module and then i've replace the onboard module...
All of the work gone fine, the OrangePi Zero still boot and work perfectly, but i was hoping to upgrade the RAM on the board...
After the boot, in the welcome screen the, the RAM amount is now 512MB (494MB) and before was 256MB...
The RAM amount is now increased, but not like expected...

I've choose the K4B4G1646E RAM module because, theoretically, it was a 4GB RAM module...

What's was wrong? I cannot upgrade the memory in this way? Have i to edit something in the FEX file?


Thanks in advance,
Luca

Ps. my OrangePi Zero come without an inductor, that's why you see an horrible inductor in my board

Since the PCB itself doesn't route the extra address lines to the SoC, you can't expect to see bigger DDR size than the one provided by manufacturer.
And you're lucky that it still boot, because the extra address lines left unplugged on the DDR are floating, therefore any ESR on those lines could change the current bank and memory could becomes corrupted...

Actually, nothing is wrong. You got exactly what you should expect.  The K4B4G1646E-BYMA is a 4 gigabit ram module.
 
BTW: impressive that you can resolder a BGA at home. Congrats.

Added nightly minimal images (root ≈ 500 Mb in size) for La Frite.
https://dl.armbian.com/lafrite/

thank you.

Oh ! I forgot to upgrade one : Olimex-Micro-A20 ... I will start a new build ...

Today I did clone and compile kernel 4.14 from:
https://github.com/Lichee-Pi/linux/tree/zero-4.14.y
with their standard setttings (.config)
 
The resulting zImage ( 4.14.14-licheepi-zero+ ) does also work with Ethernet / Audio-Codec and the Tripple-Status-LED
 
I did put the 4.14.y zImage as zImage_Kernel_414.zip on my GoogleDrive (see above for the link)
 
I do like the small 23MB footprint of this small Linux (would like to see such Linux on a Router which normally do use OpenWRT - many of them have 128MB RAM, but less Mhz)
 

@guidol here is for reference the minimal buildroot guide for the Lichee Pi Zero for comparison
https://github.com/Squonk42/buildroot-licheepi-zero-old/wiki/Build-system-–-Installation
 
https://github.com/Squonk42/buildroot-licheepi-zero
 
https://github.com/Squonk42/buildroot-licheepi-zero-old/wiki/Fresh-image-–-Booting
 
https://hackaday.io/project/134065-funkey-zero/log/144796-linux-distribution
 
 
 
 
 
 
 
 
 
 
 

I checked with the author to see if we could really increase the 80x25 terminal size. 
He said at the time he set the 80x25 limit it was due to the limited available ram of the ESP8266 devices
 
My attempts to try 80x30 was not yet successful
 
 
 
 

take a look here
 

didn't you call a challenge for the first one who gets armbian to run on a V3s some months ago?
 
_ _ _ ____ _ _____ | | (_) ___| |__ ___ ___| _ \(_) |__ /___ _ __ ___ | | | |/ __| '_ \ / _ \/ _ \ |_) | | / // _ \ '__/ _ \ | |___| | (__| | | | __/ __/ __/| | / /| __/ | | (_) | |_____|_|\___|_| |_|\___|\___|_| |_| /____\___|_| \___/ Welcome to ARMBIAN 5.74 user-built Debian GNU/Linux 9 (stretch) 4.20.2-sunxi System load: 1.90 0.67 0.24 Up time: 1 min Memory usage: 58 % of 50MB Zram usage: 36 % of 25Mb IP: Usage of /: 4% of 29G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Thank you for choosing Armbian! Support: www.armbian.com Creating a new user account. Press <Ctrl-C> to abort Please provide a username (eg. your forename): got one on Christmas.. didn't have time to dig into it.. but well.. here you are.. Armbian booting from a LicheePiZero 
 
Does it make sense? not really.. but hey.. who cares.. it boots.. in less than 30 seconds..

Here is the Lichee Pi Zero with 4.3inch 800x480, keyboard and Li-Po battery. (also using a ESP8266 ESP-01 for Serial console over wifi)
 
 
 

Here the Lichee Pi Zero Dock that I got Ethernet port working that I will use
 
 
 
 

Tablets like this, I bought it at ebay with broken Touch for testing, also a broken 10,1" Tablet, this was also working for testing, and an A88S from alldaymall.
 
Wifi is also working, but this can change from tablet to tablet.
 
Yuntab Q88H - 7 Zoll Tablet PC，Android 4.4, Quad Core, HD 1024x600, Dual-Kamera, Bluetooth, Wi-Fi, 8GB
https://www.amazon.de/dp/B01IJRDGGK

Not related to armbian, but I made some work with friendlyarm kernel 4.11.2 for support i2s driver for h3/h5 with support 16/24 bit master/slave mode i2s (link) and build Volumio image for nanopi neo (link). In future I want to get same in mainline kernel.

Hi Markbirss, I checked it again with current build and it's working with module "g_serial" add to boards/lime-a33.conf
 
config/boards/a33-q8-tablet2.conf
# A33 quad core 1Gb SoC BOARD_NAME="q8 A33" BOARDFAMILY="sun8i" # depending of board and resolution use a defconfig file from sources/u-boot/v2018.05/configs BOOTCONFIG="q8_a33_tablet_1024x600_defconfig" #MODULES="hci_uart gpio_sunxi rfcomm hidp bonding spi_sun7i 8021q a20_tp" MODULES="hci_uart gpio_sunxi rfcomm hidp bonding spi_sun7i 8021q a20_tp g_serial gslx680 gc0312 gc2145 rtl8150" MODULES_NEXT="hci_uart gpio_sunxi rfcomm hidp bonding spi_sun7i 8021q a20_tp g_serial gslx680 gc0312 gc2145 rtl8150" OVERLAY_PREFIX="sun8i-a33" # KERNEL_TARGET="next" CLI_TARGET="stretch:next" DESKTOP_TARGET="" # RECOMMENDED="Debian_stretch_next:75" ~/armbian/cache/sources/u-boot/v2018.05/configs$ ls -1 *[Aa]33* A33-OLinuXino_defconfig q88_a33_tablet_1024x600_defconfig q8_a33_tablet_1024x600_defconfig q8_a33_tablet_800x480_defconfig Sinlinx_SinA33_defconfig  
I had to disable the pwm_bl module, otherwise the screen will go black while boot.
echo blacklist pwm_bl>/etc/modprobe.d/pwm.conf I checked it with some Allwinner A33 Tablets from eBay or Amazon, the touch isn't working at the moment, but I hope I have time to check it in the future.
 

It should be noted, however, that such thick SILPADS are quite bad when it comes to thermal resistance. While in some cases using such a thick pad and some metal may be better than nothing at all, it is better to avoid them and find a better solution. Using thermal pads or paste or glue is mainly to bridge air gaps due to imperfect surfaces. That stuff isn't really that thermally conductive at all, it just happens to be better than air. The general rule is that such layers should be as thins possible.
 
Using a small 14x14x10mm heatsink, attached with thermal glue, is very likely to be far better than a 4mm SILPAD and a big piece of metal. Nice, suitable heatsinks for the H3 would be these: http://www.ebay.de/itm/172290970476. Add a very small dab of heat conductive glue, for example http://www.ebay.de/itm/181026615992, then put on the heatsink, align it and finally press it down _really_ good (most of the glue should squeeze out on the sides). Let it sit for a while until it's cured, done.
 
Greetings,
 
Chris

This topic continues here with the solution:
 

One of the Banana Pi employees took @zador.blood.stained's work, added a Windows GUI and extended SoC support from H3 only to A64, A83T and even H5: http://forum.banana-pi.org/t/the-3rd-party-emmc-flash-tool-for-bpi/4080

What do we know now? Not much  -- most importantly that some details will change and 'board available soon'.
 
We have a H6 Product Brief available and a few selected developers already had a look into user manual (NDA situation right now, so not possible to get any answers from them  )
 
So all we know is really just:
H6 is limited wrt DRAM (2GB DDR4/DDR3/DDR3L max), I know the DRAM manufacturer from the modules in my Beelink X2 but have forgotten the name The Ampak module might be an AP6356S providing dual-band/dual-antenna Wi-Fi + BT 4.1 Gigabit Ethernet (H6 is said to have a 2nd Fast Ethernet MAC/PHY but no idea how/whether exposed here -- maybe available on pin headers to be combined with an external MagJack like it's possible on ROCK64 or NanoPi Duo)  One HDMI is a v2.0a output for sure, the other can be another HDMI output (LCD to HDMI converter) or maybe also a HDMI to TS input (depends on the type of chip behind the left HDMI port) eMMC on board One of the USB receptacles is blue (USB3 SuperSpeed), the other is USB2 and I would believe the remaining USB2 port is available on pins 36/38 of the mPCIe connector allowing to attach 'miniPCIe WWAN modems' (to be combined with the SIM card slot -- AFAIK these modems use USB at a 3.3V logic level) the mPCIe slot also exposes H6's single PCIe 2.x lane there's AV, optical audio out and an IR receiver (positioned IMO somewhat strangely since if rotated 90° on the PCB side next to its actual location OPi 3 Plus combined with a little enclosure would already make up for a complete TV box)