TonyMac32

Under a dozen developers, seemingly hundreds of boards. I think between lack of hardware in developers hands and really low download numbers were primary reasons.

I'll be able to check later, but the SD is ext4, and I am moving the same physical SD between the two revisions of the board without any other changes. I did a lot of other tests on my own earlier on, MMC 0 is not present (and is not installed, so ok). Sent from my Pixel using Tapatalk

This is from Rock64 Rev 3. => version U-Boot 2017.09-armbian (Mar 20 2019 - 22:48:31 -0400) aarch64-linux-gnu-gcc (Linaro GCC 7.2-2017.11) 7.2.1 20171011 GNU ld (Linaro_Binutils-2017.11) 2.28.2.20170706 => ls mmc 1:1 ** No partition table - mmc 1 ** => ls mmc 1:0 ** ext4fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** => Pulling the exact same card out of the Rev 3 and stopping boot on the Rev 1: => version U-Boot 2017.09-armbian (Mar 20 2019 - 22:48:31 -0400) aarch64-linux-gnu-gcc (Linaro GCC 7.2-2017.11) 7.2.1 20171011 GNU ld (Linaro_Binutils-2017.11) 2.28.2.20170706 => ls mmc 1:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <DIR> 4096 bin <DIR> 4096 boot <DIR> 4096 dev <DIR> 4096 etc <DIR> 4096 home <DIR> 4096 lib <DIR> 4096 media <DIR> 4096 mnt <DIR> 4096 opt <DIR> 4096 proc <DIR> 4096 root <DIR> 4096 run <DIR> 4096 sbin <DIR> 4096 selinux <DIR> 4096 srv <DIR> 4096 sys <DIR> 4096 tmp <DIR> 4096 usr <DIR> 4096 var => ls mmc 1:0 Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** =>

I would guess using the chiptenna it suffers significantly. That would be why there is a hole on the same side as the SD card to mount an external antenna and use the connector on the RTL8723BS

Same. At $100 it fits in nicely.

Sure thing.

Hi@Ayufan, perhaps then I will focus on the Renegade, I was starting to get into the code last night for mainline u-boot. Have you seen my concerns with Rock64 rev 3? Sent from my Pixel using Tapatalk

I don't think this has anything to do with the drive strength, I can scan different SD's with no issue, reading the mfg info/type/size/etc. But it won't recognize the filesystem in any of them. (Tried 6 different ones) Sent from my Pixel using Tapatalk

Sorry I didn't get back to you, but here goes: => mmc list rksdmmc@ff520000: 0 rksdmmc@ff500000: 1 (SD) => mmc info Device: rksdmmc@ff500000 Manufacturer ID: 3 OEM: 5344 Name: SL16G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 14.8 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes => ls mmc 1 ** ext4fs_devread read error - block Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Now, to be completely clear, that SD card boots perfectly on a revision 1 board. I was talking to Pine, I think I might have to reach out again. Interestingly, if I stuff my Renegade SD into the Rock64 I get this: DDR version 1.13 20180428 ID:0x805 Y In LPDDR3 786MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB ddrconfig:1 OUT Boot1 Release Time: Feb 2 2018 15:41:39, version: 2.46 ChipType = 0x11, 147 SdmmcInit=2 0 BootCapSize=0 UserCapSize=0MB FwPartOffset=2000 , 0 SdmmcInit=0 0 BootCapSize=0 UserCapSize=15193MB FwPartOffset=2000 , 0 StorageInit ok = 39136 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 LoadTrustBL No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x91d80 RunBL31 0x10000 NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 12:41:19, Mar 3 2019 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using rkfiq sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian (Mar 19 2019 - 23:49:43 -0400) Model: Firefly ROC-RK3328-CC DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Firefly ROC-RK3328-CC misc_init_r boot mode 0. Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2949 bytes read in 20 ms (143.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 151 bytes read in 17 ms (7.8 KiB/s) 8767906 bytes read in 427 ms (19.6 MiB/s) 14107136 bytes read in 664 ms (20.3 MiB/s) 48282 bytes read in 32 ms (1.4 MiB/s) 1847 bytes read in 31 ms (57.6 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8767842 Bytes = 8.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 3d6b7000, end 3df13962 ... OK reserving fdt memory region: addr=1f00000 size=72000 Loading Device Tree to 000000003d642000, end 000000003d6b6fff ... OK Starting kernel ... ...Where it of course freezes because it is not a Renegade and they are different enough for that to be a problem. What options and hardware combo would wreck reading the SD card? *head explodes*

Probably a good question, are you concerned about emissions from the SBC or immunity of the SBC to outside noises? Obviously increasing drive levels makes the square waves more square, meaning higher frequency content. For immunity, my guess is conducted immunity through the power supply is a touchy spot, being supplied 5 V and running on 5V, no chance to avoid noise.

Mmhmm. my V1 has no problems with our u-boot, it is fine from eMMC and from SD. The V3 is fine from eMMC if I 'transplant' it from the V1 to the V3. SD using our u-boot recipe somewhere goes wrong on V3, so I need to debug

Hi @Thewonderer, I have dev samples of a few boards, it's one of the ways we work with vendors that show interest. My other Rock64 is a pre-V1, so I wanted to make sure I had something representative moving forward. I've had some personal projects going, and @martinayotte moved so much around on these boards I decided to stay out of the way. Taking a look at the u-boot configs and device trees tonight to see if I can find a difference, the Renegade image got to the point of loading kernel (obviously didn't get past that with the differences in DTS's) on the Rock64 3.0 while the Rock64 V1/2 image would not, telling me there's no hardware issue. @martinayotte did you try to boot Renegade with newer u-boot? I can't remember if you have one or not.

I ran tinycore on some PC's a long time ago for experimentation purposes. I check back from time to time.

Hmmm, last test I had 4k60 on potato and K2 with a samsung monitor... Sent from my Pixel using Tapatalk

Agreed. I'd forgotten that, for standard Armbian nand-sata-install works, but you have to boot Armbian first to get that far. I wasn't able to brick it on purpose using the USB burning tool because it's built not to allow it. (Of all the things for them to do right...)