Proof of concept - Realtek 1295

y52 · December 25, 2019

Does somebody know how to implement the following solution ?

https://lkml.org/lkml/2019/7/7/39

Staars · December 29, 2019

On 12/25/2019 at 10:54 PM, y52 said:

Does somebody know who to implement the following solution ?

https://lkml.org/lkml/2019/7/7/39

I can not answer your question, but in the last few weeks there has been a lot of activity on lkml.org regarding the realtek-platform.

Basically „the pro‘s have taken over“ and this is the best thing, that could have happened. I think it is a smart move from realtek to go the „mainline-route“, as it will make their and our lives much easier in the future.

But now we need some patience, because every effort outside of the kernel-development is (IMHO) wasted time.

y52 · December 29, 2019

1 hour ago, Staars said:

every effort outside of the kernel-development is (IMHO) wasted time

I can not but agree.

I've tried several kernel branches for now: mainline, next, legacy BPI-SINOVOIP. In the absence of Realtek's support, accessibility to the board features is very poor. Even basic ethernet NIC's are not operational, even with the legacy BPI-SINOVOIP, which is supposed meeting this basic task. I do not even mention the video Mali T820 support, which is probably far from being thought of.

chewitt · December 30, 2019

Once all the clocking and pin-control and other stuff is done the Mali T820 bit is trivial .. Amlogic S912 (also T820) is now on parity with T860/T760 and other devices using panfrost.

y52 · January 12, 2020

On 12/24/2019 at 10:40 AM, danman said:

Can you try to dump it from u-boot?

My UART cable hasn't arrived yet, it should has been lost on its way to complete the setback with the W2 itself. Meanwhile I have decided sending the BPI-W2 back to the supplier, as no achievement has been made with the broken ethernet and it looks, that nobody interested from the Sinovoip side. Thus I shall not be able dumping mtd. The hardware components are good for different applications, but the absence of drivers and kernel support makes it a handicap.

danman · February 23, 2020

I was sniffing the SPI communication today. It seems to be loading data from address 0x000200 from SPI flash. (those short spikes are glitches in my logic analyzer)

yieexu · March 3, 2020

On 12/29/2019 at 11:30 PM, Staars said:

I can not answer your question, but in the last few weeks there has been a lot of activity on lkml.org regarding the realtek-platform.

Basically „the pro‘s have taken over“ and this is the best thing, that could have happened. I think it is a smart move from realtek to go the „mainline-route“, as it will make their and our lives much easier in the future.

But now we need some patience, because every effort outside of the kernel-development is (IMHO) wasted time.

good job!

hi Staars I have rtd1295 tvbox how install armbian on my tvbox?

UART cable info:

U-Boot 2012.07-g593d2f1-dirty (Sep 01 2016 - 15:39:48)

CPU : Cortex-A7 dual core
Board: Realtek QA Board
DRAM: 1 GiB
Watchdog: Disabled
Cache: Enabled
Non-Cache Region: 1 MB@0x07900000
MMC: rtk_emmc : Detect chip rev. >= B
RTD1195 eMMC: 0
rtk_emmc : Detect chip rev. >= B
mmc->version=0x00010000
version=0x00000004
SDR select (sample/push) : 0x00/0x00
[LY] cardtype=57, mmc->card_caps=0f
[LY] TBD : to support DDR50/HS200
[LY] SDR bus width=2
SDR select (sample/push) : 0x00/0x00
[LY] mmc->boot_caps = 203
[LY] sdr50 : 0
exit from mmc_startup(),err=0
Device: RTD1195 eMMC
Manufacturer ID: 11
OEM: 100
Name: 004GE
Tran Speed: 3197500
Rd Block Len: 512
MMC version 4.0
High Capacity: No
Capacity: 3.7 GiB
Bus Width: 8-bit
Speed: SDR50
Net: Realtek PCIe GBE Family Controller mcfg = 0024
dev->name=r8168#0
167,sw_boot_init
SECURE_BOOT enter!
Cache: Enabled
Non-Cache Region: 1 MB@0x07900000
hardware name = R140B
74,sw_ptable_init
Read Partition ptable,offset = 0,length = 2000,addr=6000000
130,sw_ptentry_read
Read Partition ptable,offset = 200000,length = 2000,addr=6000000
30,sw_mmc_read
offset:200000,lengh=2000,addr=6000000, blk:1000,cnt:10
56,sw_ptable_check
mtd_parts=mtdparts=emmc:2M(loader),2M(ptable),2M(devinfo),2M(misc),16M(logo),24M(recovery),24M(boot),48M(swdb),320M(backup),320M(cache),480M(system),2856M(data)
ptable->cksum=0x298b,count=12
ptn=0   name='loader'   flags=0x0   offset=0x0   size=0x2
ptn=1   name='ptable'   flags=0x0   offset=0x2   size=0x2
ptn=2   name='devinfo'   flags=0x0   offset=0x4   size=0x2
ptn=3   name='misc'   flags=0x0   offset=0x6   size=0x2
ptn=4   name='logo'   flags=0x0   offset=0x8   size=0x10
ptn=5   name='recovery'   flags=0x0   offset=0x18   size=0x18
ptn=6   name='boot'   flags=0x0   offset=0x30   size=0x18
ptn=7   name='swdb'   flags=0x40   offset=0x48   size=0x30
ptn=8   name='backup'   flags=0x40   offset=0x78   size=0x140
ptn=9   name='cache'   flags=0x40   offset=0x1b8   size=0x140
ptn=10   name='system'   flags=0x40   offset=0x2f8   size=0x1e0
ptn=11   name='data'   flags=0x80   offset=0x4d8   size=0xb28

Press 1b Key
Hit Esc or Tab key to enter console mode or rescue linux: 0
Start Boot Setup ...
[ERR] rtk_plat_prepare_fw_image_from_eMMC:Signature() error!
Enter console mode, disable watchdog ...

Realtek>

AaronNGray · August 19, 2020

Hi @Igor

I have a Banana Pi W3 board which now has kernel code for supporting the two Ethernet ports (actually three, one not wired).

https://github.com/BPI-SINOVOIP/BPI-W2-bsp/tree/rtk1296_ow

I am wanting to know if there are any instructions or help available on how to go about :-

a) supporting the BPI W2 A53 CPU

b) integrating the Realtech 1296 Support and possibly all th Realtech chipsets, on the following links

https://github.com/BPI-SINOVOIP/BPI-W2-bsp/tree/rtk1296_ow/linux-rtk/drivers/soc/realtek

https://github.com/BPI-SINOVOIP/BPI-W2-bsp/tree/rtk1296_ow/linux-rtk/drivers/soc/realtek/rtd129x

I am a pretty confident programmer but have not looked at the Linux Kernel properly since v2.4 days and do not know the Armbian framework other than top level image building.

Tido · August 19, 2020

The links mention BSP - board support package - is this code or binaries?

See our get involved documentation on how you can help

AaronNGray · August 19, 2020

16 minutes ago, Tido said:

The links mention BSP - board support package - is this code or binaries?

See our get involved documentation on how you can help

Its a Linux Kernel (4.9 I think) with the new device driver support for the W2 and other BananaPi boards.

Thanks for the link I will read up on it

Igor · August 19, 2020

1 hour ago, AaronNGray said:

I am wanting to know if there are any instructions

If initial board support package (boot loader + kernel + toolchain) is on some decent level, check those examples:

https://github.com/armbian/build/pull/2126

https://github.com/armbian/build/pull/2032

1 hour ago, AaronNGray said:

integrating the Realtech 1296 Support and possibly all th Realtech chipsets, on the following links

HW integration and support is very expensive and we can't afford to sponsor maintenance and support more hardware without expanding team / hire people. Maintaining the code is not exactly something people would stay in the line to get that. Development, playing with toys, contributing here and there, existing, but not near enough to cover everything. Nevertheless, there are people that might be interested to join your efforts ... which is the purpose of this forum. Officially, basic conditions are still at least those:

1 hour ago, AaronNGray said:

I am a pretty confident programmer but have not looked at the Linux Kernel properly since v2.4 days and do not know the Armbian framework other than top level image building.

Kernel tinkering experiences are surely helpful but IHMO in this particular case not enough. (I am not dealing with this particular hardware so I could be wrong) Boot loaders are custom pcs of poorly maintained but very important part of the whole - for each board. Also kernel changed in the term how hardware is configured since the old days ...

Armbian is "just" a tool that helps you put all those things together. Like Yocto or Buildroot, just from a different perspective.

AaronNGray · August 19, 2020

Okay I understand the background issues now so I have either got to wait till SINOVOIP's drivers get into mainline Linux source (which I dont know if that will ever happen judging on what I have seen), or go about integrating the drivers at my end into Armbian, then testing, possibly getting other BananaPi W2 users testing, and then do pull request to you and maybe to appropriate kernel driver maintainer(s).

Is there any documentation on the internals to the Armbian framework at all ?

Oh I had done an issue following your guidlines I was pointer at before the forum topics were merged :- https://github.com/armbian/build/issues/2152

AaronNGray · August 19, 2020

The rtk1296_ow branch works for the main two Ehernet ports on the BPI-W2 according to the BananaPi forum.

https://github.com/BPI-SINOVOIP/BPI-W2-bsp/tree/rtk1296_ow

And obviously the A53. I will look into the kernel changes more and report back here if I find anything more.

Igor · August 20, 2020

7 hours ago, AaronNGray said:

Is there any documentation on the internals to the Armbian framework at all ?

Docs -> Building Armbian

https://docs.armbian.com/Developer-Guide_Build-Preparation/

Building Armbian
Building with Vagrant
Building with Docker
Build Options
User Configurations
FEL boot

is the best we got + already exposed examples. You can find more under https://github.com/armbian/build/pulls?q=is%3Apr+is%3Aclosed

7 hours ago, AaronNGray said:

Okay I understand the background issues now so I have either got to wait till SINOVOIP's drivers get into mainline Linux source

Mainlining is a serious business and can easily takes years to complete (but almost no board gets complete support). There are a few companies that provide such services (with help of community) and vendors have to pay hard cash if they choose to go that path. More complicated and exotic device, more work ... Majority can't afford (or would not gamble) and if community around is too small, all you get is old private development kernel drop.

AaronNGray · August 20, 2020

So there is no way to specify an external kernel like the one in the SINOVoIP BPi W2, rather we have to create patch(es) for the Armbian patch directory ?

I have checked the mainline kernel, kernel mailing list, and found this maining list http://lists.infradead.org/pipermail/linux-realtek-soc/ its only three months old and it looks like all there is now is boot, and probing support so far.

So ot goes down to how long its going to take to wait for support from RealTek or whether I can make up patches from the BPi BSP Kernel code for an Armbian build in the meantime.

Igor · August 20, 2020

43 minutes ago, AaronNGray said:

So there is no way to specify an external kernel like the one in the SINOVoIP BPi W2

Kernels that are not part of the mainline are usually heavily derived from and can contain many incompatible code. Probably it is possible to bring the kernel in and probably somebody already tried that. I would do a wide research before thinking about any coding / porting.

45 minutes ago, AaronNGray said:

and it looks like all there is now is boot

Probably something is, but is it useful?

49 minutes ago, AaronNGray said:

So it goes down to how long its going to take to wait for support from RealTek

You can see how much it was for past few years. It is probably just you. Like I said - there are other people in community that might want to help out when they see things moving.

AaronNGray · August 20, 2020

3 hours ago, Igor said:

Kernels that are not part of the mainline are usually heavily derived from and can contain many incompatible code. Probably it is possible to bring the kernel in and probably somebody already tried that. I would do a wide research before thinking about any coding / porting.

OKay I think I will parallel researching further, with preparing patches and either doing a base level diff's without the prepatched code to see what elese there is in the SINOVoIP code, and searching back through the commits if necessary.

Quote

Probably something is, but is it useful?

I will check whats there against the SINOVoIP code. Not got down to that level yet.

Quote

You can see how much it was for past few years. It is probably just you. Like I said - there are other people in community that might want to help out when they see things moving.

Yeah, I am thinking if I can get the exising BSP Realtek Driver code there and working in Armbian, it will stand as a stop gap until Realtek get there drivers and kernel support there in the Linux Kernel proper.

danman · February 27

Ladies and gentlemen, I managed to boot from SPI on my Zidoo X8:

        Banana Pi BPI-W2(SPI ROM:20180907)

C1:80000000
C2
?
C3h
SD card is not detected !!
BPI: try get_builtin_hwsetting !!

hwsetting size: 00000000
C4
BPI: try bootcode_from_emmc !! 
        BPI: support boot from emmc
switch frequency to 0x00000046
frequency divider is 0x00000080
switch frequency to 0x00000046
frequency divider is 0x00000004
switch to SDR 8 bit
switch bus width to 0x00000008 bits success
Time out 
Time out 
Time out 
End bit error 

BPI: sys_boot_type:1414141490A73F71C7
        Banana Pi BPI-W2(SPI ROM:20180907)

C1:80000000
C2
?uu3-1

All I needed was dump from BPI-W2 SPI flash (attached) which I was asking for serveral times here

In next days, I'll try to boot Linux kernel as described here:

http://forum.banana-pi.org/t/bananapi-w2-ubuntu-18-04-new-image-release-2018-09-17/6790

bpi-w2.bin.short

danman · March 1

From https://drive.google.com/file/d/1kXaI5eYJ4cNLnhfr4rTwUVrENbMc1q-E/view

this shows the addresses in spi flash:

danman · March 3

I need to find out where to put the hwsetting onto SPI and I am not very good with ghidra.

danman · March 4

Until now, I thought that dvrboot.exe.bin is SPI image which is supposed to be directly written to SPI FLASH chip.

But today I discovered it is actually a binary which should be executed on the device to program the SPI chip "in system".

We have sources for this binary here:

https://github.com/BPI-SINOVOIP/BPI-W2-bsp/blob/master/u-boot-rtk/examples/flash_writer/dvrmain.c#L2101

so my next step for creating custom SPI with bootloader for my zidoo X8 is to dissect the locations and create a script to assemble SPI image from all the components which could be directly written to SPI FLASH chip.

JAN27 · May 21

Hello, I just want to inform to anyone that still is going with this project that from here https://www.terra-master.com/code/ you can download the sources of openwrt for rtd1295 (i believe they are complete, with kernel and bootloader sources, and ffmpeg encoder), i found it because i have a wd nas with this chip, and i was trying to bring the video transcode to linux, i failed because my knowledge is limited, but maybe is useful to bring armbian to this board.

Павел Мухатаев · May 29

Hello

I'm trying to run armbian (or any other custom linux) on my NAS TerraMaster F4-210/2G (SoC Realtek RTD1296 based). It has uart connector (the same connector and pins as Zidoo X9S).

So I've created USB stick with Fat32, put uImage and device tree files into it, created another ext2 partition to use as root. Took uImage from banana-pi-w2 just to check things. And used the following command to load my kernel from uboot (there is no b2ndbc command in my uboot):

Realtek> env set bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/sda1 rootfs=vfat
Realtek> usb start && fatload usb 0:1 $kernel_loadaddr uimage && fatload usb 0:1 $fdt_loadaddr tm_f4-210.dtb && env set bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/sda2  rootfs=ext2 init=/bin/bash && bootr
starting USB...
...
reading uimage
10630032 bytes read in 403 ms (25.2 MiB/s)
reading tm_f4-210.dtb
65536 bytes read in 30 ms (2.1 MiB/s)
Start Boot Setup ... 
*** rtkspi_read32_md 422, tar 0x0b000000, src 0x881a0000, len 0x00050000
...
PowerOnOSD~~
[    0.000000] psci: probing for conduit method from DT.

After that original kernel loaded instead of mine.

Then I tried to use bootm - also without any luck

Realtek> usb start && fatload usb 0:1 $kernel_loadaddr uimage && fatload usb 0:1 $fdt_loadaddr tm_f4-210.dtb && env set bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/sda2  rootfs=ext2 init=/bin/bash 
&& bootm $kernel_loadaddr - $fdt_loadaddr
Wrong Image Format for do_booti command
ERROR: can't get kernel image!

I didn't find any documentation on bootr command which stays for `bootr - boot realtek platform`. So my questions are:

is it possible to get info from current stock uboot or devtree or kernel. Or what image type is required by bootm.

uboot load log

uboot help

uboot base, bdinfo, flinfo, printenv, showvar, version

Also in my device-tree I see the following:

chosen {
        bootargs = "rdinit=/sbin/init  mtdparts=RtkSFC:128k(factory),512k(uboot),320k(logo),1408k(afw),64k(dtb),7680k(kernel),5632k(initrd)  earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 loglevel=7";
        linux,initrd-start = <0x2200000>;
        linux,initrd-end = <0x2600000>;
        compatible = "Realtek,rtk1295-cma_info";
        cma-region-enable = <0x01>;
        cma-region-info = <0x00 0x1000000 0x11000000>;
};

memory {
        device_type = "memory";
        reg = <0x00 0x80000000>;
};

mem_remap {
        compatible = "Realtek,rtk1295-mem_remap";
        #address-cells = <0x01>;
        #size-cells = <0x01>;
        ranges;

        rbus {
                reg = <0x98000000 0x200000>;
        };

        common {
                reg = <0x1f000 0x1000>;
        };

        ringbuf {
                reg = <0x1ffe000 0x4000>;
        };
};

Sign In

Proof of concept - Realtek 1295

Recommended Posts

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Join the conversation

Important Information