New to the forum

return0

Hi, it would be helpful to know what board you're working on - even if the SoC is exactly the same (RK3288) there might be substantial differences between the Firefly hardware and yours.

Is the LAN interface pre-built on the board you have or you added it (e.g. USB-LAN)? Have you tried asking the manufacturer directly?

Hard to say how to solve your problem without more details however, the flashing procedure should be very similar to the Firefly given that the RK3288 uses the same tools across multiple boards.

http://wiki.t-firefly.com/index.php/Firefly-RK3288/Flash_image/en

return0

Hi, do you have the resource.img file? If yes could you post it here?

The patch you pointed to (https://bitbucket.org/T-Firefly/ ... 09b6e49325613e137ed) is part of the kernel device-tree: this basically tells the kernel what kind of hardware you have on the board and a lot more parameters/configurations regarding the SoC (RK3288) itself.

The resource.img file does contain the DT but simply editing that file might/might not work - worst case you'd have to re-compile your kernel so my second question is, do you have the kernel sources for your board?

It should come together with the SDK provided by the manufacturer - probably that zip archive contains everything you need. Is there a /kernel directory in there?

Check out this answer for details on how to unpack your resource.img -> http://bbs.t-firefly.com/forum.p ... &highlight=boot

return0

biomecanoid Posted at 7/7/2015 16:23
Any hints on how i can continue will be highly appreciated

The file BluetimesQpro-plus-rk3288-_AP6330_public_20150207.img is probably a firmware update for your hardware which contains all the images such as resource.img, system.img etc.

You need to extract that .img file to find out what's in there exactly - you can refer to this wiki page: http://wiki.t-firefly.com/index. ... android_firmware/en

Once you have your resource.img image to work on, you should be able to modify the device tree as you wish.

return0

biomecanoid Posted at 7/8/2015 19:12
I decompiled the dtb file to dts

http://wikisend.com/download/520154/devicetree.dts.txt

Hi, great you may try to change the rx_delay to 0x10 leaving the tx_delay as it is - see this patch: http://lists.infradead.org/piper ... January/002282.html

Regarding the MAC address I am not entirely sure your syntax will work - I do it like this:

1. mac-address = [ 00 e0 ee 02 05 2e ];

Copy the code

Likely white spaces won't matter really, but up to you!

I do suggest that you first try to solve your LAN speed issues, then work on the MAC ADDR at a second stage once the rest of the problems are gone - just my 2 cents!

return0

biomecanoid Posted at 7/8/2015 20:35
Hi,

OK you have been right so far so i will trust you.

Hi, yes you can flash only the resource.img file using the Rockchip tools - keep a backup of the original file, which as you figured will be handy in case something goes wrong (simply re-flash it).

The userdata partition is not erased unless you do it manually so your data will remain safe!

Your DTS already matches the patch you want to apply:

1.         eth@ff290000 {
   
2.                 compatible = "rockchip,rk3288-gmac";
   
3.                 reg = <0xff290000 0x10000>;
   
4.                 interrupts = <0x0 0x1b 0x4>;
   
5.                 interrupt-names = "macirq";
   
6.                 clocks = <0x67 0x79 0x0 0x79 0x1 0x79 0x2 0x79 0x3 0x7b 0x0 0x7b 0x1>;
   
7.                 clock-names = "clk_mac", "mac_clk_rx", "mac_clk_tx", "clk_mac_ref", "clk_mac_refout", "aclk_mac", "pclk_mac";
   
8.                 phy-mode = "rgmii";
   
9.                 pinctrl-names = "default";
   
10.                 pinctrl-0 = <0xe6 0xe7 0xe8 0xe9>;
    
11.                 reset-gpio = <0x5 0x8 0x1>;
    
12.                 clock_in_out = "input";
    
13.                 tx_delay = <0x30>;
    
14.                 rx_delay = <0x20>;
    
15.         };

Copy the code

So if that's the fix (https://bitbucket.org/T-Firefly/ ... 09b6e49325613e137ed) then you actually don't need to do anything.

Can I ask how you came to the conclusion that your ethernet is slow? Are you 100% confident that it's not a problem in your LAN?

You mentioned:

My only problem is the very slow LAN and WiFi which is on a 10mbps level with trasfer so low as 1MB/s

LAN and WiFi are two completely differnet things in terms of hardware architecture - I struggle to believe that both have exactly the same issue unless the problem is within your network or the OS.

Also for the record, 1MB/s (megabyte, not megabit in this case) is actually not a bad speed at all if you're talking about a download from the Internet.

As you can see, WiFi has its own individual DTS node which would not be affected by whatever you change in the ethernet node:

1.         wireless-wlan {
   
2.                 compatible = "wlan-platdata";
   
3.                 wifi_chip_type = "bcmwifi";
   
4.                 sdio_vref = <0x708>;
   
5.                 power_pmu_regulator = "act_ldo3";
   
6.                 power_pmu_enable_level = <0x1>;
   
7.                 vref_pmu_regulator = "act_ldo3";
   
8.                 vref_pmu_enable_level = <0x1>;
   
9.                 WIFI,poweren_gpio = <0x5 0x1c 0x0>;
   
10.                 WIFI,host_wake_irq = <0x5 0x1e 0x0>;
    
11.                 status = "okay";
    
12.         };

Copy the code

What is the WiFi connection speed that you see when connected to your usual access point? What about ethernet?