gounthar reacted to TonyMac32 in La Frite (AML-S805X-AC)
OK, so, if you are the sort to build it yourself, you can. It's under WIP/CSC, and is currently kernel 5.2.y. You can do a couple things, one is to flash the image (using etcher) to a USB keyfob, the other is to update your firmware, then use a USB A to A cable from the closest USB port to the IR sensor. Power up, hitting escape to interrupt the boot process, then type in
ums 0 mmc 0 to get the device to show up on the host computer. The use etcher to flash the image right to the eMMC on the La Frite.
gounthar reacted to TonyMac32 in La Frite (AML-S805X-AC)
_ _____ _ _ | | __ _ | ___| __(_) |_ ___ | | / _` | | |_ | '__| | __/ _ \ | |__| (_| | | _|| | | | || __/ |_____\__,_| |_| |_| |_|\__\___| Welcome to Ubuntu Bionic with Armbian Linux 5.2.8-meson64 System load: 1.23 0.45 0.17 Up time: 5 min Memory usage: 11 % of 967MB IP: CPU temp: 55°C Usage of /: 4% of 56G Well then. Give me a few to get it committed.
gounthar reacted to dimtass in nvidia jetson nano
Thanks balbes150, nice one.
I get Igor's concerns going the binary way. I've tested the Yocto meta-tegra layer a few weeks ago and I got a bootable image.
This is the layer here: https://github.com/madisongh/meta-tegra
This is the yocto recipe that makes the kernel:
This is the defconfig file for nano (tegra210):
This is the recipe for u-boot:
And that's the fw_env file:
This is where partitioning happens:
I know that Yocto has this mixed bash/python scripting language, but I think it's quite straight forward to understand.
Maybe you could use this as a guide to build the kernel and the bootloader.
gounthar reacted to Igor in RK3399 image through usb c
This is exactly what our build script does. For many years. But we don't deal with/support proprietary Rockchip tools http://wiki.t-firefly.com/en/ROC-RK3399-PC/upgrade_firmware_emmc.html for flashing ... which actually might even work. I successfully flashed Armbian image directly (via USB) to emmc to some older Rockchip hardware like https://www.armbian.com/z28-pro/ or https://www.armbian.com/miqi/
I assume it with this board it should go the same / similar but it is on you to try that.
We already provide proper (ofc not fully finished/polished) DTB for Orangepi RK3399 by default.
gounthar reacted to djismgaming in La Frite (AML-S805X-AC)
OK GPU is working actually, had to input this command to get it to work. Part of it is in the readme.php in the repository where the images have been uploaded by the guys @ LoveRPi.com
sudo update-alternatives --install /usr/local/lib/aarch64-linux-gnu/mali mali /opt/libre-computer/model/aml-s805x-ac/mali/lib/aarch64-linux-gnu/gl4es 100
then using sudo update-alternatives --config mali chose the gl4es entry just added
after that glxinfo and glxgears worked! FPS counter and everything.
Debian images README: http://share.loverpi.com/board/libre-computer-project/libre-computer-board/image/debian/README.php
Total Linux noob by the way but I like to tinker. README.php has no indication of this gl4es entry, although it is included in the image.
gounthar got a reaction from Myy in Ramblings and progress with the RK3399
Thanks for these commands. They helped me getting my board out of a strange mode where it only displayed hw 0 0 0 0 0 0 0 0 0 0 and powerOn "someNumbers". Before that, I could not get into MASKROM mode anymore, nor in LOADER mode... It appeared kind of bricked to me.
By the way, I read there that one could get into MASKROM mode from software by zeroing part of the boot partition.
That's what got me into that "almost bricked" mode.
If anyone has the correct sequence of commands that could do it, I will use it from now on.
gounthar reacted to Myy in Ramblings and progress with the RK3399
Alright, turns out that the
/path/to/your/rkdeveloptool rd # Reboot step in my procedures wasn't rebooting the board anyway.
So, basically, when in Maskrom mode (the mode you are in when the serial console is quiet, or when you keep the "Recovery" button pushed with the Right U-Boot), all writes are "as-is".
If you reboot (unplug and plug the power cable back again) with a Loader, a Firmware and the Trust image, you'll get into a special "rockusb" mode that offset everything by 0x2000 sectors (0x2000 * 512 bytes).
Since I'm not interested in that special rockusb mode, here's the "right" process for installing a U-Boot and Trust.img when you are in "quiet" mode :
/path/to/your/rkdeveloptool db /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Write the Bootloader /path/to/your/rkdeveloptool ul /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Which is also their firmware /path/to/your/rkdeveloptool wl 0x4000 /path/to/uboot.img # Write the U-Boot image /path/to/your/rkdeveloptool wl 0x6000 /path/to/trust.img # Write the Trust bits # "Turn it off and on again" by unpluging and plugging the power cable back (Either the USB-C cable or the power plug) # Rebooting through the little button generate "Tinkerboard"-esque issues with the eMMC, which won't be properly power up anymore.
Now, if you already have an eMMC image, you can do this instead :
/path/to/your/rkdeveloptool db /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Write the Bootloader /path/to/your/rkdeveloptool ul /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Which is also their firmware /path/to/your/rkdeveloptool wl 0 /path/to/eMMC.img # This will be STUPIDLY slow. You'll have to wait betweens 10 and 30 minutes. # Unplug and plug the power cable back again, after the command finishes.
I tested successfully these last steps and, therefore, have been able to directly flash my semi-working Armbian installation based on the Firefly RK3399 image.
So, the current step now is "Getting a Rockchip kernel working correctly with this board".
gounthar reacted to DataMannen in Ramblings and progress with the RK3399
I've always flashed my OrangePi RK3399 using Linux (rkdeveloptool) and never actually done it using Windows. However, I did fiddle around with it and noted that in order to change to english, open the file config.ini in the same folder as AndroidTool.exe, and change:
gounthar reacted to chwe in Raspberry Pi 4 Released - From $35 USD
I couldn't less agree on this one..
It is a TV box SoC with schematics.. It might not matter if you only consume and someone else provides the images.. But it matters if you're on the other side. You (mostly) know what you get, whereas TV boxes sometimes change depending on what is cheaper at the moment (e.g. different wifi module, NAND instead of eMMC etc.).
well.. IMO it was RPi who had to respond.. all those RK3399 based boards crushed the RPi fully..
I assume we'll see more specialized SBCs in the future. e.g. https://www.cnx-software.com/2019/06/19/rock-pi-s-tiny-sbc-rockchip-rk3308-processor/
some NAS ones etc.
Indeed it is the first RPi since v2 which doesn't look annoying. They try their first step away from VC4 which might be interesting.. I don't get this (claimed) full backwards compatibility of images. IMO it was a good opportunity to make a cut (keep, pin-compatibility etc. but craft an image which is either fully armhf - or arm64). having a VC4 and a VC6 branch of raspian is something the majority of their believers would probably accept.
I will likely buy one (will be the first one I bought after the Pi2 IIRC), I've a project where the A72 cores might shine, and if thermals are somehow controllable passively, 4xA72 for 35$ looks good to me (don't need really much ram for this project, it's really about numbers crunshing). They did a couple of things right, e.g. SPI NOR, USB-C instead of microUSB (btw it's a 'dumb' one right? so no PD), even the double HDMI was IMO a smart move (now it's somehow unique to its competitors). And from the software side I'm quite sure things will mature over time (looking forward to the PXE, my project would really benefit from a proper PXE implementation), and we'll soon get some deeper insights from people experienced in kernelcode.. E.g.
But I don't think that 'chinese' (whatever that means) have to respond. For different use-cased several companies have a good line-up, and the user group they target is often different.
It was a needed, and from the first glace well crafted update of the (IMO) complete failure called RPi3b+. I was surprised by the 4xA72 core they've chosen and the 1,2 and 4 GB ram was smart too. Let's face it, the average 'rich' user will always opt for the 4GB variant no matter he needs it or not and I assume the profit margin will be slightly higher with this variant.
gounthar reacted to TonyMac32 in La Frite (AML-S805X-AC)
Sort of. it is still a Meson-GXL, think of it the same was as an Allwinner H2+ when compared to an Allwinner H3
I've heard there is no plan for proper bootloader support or EXT4 boot support, apparently Broadcom parts can't do what literally any other SoC is capable of from SPI flash... So unfortunately I doubt Armbian will ever officially visit that board either...
gounthar reacted to balbes150 in nvidia jetson nano
New versions of 20190621 images for Jetson Nano. In these images we use a standard procedure of initial setting as in all the other images Armbian. The primary root password is 1234.
Automatic partition expansion may work, but I didn't check it. Please note that these are test images and I did not have time to check them all. I would appreciate feedback on what works or not in these images. Importantly. If image capture is used SD card which was previously recorded in any system for Jetson Nano. It is necessary to completely erase (zero) SD card. Details can be seen in these messages.
By default, audio output via analog is enabled, to output audio via HDMI, you need to switch the default device to HDMI in the settings panel (in the upper right corner, click on the dynamics and select the first device in the list by default).
gounthar reacted to MartyPG13 in La Frite (AML-S805X-AC)
My board arrived ahead of any tracking number, but it does appear they have been sent.
Likewise I've had no luck finding any OS images - the board does appear to seek the USB at power on and interesting goes to a network boot when the USB seek fails.
Currently this board is just a paperweight though.
gounthar got a reaction from qblueRed42 in Very Small Platforms - Rockchip 3308 and Allwinner V3s
gounthar got a reaction from darethehair in Very Small Platforms - Rockchip 3308 and Allwinner V3s
gounthar reacted to chwe in Very Small Platforms - Rockchip 3308 and Allwinner V3s
remember those dirt cheap android sticks you could buy years ago? The MK802.. I knew that I bought one years ago.. but didn't know for a long time that they're equipped with a AW A10... http://linux-sunxi.org/Rikomagic_mk802
Well, seems that they're supported in mainline (u-boot and kernel).
__ __ _ _____ ___ ____ | \/ | |/ ( _ ) / _ \___ \ | |\/| | ' // _ \| | | |__) | | | | | . \ (_) | |_| / __/ |_| |_|_|\_\___/ \___/_____| Welcome to Debian Stretch with Armbian Linux 5.1.7-sunxi System load: 2.26 1.12 0.43 Up time: 2 min Memory usage: 4 % of 999MB IP: CPU temp: 11°C Usage of /: 4% of 30G ... root@mk802:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU 21:44:11: 1008MHz 1.57 82% 30% 20% 0% 30% 0% 11.6°C 21:44:16: 1008MHz 1.68 19% 19% 0% 0% 0% 0% 10.9°C 21:44:21: 1008MHz 1.55 13% 13% 0% 0% 0% 0% 11.4°C 21:44:27: 1008MHz 1.42 22% 21% 0% 0% 0% 0% 11.2°C 21:44:32: 1008MHz 1.31 17% 14% 1% 0% 0% 0% 11.6°C 21:44:37: 1008MHz 1.20 21% 20% 0% 0% 0% 0% 11.0°C 21:44:43: 1008MHz 1.11 13% 13% 0% 0% 0% 0% 8.5°C well the thermal is a bit sloppy.. in fact the SoC was roughly 60°C at this time...
and soldering UART to test points isn't as fun.. but it works
and now imagine this board with sata instead of HDMI wired out.. (well maybe with the A20 instead of A10)..
gounthar reacted to danman in Proof of concept - Realtek 1295
Ok guys, am I in the club?
Last login: Fri May 31 19:21:18 UTC 2019 on ttyS0 _ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.86 user-built Debian GNU/Linux 9 (stretch) 4.9.176-rtd1295 System load: 1.09 0.99 0.56 Up time: 8 min Memory usage: 3 % of 1636MB IP: CPU temp: 46�°C Usage of /: 7% of 15G [ General system configuration (beta): armbian-config ]
my boot command:
usb start && fatload usb 0:1 $kernel_loadaddr vmlinuz && fatload usb 0:1 $fdt_loadaddr dtb && env set bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/mmcblk0p1 rootfs=ext4 init=/sbin/init && b2ndbc; bootr