Xalius

Has the rx/tx delay been tuned on the Tinkerboard? Since we did that for Pine64/Rock64 most of the GbE issues have gone away. Ayufan made an automated script that uses configfs/dt-overlays to iterate through all the values without rebooting each time, based on tkaiser's scripts... https://github.com/ayufan-rock64/linux-build/tree/master/recipes/gmac-delays-test This resulted in a small patch that did wonders for GbE performance: https://patchwork.kernel.org/patch/10178969/ Worked both for BSP and mainline...

Some more infos around the 11 inch model (should be back in production, display sourcing problem is solved, but afaik DRAM prices are too high to start production...) and a new variant will be released at FOSDEM as far as I understand Tl Lim...

I am all for using the ARISC for useful things , it is somewhere on my TO-DO list but my day only has 24h so I never got around to try anything yet...

There are some people in the linux-sunxi community that have started writing custom firmware for the AR100, do you follow #linux-sunxi on freenode? For hard real-time applications I would personally go for a setup where the motor control is done by a MCU (Cortex-Mx, AVR32...) and the high level stuff by a SBC...

Hi, do you have any logs you can provide from one of the Tinkerboards? While RTL8723BS is not the most stellar of wifi chipsets, the Armbian tweaks to it's default config usually work quite well...

Yes firmware+u-boot are on the SPI flash, only the rootfs is on USB or network... check https://github.com/ayufan-rock64/linux-build/releases https://github.com/ayufan-rock64/linux-build/releases/download/0.6.16/u-boot-flash-spi.img.xz is a sdcard image that writes the bits to SPI https://github.com/aw/linux-build/blob/2fec6745b584c2bbc5fbe15d4cbaacd62c096b24/recipes/flash-spi.md for the how-to

I will be at FOSDEM (Bruxelles, BE) 2018 next week... https://fosdem.org/2018/ If you want to meet up or just drop by, I will be hanging around the Pine64 booth/table in building AW and the SUNXI dinner on saturday as well as the #HSBXL ByteNight party at the Bruxelles hackerspace... So who else is attending?

I had some problem with DRAM init on my Pine H6 prototype... do you have a serial console log? Did you try to build a Linux image with the old 4.4.x BSP?

RPi is not 'The grandfather of SoCs', if you think that, you are about 10 years late, and it is a good example of how you can still make a good project of obsolete hardware by having enough people buy into the hype...

Just to recap, the only image that works on your board is ayufan's 0.5.15 stable build?

Hi jsfrederick, glad to hear it works for you, I think ayufan did some good progress in that area...

Can you please connect a serial cable (e.g. USB to UART dongle with 3.3V levels) to your debug UART and post the output on pastebin? It is a bit hard to tell without any logs what is going on :-)

I got my PineH6(4) prototype board together with my clusterboard package now, there is also a datasheet available now for AXP805...

I would try and find out what reference design variant your box follows and then provide a dts(i) for it. Can you ask your TV box OEM to provide a schematic, otherwise it doenst make much sense to reverse engineer all the details...

I just booted a mainline kernel on my Rock64 (4.12-rc7 with defconfig, rest was from ayufan's minimal xenial image) and that seems to work ok. Currently investigating a problem with the GMAC0 not finding the PHY, so no network at the moment, but USB2 seems to work, USB3, video and audio drivers are not there yet... Boot log: http://pastebin.ubuntu.com/25206030/ I guess I will try 4.12.4, 4.13-rc2 and rockchip-next as well...

This sounds like a familiar issue I have with my Rock64 sample too, there seems something wrong with the sampling clock for the analog audio codec...

I either use the eMMC adapter that came with one of my ODROIDs or write to the eMMC from a sdcard image. There is also a flash tool from RK that uses USB-OTG via USB A-to-A cable... As for heatsinks, I mounted a small 14x14x14mm sink since I build a lot on my Rock64 and that keeps it from throttling with all four cores running at 1.3Ghz. The RK3328 is implemented with 28nm node, not sure what S905 uses? http://www.fischerelektronik.de/web_fischer/en_GB/heatsinks/B01/Heatsinks for PGA/PR/ICKPGA14x14x14_/index.xhtml

I added some experimental tweaks to my development image to enable HS-200 mode for the eMMC ( was SDR50 before just like the SD card). I will submit a proper patch for ayufan's BSP linux branch during this week. To get HS-200 mode working, there were some clock definitions (looking at you, ciu-sample and drive clocks...) missing and some properties (maximum bus frequency) I had to add to the rk3328.dtsi... but it seems to run stable now... Some iozone results before and after switching SDR50 to HS-200: ---------------- SDR50 --------------------------------------------- random random kB reclen write rewrite read reread read write 512000 4 3430 3554 10964 10472 8152 1614 512000 16 7064 7647 25009 25242 2069 6249 512000 512 10800 11494 41555 43169 42551 10620 512000 1024 11228 11736 42159 43690 43338 10890 512000 16384 11258 11733 44909 44825 44875 11165 ----------------- HS-200 ------------------------------------------- 512000 4 3414 3399 17914 8218 11523 1752 512000 16 9078 9804 56272 56583 39466 7190 512000 512 13173 14054 119128 118530 116335 13008 512000 1024 13816 14607 117665 121782 120387 13429 512000 16384 13814 14662 122756 124242 123471 14007 It seems we are getting close to the 140MB/s read performance the datasheet promises, but 15MB/s is still short of the 35MB/s write performance according to the datasheet, so any hints are welcome here... I would also like some advice on the phase correction loop sublayer in the generic mmc driver, how does one pre calculate the default phase shift?

@r1kaomsk, the 4.4.x BSP kernel tried to store MACs in the GPT vendor partition on the eMMC. ayufan changed that for Rock64 images to the SPI flash since eMMC are removable here...

@Da Alchemist thanks, how did your Z28 die?

@Da Alchemist can you pastebin a dmesg bootlog with Ethernet inserted?

I use either flashcp or nandwrite from the mtd-tools, those can work directly on /dev/mtd0 or partitions..

Can you provide a log from your boot sequence? Do you have a serial console adapter?

Yeah the connectors for USB3-A are tricky. On my old Thinkpad the lower USB3 port which I used a lot more than the upper port enumerates half the time only as high speed instead of super speed because it seems to be worn out, I also noticed some USB3 connectors fit a lot tighter than others... I wonder if there is some low level stats we can pull out of Linux to see USB transmissions errors as an indicator for bad cable connections? Edit: apparently there is this https://wiki.wireshark.org/CaptureSetup/USB