Super Console X Dtb.img
Bartley Trowbridge
It helps as well as those who have invested in the earlier OPi Zero 2 would see continuity and all these efforts to test and mainline the recent changes for H616 Orange Pi Zero 2 likely works well on Orange Pi Zero 3 (just fresh out of the oven) as well.
I can confirm 4GB model works with -images `ubuntu22.04 server` for the first time when I logged in as root. After I reboot or shutdown it disappears from the `ipscan`. Unfortunately I'd had no hdmi-micro hdmi cable to connect the SBC directly to the monitor couldn't go further debugging. Anyway the non-official Armbian image provided by the official Orangepi team works..weirdly.
well, I still have problems typing things into the console, it seemed the characters typed 'didn't get across' to the H618 uart, even though this time the text is properly received and displayed at 115200 baud from a different PC
@ag123 can you post the full bootlog for the armbian release from GitHub (23.08)?
I tried both bookworm and jammy with several micro SD cards (including name brands like Samsung) and my board (4GB model) never gets further than the following:
And yes, I did copy the 4GB dtb and u-boot as instructed.
I know this forum is not the place to ask for support for unofficial Armbian forks, but I'm just curious if you encountered any such issues. If I remove the micro SD card entirely, the board boots some kind of Android from the SPI:
3 Then insert the TF card that has been burnt into the opizero3 linux6.x system into other linux machines
4 Then use the sudo fdisk -l command to view the device name of the tf card: For example: /dev/sdax
5 Then mount the file system in the tf card to the /mnt directory of the linux machine: sudo mount /dev/sdax /mnt
6 Then copy the dtb file to the /boot/dtb/allwinner/ directory in the TF card (please modify this directory according to the actual situation, do not copy):
Note that steps 3 - 7 are done on a different Linux machine (which probably can even be a small board e.g. Raspberry Pi or an existing Armbian board that runs. And assuming that you are workng it say on a usb SD card reader.
If you are working that on your PC, do be careful with the commands, as it is intended to edit binaries on the image written to a TF card. Be careful about working on your PC to idenfity the correct device disk or risk trashing data on your hard drives.
I carved u-boot out of the Jammy image from Google Drive (Orangepizero3_1.0.0_ubuntu_jammy_server_linux6.1.31.7z) and applied it to the bookworm image (along with copying the dtb, as instructed) and now it's booting. I updated the GitHub issue with my test results.
I'll attach it here so that people don't have to download a 575MB image from Google Drive just to carve it (gunzip it first).
I've got a weird problem on the OPi Z3, thus far I've seen all the boot messages on the serial console, it turns out it is /dev/ttyS0. However, it doesn't 'accept/receive any inputs'. Hence, I can't login over serial tty.
but that there are 'cheap and good' usb-uart dongles, e.g. the (original, as in the chip) FT232 dongles and a search for "usb uart" in the usual online marketplaces Amazon, Ebay, Aliexpress etc would turn them up.
Note that when you are playing with bridging etc, it is advisable to use the uart interface. it is super easy to hose the connected ethernet interface e.g. using nmcli network manager commands and after that there is 'no way' to access the board other than using uart (and perhaps usb gadget) interface.
but thinking it through, the steps would likely to be quite similar with tests etc. e.g. that it is less likely to be a 'just works' setup and requires quite a bit of work to have all the peripherals working.
But that among the surprises, it seemed there are some hardware problems even with those images released by Orange Pi. Ethernet is not working after a while and after a few reboots, things are totally jammed even on the serial console.
I have the same issue on the OPi Zero 3. I used the Armbian image in the leeboy/armbian repository and followed the instructions on updating the dtb and bin file for the 4gig variant and it works. however WIFI does not and I can't connect at all. I see that there was an issue that was fixed earlier this week regarding the Orange Pi Wifi drivers and xradio not working. I think if someone was to pull the latest armbian and build the kernel it might work (I'm very new to all this, otherwise I would!).
Trying to use the sdcard image from snapshots for the espressobin and am not quite sure how to get it to work. Writing the image with dd (I think) breaks a load of symlinks as, on boot, the kernel cant locate an init system and when extracting with 7zip the inner images of the disk image for partition two (root partition) show symlinks broken when extracted. Not sure how to get it to work and some help would be nice
Then, put the card back in the espressobin, and connect to it over serial as it boots up to get to the U-Boot prompt. Follow the instructions here for setting the boot parameters, except the following lines:
The problem in Your case is that when You change the size of a partition, it's not the only thing that changes. When it's performed also new PARTUUID is assigned, and that is the root cause for stalled boot. To check this You can use blkid.
Ok I understand what you are saying but I'm still a bit new to this so. How would I go about expanding the partition?
Option 1 : Manually rewrite the partition
Where/how would I do that?
Option 2: Recreate boot.src
How would I go about that?
Option3: use Image builder
Is that way more advance? Would that be the best option?
How would I do that?
Add. 1
Not to rewrite the partition but the MBR. To rewrite it You'll need hex editor for that, never done that myself.
You do that after partition expanding.
Add. 2
If You followed the instructions in commit introducing ESPRESSObin, U-Boot searches in the first partition on SD card for small boot script named boot.scr. In this script there are few commands for U-Boot itself to execute and few options passed to kernel (one of them is PARTUUID). The script is viewable by any text editor but it embeds also a checksum, so if You'll change it, without adding proper checksum, U-Boot will complain that it's invalid. To generate proper script, You feed plain script file to mkimage which is part of uboot-tools (may be that it's called different in Your distro).
This is also done after partition expanding.
Add. 3
It's the easiest one (my biased opinion). Download the image builder from the same download directory as the SD card image for ESPRESSObin. Unpack, edit .config file like i mentioned in previous post, and build the image (for available commands run make help, more generic infos: -user/additional-software/imagebuilder). Write resulted image to SD card and enjoy.
I was able to successfully create a custom image ROOTFS to fill a 64GB SD card with your instructions. Thanks. Now I would like to find the OPTION to expand the filesystem instead of creating these unruly images. Had to create a virtual disk image twice the size of the image I wanted to create just to avoid write failures. Any thoughts?
I really like OpenWRT from the user end rather than the Linux experiment and compile end, and I'm a Linux user only to the extent of what I see in Windows PuTTY and WinSCP. So I am sitting here with an Espressobin V5 and a 16G super fast SD. Is there currently a shorter route to get the my V5 up and running? Thanks!
***** Anyone willing to share how to easily build a 16GB SD card using Windows so I can boot this machine and get started? I am a long-time OpenWRT fan but only use the basic plug and play in the past (and thanks to the countless who have brought it to this level for those of us who struggle with the constant changes in technology)
Espressobin was incidentally suggested to me here in the OpenWRT forum to use as a network drive server. I know I could likely spend hundreds of dollars on one of the new routers that look like an alien space pod with 20 antennas on them but this was presented to me in another post by the OpenWRT community as an economical NFS solution and I am anxious to get started. I'd like to simply use a Windows utility to burn a SD card but I am guessing from above it's not that simple.
The ext4 image will not have that "revert to stock" option that you're used to with OpenWrt, but the squashfs will... On the other hand, if you want to revert to stock, you can always yank the card and reflash the image. So I'd recommend the ext4 version.
I am not subscribed to this and missed your comment. Thanks for providing it. What I have done up to this moment is to use Win32diskimager to build the 16GB very fast SD card. I followed instructions online to install the PL2303 drivers and when I plugged in the board, I was assigned COM4 (unique to each install) and then I configured PuTTY for a SERIAL connection to COM4 (seen from Windows Device Manager, Com ports) at a speed of 115200 and then I powered on the device and I received this. I am not sure what this says, maybe it says that the card image is no good???
OK I downloaded Balena Etcher and flashed the same file to the SD card. This time the boot sequence went forward but it paused for a moment to see if I wanted to stop autoboot but then it kept on going. Here is my console output:
Just like my microcontroller article, the parts I picked range from the well-worn horses that have pulled along products for the better part of this decade, to fresh-faced ICs with intriguing capabilities that you can keep up your sleeve.
Network security is about limiting software vulnerabilities and creating a trusted execution environment (TEE) where cryptographic operations can safely take place. The classic example is using client certificates to authenticate our client device to a server. If we perform the cryptographic hashing operation in a secure environment, even an attacker who has gained total control over our normal execution environment would be unable to read our private key.
c80f0f1006