How to upgrade to LEDE? Is it Lite compatible?

rkk
 
Posts: 16
Joined: Sat Jun 17, 2017 11:15 pm

How to upgrade to LEDE? Is it Lite compatible?

Wed Jun 21, 2017 7:18 pm

Hi, as seen in Vonger's post (http://vonger.cn/?p=14237), there is some new LEDE based firmware for the Vocore 2.

I just want to ask how to upgrade my Vocore 2 Lite to the LEDE image. Is that a firmware upgrade image that can be used from System/Firmware Upgrade part in LUCI? Or is it some low-lever system image?

Is it compatible with Vocore 2 Lite? (Is the RAM size and so on right there?)

What is the status of the current LEDE firmware for Vocore? Are there any missing drivers or issues? Any planned updates for the firmware from @Vonger?

Greetings and thanks.

Vonger
 
Posts: 565
Joined: Sun Oct 19, 2014 6:00 am

Re: How to upgrade to LEDE? Is it Lite compatible?

Thu Jun 22, 2017 3:58 pm

Yes, default from current LEDE setting, it is 64MB memory and 8MB flash.
The driver are same 7688 and 7628, just memory and flash size need to be setup.

rkk
 
Posts: 16
Joined: Sat Jun 17, 2017 11:15 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Sat Jun 24, 2017 11:56 am

Nice!! Thanks @Vonger.

rkk
 
Posts: 16
Joined: Sat Jun 17, 2017 11:15 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Mon Jun 26, 2017 5:50 pm

Wow, LEDE seems to be hell unstable. It might be due to the WiFi driver (Which is not the Official driver).

It disconnects frequently saying:
...
[ 551.859784] MCU message 40 (seq 3) timed out
[ 552.859741] MCU message 8 (seq 4) timed out
[ 553.859707] MCU message 40 (seq 5) timed out
[ 554.859669] MCU message 8 (seq 6) timed out
[ 555.859625] MCU message 40 (seq 7) timed out
[ 556.859586] MCU message 8 (seq 8) timed out
[ 557.859550] MCU message 40 (seq 9) timed out
[ 558.859515] MCU message 8 (seq 10) timed out
[ 559.859478] MCU message 40 (seq 11) timed out
[ 560.859440] MCU message 8 (seq 12) timed out
[ 561.859404] MCU message 40 (seq 13) timed out
[ 562.859370] MCU message 8 (seq 14) timed out
[ 563.859325] MCU message 40 (seq 15) timed out
[ 564.859297] MCU message 8 (seq 1) timed out
[ 565.859254] MCU message 40 (seq 2) timed out
[ 566.859216] MCU message 8 (seq 3) timed out
...

It even got some kind of Kernel panic.. but the system continued running, and later connected again to the WiFi.
Here is the stack trace:

[ 543.496493] ------------[ cut here ]------------
[ 543.501314] WARNING: CPU: 0 PID: 64 at /home/buildbot/slave-lede-local/ramips_mt7628/build/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7628/mt76-2017-06-16-70d22512/mt7603_mac.c:1225 mt7603_mac_work+0xf0/0x288 [mt7603e]()
[ 543.521679] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt mt76x2e mt7603e ledtrig_usbport mt76 mac80211 cfg80211 compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables mmc_block mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[ 543.590282] CPU: 0 PID: 64 Comm: kworker/u2:3 Not tainted 4.4.71 #0
[ 543.596654] Workqueue: phy0 mt7603_mac_work [mt7603e]
[ 543.601785] Stack : 83803410 83904a18 00000088 8004ae30 838d2fcc 803b4e23 80350484 00000040
803786d0 838e1d64 803b0000 80048d9c 00000088 8004ae30 80355990 803b0000
00000003 838e1d64 803b0000 80038dac 00000088 838e1d9c 000000b7 00000000
00000001 00000000 8314d268 83b9aa00 83b9a900 30796870 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
[ 543.637937] Call Trace:
[ 543.640438] [<800148e0>] show_stack+0x50/0x84
[ 543.644866] [<80025410>] warn_slowpath_common+0xa0/0xd0
[ 543.650183] [<800254c8>] warn_slowpath_null+0x18/0x24
[ 543.655321] [<8314d358>] mt7603_mac_work+0xf0/0x288 [mt7603e]
[ 543.661182] [<80036cc4>] process_one_work+0x1f8/0x334
[ 543.666314] [<80037ad8>] worker_thread+0x2b0/0x404
[ 543.671191] [<8003be90>] kthread+0xd8/0xec
[ 543.675351] [<80004478>] ret_from_kernel_thread+0x14/0x1c
[ 543.680833]
[ 543.682346] ---[ end trace 8a9125e59af25794 ]---


Anybody can help? @vonger?

Ermanoff
 
Posts: 7
Joined: Tue Jun 27, 2017 9:44 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Sun Jul 02, 2017 6:04 pm

Vonger wrote:Yes, default from current LEDE setting, it is 64MB memory and 8MB flash.
The driver are same 7688 and 7628, just memory and flash size need to be setup.


Where exactly can I set memory and flash size while compiling the system?

Kind regards.

Ermanoff
 
Posts: 7
Joined: Tue Jun 27, 2017 9:44 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Fri Jul 07, 2017 6:52 pm

Ermanoff wrote:
Vonger wrote:Yes, default from current LEDE setting, it is 64MB memory and 8MB flash.
The driver are same 7688 and 7628, just memory and flash size need to be setup.


Where exactly can I set memory and flash size while compiling the system?

Kind regards.


Any tips, guys?

noblepepper
 
Posts: 239
Joined: Sat Nov 29, 2014 3:22 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Fri Jul 07, 2017 9:15 pm

To set ram and flash size you need to build your own image to flash to the vocore. The settings are in the devicetree target/linux/ramips/dts/VOCORE2.dts.

A quick look on my phone shows the prebuilt lede image will have these set for 64M ram and 16M flash.

I have several issues the current dts in the lede repo so I use my own when I want to use lede.

I had very mixed results with the wifi driver in lede, some boards speed is horrible, some it isn't bad. The kernel oops mentioned above seems to have no effect except the barf on console. This only appears when you first configure wifi I have never seen it on subsequent reboots.

Ermanoff
 
Posts: 7
Joined: Tue Jun 27, 2017 9:44 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Sun Jul 09, 2017 1:47 pm

noblepepper wrote:To set ram and flash size you need to build your own image to flash to the vocore. The settings are in the devicetree target/linux/ramips/dts/VOCORE2.dts.

A quick look on my phone shows the prebuilt lede image will have these set for 64M ram and 16M flash.

I have several issues the current dts in the lede repo so I use my own when I want to use lede.

I had very mixed results with the wifi driver in lede, some boards speed is horrible, some it isn't bad. The kernel oops mentioned above seems to have no effect except the barf on console. This only appears when you first configure wifi I have never seen it on subsequent reboots.


Awesome, dude! I tried to understand what section should I change. It's not completely sucessful. Don't you know, If some manuals about it exists?

noblepepper
 
Posts: 239
Joined: Sat Nov 29, 2014 3:22 pm

Re: How to upgrade to LEDE? Is it Lite compatible?

Tue Jul 11, 2017 10:55 pm

You can see an example in my GitHub repo the flash is set in this section
Code: Select all
partition@50000 {
         label = "firmware";
         reg = <0x50000 0xfb0000>;
      };
the format is <start length> so you want 0x50000 + 0xfb0000 to equal the flash size (1000000?)

The ram is set in
Code: Select all
memory@0 {
      device_type = "memory";
      reg = <0x0 0x4000000>;
   };


The newer kernels (like lede uses) autodetect ram so you should be able to just delete that section but one of my boards hit a bug, had problems with nothing but found correct ram size even with wrong values in the devicetree. Leave it as is and run
Code: Select all
free
to see what ram it found.

Return to VoCore2

Who is online

Users browsing this forum: Bing [Bot] and 1 guest