• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mboehmer's Achievements

  1. After "apt update" I made a normal reboot. That was already end of game. Power cycle followed afterwards, with no change in behaviour. I set up now a new eMMC with normal Focal system (no desktop), and excluded the following files from upgrade: linux-dtb-current-meson64/focal 20.11 arm64 [upgradable from: 20.08.22] linux-focal-root-current-odroidc4/focal 20.11 arm64 [upgradable from: 20.08.22] linux-image-current-meson64/focal 20.11 arm64 [upgradable from: 20.08.22] linux-u-boot-odroidc4-current/focal 20.11 arm64 [upgradable from: 20.08.22] One of them (or the way it is updated) should be the culprit.
  2. Anyone had problems with "apt update / apt upgrade"? Today I updated the packets on my C4, and for some reasons the system didn't boot anymore. I will try to reproduce with a freshly etched eMMC tonight.
  3. Small update on the official image (Armbian 20.08.22 Focal with Linux 5.9.6-meson64): when I boot from eMMC, everything is fine. Inserting a Samsung uSD card leads to repeated "mmc1: error -84 whilst initialization". Trying to boot from uSD card (same image, working on eMMC) fails. System is stuck with"Starting kernel..." on console. Attaching the same uSD card by USB card reader works. So in case you find troubles with uSD card, check brand and product.
  4. Hi, have been off for a few days, too many ongoing projects. I'm really happy to see that C4 is now "supported", and want to express my thanks to all people involved! Aynway, a small issue: the download image is reporting to be officially supported, while both selfcompiled images (buster/focal) report themselfs as "trunk" images without official support. Welcome to Armbian 20.11.0-trunk Buster with Linux 5.9.9-meson64 No end-user support: built from trunk I used a freshly installed build system from yesterday night. Is this expected behaviour? The network controller problem (dwmac reset issue) of previous builts is gone, btw. uSD card issues have not been verified, I'm using eMMC on my systems. So far, Michael
  5. HI all, first of all, I found thi sissue adopting a new board to the CSC tree, done by @balbes150. As it seems to be a problem of RK3288 in general, I post here, in case please move the topic to the approriate place. I have a JLD076 board, and started adjusting the DTS to the schematic. According to the schematic, and the TRM of RK3289, there is a maximum number of 160 GPIOs. This is also the number I get from my schematics. So I expected th get suitable number of pins from gpioinfo (bank:number 0:19, 1:4, 2:18, 3:28, 4:26, 5:12, 6:19, 7:24, 8:10). Instead, I get listed (0:24, 1...7:32, 8:16). I tried now to set ngpios for the &gpioX entries in the DTS, both in the rk3288.dtsi and the rk3288-ev-act8846.dts, and verified by dtc that the ngpios entry is in the DTB file, but gpioinfo still shows the wrong number of pins. This seems to be hardcoded somewhere... any ideas on what I do wrong here? Best regards, any help is appreciated. Michael
  6. We are down... and modules seem to be in good shape. Let's hope the powerup will work as expected.
  7. To get things more structured, I start over now, and try to get things done more systematically. (1) The image found here can't be started from uSD card. I press the maskrom button shortly, following console output, and see that the RK3288 tries to boot from uSD card, but fails. (2) The images proposed by @balbes150 can be booted from uSD card, by shortly pressing the maskrom button. (3) A shortly pressed maskrom button forces uSD card booting, a long pressed maskrom button forces the board to go to RKUSB mode. Edir: @balbes150 is right, it starts also directly from uSD card. (4) I changed now to Armbian_20.09_Arm-32_bionic_current_5.9.0-rc6.img image from @balbes150. It boots, but lacks ethernet. Changing the /boot/extlinux/extlinux.conf file to rk3288-evb-act8846.dtb I get ethernet. As the genuine Linaro reports itself as "evb" and carries the ACT8846 I think this is a good starting point. EDIT: got the versions mixed up. Sorry. (5) Uboot in this image seems to use random MACs, so accessing the board is a bit nasty. is the ethaddr env supported in this Uboot? EDIT: works like a charm. No more random MACs anymore I will extend this message with new informations as they arise.
  8. I recompiled the DTS and applied it in /boot/extlinux/extlinux.conf and get ERROR: reserving fdt memory region failed (addr=7df00000 size=d4638) Loading Device Tree to 0f8a1000, end 0f8b77e4 ... OK I will try thw Q8 image now, but it seems to lack ethernet support. Can you add it to the DTB? Otherwise I have to work all over USB serial which is a pain
  9. The schematic is not under NDA; but under gentlemen's agreement. I have to ask first.
  10. I have extracted the device tree from the eMMC based linux now, and attached it here. Does this help us? I have no access to the eMMC partitions for some reasons, as the eMMC partitions are Android type dts_orig.txt
  11. Thank you for your good explanation. I'm in contact with @balbes150 already, he helped me a lot. I used one of his images, and could successfully boot the board from uSD card. My main rror was to keep the maskrom switch pressed too long. If pressed shortly, it forces the RK3288 to skip the eMMC card and use the uSD card instead - it fails to load the kernel directly (as you pointed out) and loads the included 2020 Uboot, which does the rest. If pressed too long, it goes to real MaskROM loader... AFAIK it is possible to reflash the single sectors of eMMC later with newer Uboot and rootfs? Some help on how to backup and restore the current image would be great (I did some "backup" by rkdeveltool ( rkdeveloptool rl 0x0 $((7456 * 2048)) backup.data rkdeveloptool rl 0x0 $((7456 * 2048)) backup.data but I'm not sure if this is really the way to go. For DTB work, I will need some help, but I have a complete schematics of the board, documentation on how to compile for that specific card, and I already asked the manufacturer for his DTS file. I think - apart from DTS syntax - there is no problem to get all information. I would be happy to have some kind of official Armbian build, even if I have to get maintainer I have started now with rk3288-evb-act8846.dtb, and get ethernet working, other stuff not tried yet. Maybe you can send me your DTS file to check about ACT8846 stuff first?
  12. Any idea on how to prepare a microSD card with all stuff needed? I can force the board into bootloader mode by a switch, and it tries to boot from uSD card, but fails: DDR Version 1.06 20171020 In Channel a: DDR3 400MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel b: DDR3 400MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Memory OK Memory OK OUT Boot1 Release Time: Apr 11 2018 10:32:58, version: 2.36 ChipType = 0x8, 227 mmc2:cmd19,256 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 mmc0:cmd5,32 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14924MB FwPartOffset=2000 , 0 StorageInit ok = 178583 tag:LOADER error,addr:0x2000 hdr 032c77e4 + 0x0:0x000081a4,0x00001862,0x5f5179c8,0x5f5179c8, tag:LOADER error,addr:0x4000 hdr 032c77e4 + 0x0:0xa4,0x81,0x00,0x00,0x67,0x03,0x00,0x00,0xc9,0x79,0x51,0x5f,0xc9,0x79,0x51,0x5f, tag:LOADER error,addr:0x2800 hdr 032c77e4 + 0x0:0x000081a4,0x000000f9,0x5f5179c8,0x5f5179c8, tag:LOADER error,addr:0x4800 hdr 032c77e4 + 0x0:0xed,0x81,0x00,0x00,0xfa,0x01,0x00,0x00,0xca,0x79,0x51,0x5f,0xca,0x79,0x51,0x5f, ....
  13. I received full documentation for building the "genuine" LInux of the board (won't start reading now, our deep sea deployment takes place today). I tried to backup the partition information with this tool, which works for the Android 7.1 board version, but fails on the Linux board version. Next I will try to get some uSD card image booted...
  14. I'm a bit wiser now: in Uboot the partition table is like this: Partition Map for MMC device 0 -- Partition Type: EFI Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00004000 0x00005fff "uboot" attrs: 0x0000000000000000 type: cb280000-0000-4d3c-8000-7b5800000ab9 guid: dd3d0000-0000-473b-8000-58800000230e 2 0x00006000 0x00007fff "trust" attrs: 0x0000000000000000 type: e86f0000-0000-495e-8000-30c300005377 guid: 42040000-0000-4900-8000-019800001cf7 3 0x00008000 0x00009fff "misc" attrs: 0x0000000000000000 type: 7f330000-0000-4c09-8000-3ab3000015d5 guid: 742c0000-0000-4607-8000-520800000195 4 0x0000a000 0x00019fff "boot" attrs: 0x0000000000000000 type: 372e0000-0000-4d35-8000-55ce00005cfc guid: 1c160000-0000-4611-8000-747800006a10 5 0x0001a000 0x00029fff "recovery" attrs: 0x0000000000000000 type: b96d0000-0000-456b-8000-14bc00004914 guid: e2790000-0000-4074-8000-628f00007f8f 6 0x0002a000 0x00e8ffde "rootfs" attrs: 0x0000000000000000 type: ad500000-0000-4b4d-8000-5d2600000f44 guid: 614e0000-0000-4b53-8000-1d28000054a9