OpenWrt Forum Archive

Topic: How to compile the OpenWRT for ARM Architecture?

The content of this topic has been archived on 20 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Dear All,

I am new to OpenWRT. I followed the http://wiki.openwrt.org/doc/howto/build link to download and build the OpenWRT. I downloaded OpenWRT backfire successfully. However, I did not find the ARM in the "Target System" menu after running the "make menuconfig" from backfire folder.

Please any one can let me know, how can I get the ARM in the "Target System" menu after running make menuconfig. Am I missing any configurations, here?

Any help would be appreciated.

Thanks and Regards,
Madhavi M.

Dear All,

Does OpenWRT supports the ARM architecture? If does not, how can I build the images for ARM architecture? Is there any documentation for building the images for ARM?

Thanks and Regards,
Madhavi M

Thanks atlaware.

Those images are already build. Is it possible to build our own OpenWRT images based on ARM architecture? If there is any documentation or link, please let me know.

Thanks and Regards,
Madhavi M.

Well are you aware of the Seagate docstar, I believe it' s ARM then again quite  a lot of marvel chips around are ARM too they are supported on openwrt.
search them in the menuconfig and try to compile it on your linux box.

The ARM core is only part of a system-on-chip (SoC). AFAIK at least these SoC contain an ARM core and are supported by OpenWRT in the trunk (menuconfig -> "Target System"):

- Intel IXP4xx
- Marvell Kirkwood, Orion
- Marvell/Intel PXA2xx

Madhavi M wrote:

Thanks atlaware.

Those images are already build. Is it possible to build our own OpenWRT images based on ARM architecture? If there is any documentation or link, please let me know.

Thanks and Regards,
Madhavi M.

there the istruction for build OpenWRT for ARM:

http://wiki.openwrt.org/toh/seagate/doc … e.dockstar

atlaware wrote:
Madhavi M wrote:

Thanks atlaware.

Those images are already build. Is it possible to build our own OpenWRT images based on ARM architecture? If there is any documentation or link, please let me know.

Thanks and Regards,
Madhavi M.

there the istruction for build OpenWRT for ARM:

http://wiki.openwrt.org/toh/seagate/doc … e.dockstar

Hi atlaware,

Thanks for the link.

I want to build the OpenWRT image for my Samsung s3c24xx processor which is ARM based. I am not able to see the Samsung s3c24xx as Target System or Target Profile.

I followed the following steps for generating the OpenWRT image for my Samsung s3c24xx processor.

1) make menuconfig
    selected the "Intel IXP4XX" as Target System.
    selected the "Default Profile" as Target Profile.
    Selected the default boot loader "apex". We are able to see onlt this boot loader.

2) make V=99
    This step build the different types of images in bin directory. However, I need the image for Samsung. So, I followed the #3, below.

3) make kernel_menuconfig
    selected the ARM System Type (Samsung s3c24xx...) as System type.

When I save and exit, I am getting "error: '__LINUX_ARM_ARCH__' undeclared " error.

Here my question is, is my #3 is correct for selecting the Samsung processor as I am NOT able to see it in #1?

How can I build the openwrt images for my Samsung s3c2xxx processor?

Any help would be appreciated and help me a lot.

Thanks and Regards,
Madhavi M.

Hi, Madhavi M.

Get trunk buildroot and make menuconfig.
You can find "Samsung S3C24xx".

Good luck!

zukky

yapoo wrote:

Hi, Madhavi M.

Get trunk buildroot and make menuconfig.
You can find "Samsung S3C24xx".

Good luck!

zukky

Hi Zukky,

Thanks for your useful information.

I checked out the trunk and able to see Samsung S3C24XX in the Target System options. Previously I checked out the backfire.

Thanks once again.

Regards,
Madhavi M.

yapoo wrote:

Hi, Madhavi M.

Get trunk buildroot and make menuconfig.
You can find "Samsung S3C24xx".

Good luck!

zukky

Hi Zukky,

Thanks for your help.

I checked out the trunk and build the images for the Samsung S3C24XX target system. I found only two image files under bin directory one is kernel image (uImage) and another one is root file system (jffs2). I did not find the boot loader file.

Please let me know, if there is any documentation/link/procedure for loading/installing the images on to Samsung S3C24XX target device.

Please help me. I am new to this environment. Any help would be appreciated.

Thanks and Regards,
Madhavi M.

Hi, Madhavi M.

What board/device are you about to install? Isn't any bootloader installed on your device?

When s3c24xxx is seleced, nothing is selectable in "make menuconfig" -> "Boot Loaders". But, for example, when "Target System" -> "Marvell Kirkwood" is selected, you can find bootloader selection under "Boot Loaders".
So if you need bootloader, you need to modify or add makefile about them by yourself. About u-boot, you can find example in /your/dir/to/trunk/package
About target specific files, you can find them in /your/dir/to/trunk/target/linux/s3c24xx

Good luck!

zukky

yapoo wrote:

Hi, Madhavi M.

What board/device are you about to install? Isn't any bootloader installed on your device?

When s3c24xxx is seleced, nothing is selectable in "make menuconfig" -> "Boot Loaders". But, for example, when "Target System" -> "Marvell Kirkwood" is selected, you can find bootloader selection under "Boot Loaders".
So if you need bootloader, you need to modify or add makefile about them by yourself. About u-boot, you can find example in /your/dir/to/trunk/package
About target specific files, you can find them in /your/dir/to/trunk/target/linux/s3c24xx

Good luck!

zukky

Hi Zukky,

Thanks for your information.

I will let you know the deatails about the board once I receive the permisson from my higher authority. The board is up and running fine with a different OS, currently. So, there is a boot loader installed.

As per my understand, there are two options. 1) with the existing boot loader 2) without the boot loader.

In case of #1, we need only kernel image file and root file system.
In case of #2, we need boot loader along with the kenerl image and root file system.

If I want to do as per #2, then I will need to modify the Makefile in the trunk/ sources as you said for building the boot loader. If I want to do as per #1, then I will need to modify the existing boot loader sources for loading my OpenWRT images.

Please let me know whether my assumptions are correct or not. If the questions are very silly, execume me as I am learning the concepts, now.

Thanks and Regards,
Madhavi M.

Madhavi M wrote:
yapoo wrote:

Hi, Madhavi M.

What board/device are you about to install? Isn't any bootloader installed on your device?

When s3c24xxx is seleced, nothing is selectable in "make menuconfig" -> "Boot Loaders". But, for example, when "Target System" -> "Marvell Kirkwood" is selected, you can find bootloader selection under "Boot Loaders".
So if you need bootloader, you need to modify or add makefile about them by yourself. About u-boot, you can find example in /your/dir/to/trunk/package
About target specific files, you can find them in /your/dir/to/trunk/target/linux/s3c24xx

Good luck!

zukky

Hi Zukky,

Thanks for your information.

I will let you know the deatails about the board once I receive the permisson from my higher authority. The board is up and running fine with a different OS, currently. So, there is a boot loader installed.

As per my understand, there are two options. 1) with the existing boot loader 2) without the boot loader.

In case of #1, we need only kernel image file and root file system.
In case of #2, we need boot loader along with the kenerl image and root file system.

If I want to do as per #2, then I will need to modify the Makefile in the trunk/ sources as you said for building the boot loader. If I want to do as per #1, then I will need to modify the existing boot loader sources for loading my OpenWRT images.

Please let me know whether my assumptions are correct or not. If the questions are very silly, execume me as I am learning the concepts, now.

Thanks and Regards,
Madhavi M.

Hi Zukky,

The existing boot loader is not working currently. That was broken when I try to load the OpenWRT image on the device flash through a J-Link JTAG. Now, the board is not working.

So, I want to load the OpenWRT into the board and run the OpenWRT on it. I guess, now I need the boot loader. Am I correct?

One silly question, what type of image is "openwrt-s3c24xx-openmoko-gta02-2.6-uImage". Is it a .bin format or .elf format or .out format? However, I heard that it is a uImage format? Is this correct?

Thanks and Regards,
Madhavi M.

atlaware wrote:
Madhavi M wrote:

Thanks atlaware.

Those images are already build. Is it possible to build our own OpenWRT images based on ARM architecture? If there is any documentation or link, please let me know.

Thanks and Regards,
Madhavi M.

there the istruction for build OpenWRT for ARM:

http://wiki.openwrt.org/toh/seagate/doc … e.dockstar

why i can't entry the URL link " http://wiki.openwrt.org/toh/seagate/doc … e.dockstar "?

who can entry the link and send the detail to my email : lishuliang8888@163.com.

Any help would be appreciated !

Thanks and Regards!

byxlk

byxlk wrote:

why i can't entry the URL link " http://wiki.openwrt.org/toh/seagate/doc … e.dockstar "?

who can entry the link and send the detail to my email : lishuliang8888@163.com.

I don't know what you meant, but I have no problem to access to the above link to browse its contents.

Huawei EC1309V2
IP Set-Top-Box
Bootloader:                     U-Boot 2008.10-svn (May 23 2011 - 21:18:32)
Nand:                             128MB   :-D
Ram:                              64MB
USB:                               2 Ports
Rj45:                              1 Pport

Is it possible to somehow install openwrt in it??

Bootlog

NAND:  128 MiB


U-Boot 2008.10-svn (May 23 2011 - 21:18:32)

DRAM:  64 MB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
MAC address invalid!
Set Random MAC address: 46:FD:19:68:0E:47
boot linux kernel now : bootf vmlinux.bin
Press CTRL-C to abort autoboot in First boot loader Booting 2th loader to mem : form 20000 to mem c2000000 ....
nand_mem_cp off= 20000,size = 262144,addr = c2000000
## Starting application at 0xC2000000 ...
NAND:  128 MiB


U-Boot 2008.10-svn (Oct 14 2011 - 19:04:48)

DRAM:  64 MB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
MAC address invalid!
Set Random MAC address: 8A:52:41:1B:EF:A2
boot linux kernel now : bootf vmlinux.bin
Press CTRL-C to abort autoboot in 1 seconds
boot flag : 0
logo flag : 0
show logo 3300000 262144
0   720    576
TDE_MAIN_VERSION[TDE_MAIN_VERSION] Build Time[Oct 14 2011, 19:04:57]
TDE_ADP_VERSION[TDE_ADP_VERSION] Build Time[Oct 14 2011, 19:04:57]
Booting kernel  load data to mem : form 100000 to mem c2000000 ....
nand_mem_cp off= 100000,size = 1572864,addr = c2000000
## Booting kernel from Legacy Image at c2000000 ...
   Image Name:   Linux-2.6.14-hi3560v200-release
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1057648 Bytes =  1 MB
   Load Address: c0800000
   Entry Point:  c0800000
   Loading Kernel Image ... OK
OK
app flag : 1
*Start check appinfo 3 0 0 0 *
UBoot starting ... mem=80M console=ttyAMA0,115200 root=/dev/mtdblock8 rootfstype=yaffs2  mmz=ddr,2,0xF50M,48M  fes=128 nand_partitions=v2&&0:0:1024&1:0:8&2:8:16&3:24:384&4:408:8&5:416:8&6:424:8&7:432:16&8:448:384&9:832:8&10:840:8&11:848:8&12:856:168 tmem=128M

Starting kernel ...

Uncompressing Linux...................................................................... done, booting the kernel.
Linux version 2.6.14-hi3560v200-release (lijulong@lijulong-ThinkPad-SL410) (gcc version 3.4.3 (release) (CodeSourcery ARM Q1B 2005)) #10 PREEMPT Mon Jun 20 10:31:34 CST 2011
CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
Machine: Hi3560v200
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists
Kernel command line: mem=80M console=ttyAMA0,115200 root=/dev/mtdblock8 rootfstype=yaffs2  mmz=ddr,2,0xF50M,48M  fes=128 nand_partitions=v2&&0:0:1024&1:0:8&2:8:16&3:24:384&4:408:8&5:416:8&6:424:8&7:432:16&8:448:384&9:832:8&10:840:8&11:848:8&12:856:168 tmem=128M
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 80MB = 80MB total
Memory: 78848KB available (1806K code, 354K data, 76K init)
Mount-cache hash table entries: 512
HI_VERSION=LINUX_2_6_14-M01C04FB02F @hi3560v200_0_0_0_3 2009-10-28 11:24:28
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Hisilicon clock system V0.01
NetWinder Floating Point Emulator V0.97 (double precision)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
yaffs Jun 20 2011 10:28:26 Installing.
Initializing Cryptographic API
Serial: AMBA PL011 UART driver
ttyAMA0 at MMIO 0x101ea000 (irq = 10) is a AMBA/PL011
ttyAMA1 at MMIO 0x101eb000 (irq = 11) is a AMBA/PL011
io scheduler noop registered
io scheduler deadline registered
RAMDISK driver initialized: 4 RAM disks of 8192K size 1024 blocksize
physmap flash device: 2000000 at 34000000
flash jedec_probe failed
nand extid 0x1d
NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (Unknown NAND 128MiB 3,3V 8-bit)
 partition name: whole; partition offset: 0; partition size: 134217728
 partition name: loader; partition offset: 0; partition size: 1048576
 partition name: boot1; partition offset: 1048576; partition size: 2097152
 partition name: app1; partition offset: 3145728; partition size: 50331648
 partition name: logo1; partition offset: 53477376; partition size: 1048576
 partition name: param1; partition offset: 54525952; partition size: 1048576
 partition name: playlist1; partition offset: 55574528; partition size: 1048576
 partition name: boot2; partition offset: 56623104; partition size: 2097152
 partition name: app2; partition offset: 58720256; partition size: 50331648
 partition name: logo2; partition offset: 109051904; partition size: 1048576
 partition name: param2; partition offset: 110100480; partition size: 1048576
 partition name: playlist2; partition offset: 111149056; partition size: 1048576
 partition name: swfs; partition offset: 112197632; partition size: 22020096
Creating 13 MTD partitions on "hinand":
0x00000000-0x08000000 : "whole"
0x00000000-0x00100000 : "loader"
0x00100000-0x00300000 : "boot1"
0x00300000-0x03300000 : "app1"
0x03300000-0x03400000 : "logo1"
0x03400000-0x03500000 : "param1"
0x03500000-0x03600000 : "playlist1"
0x03600000-0x03800000 : "boot2"
0x03800000-0x06800000 : "app2"
0x06800000-0x06900000 : "logo2"
0x06900000-0x06a00000 : "param2"
0x06a00000-0x06b00000 : "playlist2"
0x06b00000-0x08000000 : "swfs"
oprofile: using timer interrupt.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 2
yaffs: dev is 32505864 name is "mtdblock8"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.8, "mtdblock8"
VFS: Mounted root (yaffs2 filesystem).
Mounted devfs on /dev
Freeing init memory: 76K
vm.overcommit_memory = 1
vm.overcommit_ratio = 100
net.unix.max_dgram_qlen = 200
net.ipv4.tcp_rmem = 4096 200000 2500000

            _ _ _ _ _ _ _ _ _ _ _ _
            \  _  _   _  _ _ ___
            / /__/ \ |_/
           / __   /  -  _ ___
          / /  / /  / /
  _ _ _ _/ /  /  \_/  \_ ______
___________\___\__________________

Checking for boardip ...
Generic PHY: Registered new driver
Hisilicon ETH net controler(ver Oct 28 2009 11:30:09).
Hisilicon ETH MDIO Bus: probed
Invalid HW-MAC Address: 00:00:00:00:00:00
Set Random MAC address: 5E:6B:B3:98:4F:86
0:03 not found
hieth:/home/shared/SDKs/Hi3560E/sdk/source/drv/sfv300/net-drv.c:833: connect to phy_device 0:03 failed!
DMAC-MF @hi3560v200_0_0_0_3 2009-10-28 11:30:12
Hisilicon Media Memory Zone Manager
hiir: init ok. ver=Oct 28 2009, 11:30:15.
select i2c0 and i2c1
JPEG Driver Init Success.
TDE_MAIN_VERSION[v2.0.0.0] Build Time[Oct 28 2009, 11:31:32]
TDE_ADP_VERSION[hi3560 adp v2.0.0.0] Build Time[Oct 28 2009, 11:31:32]
hi3560E: module license 'Copyright(c)' taints kernel.
DRV3560E_init
Hisilicon UMAP device driver interface: v1.00
msp_debug device init successful!
g_VdiDbgPhyAddr = 0xc5003000
DRV3560E_init ok
insert EPL successful!
hifb info: HIFB_MAIN_VERSION[HIFB_MAIN_VERSION] Build Time[Jul 13 2011, 15:18:29]
hifb info: video:vram0_size:5242880,vram1_size:5242880
hifb info: succeed in registering the fb0: ovl0 frame buffer device
hifb info: succeed in registering the fb1: ovl1 frame buffer device
NET: Registered protocol family 17
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
NET: Registered protocol family 24
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbir
usbcore: registered new driver usbserial
/home/shared/SDKs/Hi3560E/sdk/source/os/linux-2.6.14/drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
/home/shared/SDKs/Hi3560E/sdk/source/os/linux-2.6.14/drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
ohci-hi3560v200 ohci-hi3560v200.0: ohci-hi3560v200
ohci-hi3560v200 ohci-hi3560v200.0: new USB bus registered, assigned bus number 1
ohci-hi3560v200 ohci-hi3560v200.0: irq 21, io mem 0x90050000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub 1-0:1.0: over-current change on port 1
ehci-hi3560v200 ehci-hi3560v200.0: ehci-hi3560v200
ehci-hi3560v200 ehci-hi3560v200.0: new USB bus registered, assigned bus number 2
ehci-hi3560v200 ehci-hi3560v200.0: irq 7, io mem 0x90060000
ehci-hi3560v200 ehci-hi3560v200.0: park 0
ehci-hi3560v200 ehci-hi3560v200.0: USB 0.0 initialized, EHCI 1.00, driver hi3560v200
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
rtusb init --->
usbcore: registered new driver rt2870
yaffs: dev is 32505868 name is "mtdblock<"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.12, "mtdblock<"
yaffs: MTD device does not support have the right page sizes
yaffs: dev is 32505868 name is "mtdblock<"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.12, "mtdblock<"
yaffs: restored from checkpoint
[0]MediaPlayerJSExtImpl.cpp  210 excute MediaPlayerJSImpl
OSD_WIDTH:720   OSD_HEIGHT:576  MEM_SIZE:26214400

Boot version: 84125060
Built at Jan_11_2014__18:19:04

sw_gpio_init
pinctrl
GPIO_GROUP_4
Init GPIO OK!
UpdatePtTable nand 8000000
[510]Partition loader , 0 , 100000
[510]Partition boot1 , 100000 , 200000
[510]Partition app1 , 300000 , 3000000
[510]Partition logo1 , 3300000 , 100000
[510]Partition param1 , 3400000 , 100000
[510]Partition playlist1 , 3500000 , 100000
[510]Partition boot2 , 3600000 , 200000
[510]Partition app2 , 3800000 , 3000000
[510]Partition logo2 , 6800000 , 100000
[510]Partition param2 , 6900000 , 100000
[510]Partition playlist2 , 6a00000 , 100000
[510]Partition swfs , 6b00000 , 1500000
Init partition OK!


Init flash ...
E2PROM Repeat init
HI_UNF_E2PROM_Open fails:0xa0378001
[540]Thread-<tParaSaveProc : 0 : 6a9718> opened
sw_partition_get_size param1
sw_partition_get_size 11param1:param1
[730]sw_flash_dev_read from 0x3400000 to 0x3500000
[900]sw_flash_dev_read finish  0xfffff  badblock=0
[910][reset_stbid] STBID not need to set
Init param OK!

Init screen ...
ERROR: can not open msp_debug device.
.. OK


HiGo Ver:1.0.1.2 a40
This versihifb info: The layer is show(1) now!
on is building at Jul  9 2011 14:37:07

HiGo 3560E ADP Ver:1.0.1.2 a40
This version is building at Jul  9 2011 14:37:08
[1080]sw_flash_dev_read from 0x3300000 to 0x3400000
[1130]sw_flash_dev_read finish  0x40000  badblock=0
GIF decode ok
[sw_parameter_get_int] lValue=1
[value] value=84125060
sw_network_set_mac:ifconfig eth0 hw ether 00:07:63:99:9c:7c
sw_ir_init->307
[1620]Thread-<tIRProc : 1 : 6ab658> opened
[1620]Thread-<tIRLed : 2 : 6ab6f0> opened
sw_ir_set_trans_callback->287
[1630]Thread-<swshell : 3 : 6ab790> opened
[1630]Thread-<swshell2 : 4 : 6ab810> opened
Sunniwell shell,(c) 2007 sunniwell.
==================================
>sw_network_connect pppoe
sw_network_set_mac:ifconfig eth0 hw ether 00:07:63:99:9c:7c
[1710]sw_network_init GLB_FWCTRL old value 20
[1720]sw_network_init GLB_FWCTRL new value 530
[1720]sw_network_init GLB_MACTCTRL old value 20
[1720]sw_network_init GLB_MACTCTRL  new value 95b5
ifconfig eth0 up still continue wait 1
ifconfig eth0 up still continue wait 2
ifconfig eth0 up still continue wait 3
ifconfig eth0 up still continue wait 4
ifconfig eth0 up still continue wait 5
ifconfig eth0 up still continue wait 6
ifconfig eth0 up still continue wait 7
ifconfig eth0 up still continue wait 8
ifconfig eth0 up still continue wait 9
ifconfig eth0 up still continue wait 10
ifconfig eth0 up still continue wait 11
ifconfig eth0 up still continue wait 12
ifconfig eth0 up still continue wait 13
ifconfig eth0 up still continue wait 14
ifconfig eth0 up still continue wait 15
ifconfig eth0 up still continue wait 16
ifconfig eth0 up still continue wait 17
ifconfig eth0 up still continue wait 18
ifconfig eth0 up still continue wait 19
ifconfig eth0 up still continue wait 20
ifconfig eth0 up still continue wait 21
ifconfig eth0 up still continue wait 22
ifconfig eth0 up still continue wait 23
ifconfig eth0 up still continue wait 24
ifconfig eth0 up still continue wait 25
ifconfig eth0 up still continue wait 26
ifconfig eth0 up still continue wait 27
ifconfig eth0 up still continue wait 28
ifconfig eth0 up still continue wait 29
ifconfig eth0 up still continue wait 30
ifconfig eth0 up still continue wait 31
ifconfig eth0 up still continue wait 32
ifconfig eth0 up still continue wait 33
ifconfig eth0 up still continue wait 34
ifconfig eth0 up still continue wait 35
ifconfig eth0 up still continue wait 36
ifconfig eth0 up still continue wait 37
ifconfig eth0 up still continue wait 38
ifconfig eth0 up still continue wait 39
ifconfig eth0 up still continue wait 40
ifconfig eth0 up still continue wait 41
ifconfig eth0 up still continue wait 42
ifconfig eth0 up still continue wait 43
ifconfig eth0 up still continue wait 44
ifconfig eth0 up still continue wait 45
ifconfig eth0 up still continue wait 46
ifconfig eth0 up still continue wait 47
ifconfig eth0 up still continue wait 48
ifconfig eth0 up still continue wait 49
ifconfig eth0 up still continue wait 50
ifconfig eth0 up still continue wait 51
ifconfig eth0 up still continue wait 52
ifconfig eth0 up still continue wait 53
ifconfig eth0 up still continue wait 54
ifconfig eth0 up still continue wait 55
ifconfig eth0 up still continue wait 56
ifconfig eth0 up still continue wait 57
ifconfig eth0 up still continue wait 58
ifconfig eth0 up still continue wait 59
ifconfig eth0 up still continue wait 60
mac:00:07:63:99:9c:7c 0:7:63:99:9C:7c
last pppoe session id = 15110
send padt size = 60
cmd: pppd eth0 user 6303092000 password 12345
[PPPD]: pppd eth0 user 6303092000 password 12345
options_from_file /etc/ppp/options
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
options_from_file /tmp/.ppprc
open options file failed must_exist=0
options_from_file /etc/ppp/options.eth0
open options file failed must_exist=0
Warning: couldn't open ppp database /var/run/pppd2.tdb

>

http://s27.postimg.org/hnwcq2sn7/Aqv_P96j_OQN82_B_d_NCob0_ALy_Bj7y_It_XAKu_KTq1zn0x_PRS.jpg
http://s27.postimg.org/d5ynbq1z7/Airtz_K6z_Bfh1r_ZShs_VBs_EZz_Tju_XSSDO8y_GAKFTd_H2_Hf_E.jpg
http://s27.postimg.org/qt4pjxw1v/Ajni_Ui6aby1_Bi9ij0v_RVn_Eyzl_MH_fk92_Ske_Wt_B4_D0_HB.jpg
http://s27.postimg.org/ofmrsxhmr/Atqyqj_O93_KWPx0_HAs_WBR4_NKc_DNbg_MBl_Wv_z_Lp9_WBdal.jpg
http://s27.postimg.org/8p1ozaydf/Ai_b_Dr_Xzuf_Rrk_Fd_EVOCNZFGa9c_SJw_Qq_Jzs8r_Zc_Ci_WQ83.jpg

(Last edited by Shahid on 4 Nov 2015, 00:26)

Some one plz??????????????
At least tell me at which address i should try to write firmware image???
i dnt want to brick this little buddy's u-boot
Developers kindly look into boot log and tell me what to erase and where to write.
Thanks in advance

The discussion might have continued from here.