OpenWrt Forum Archive

Topic: Bootloader/Image for a DLink DWL-2100AP

The content of this topic has been archived between 26 Mar 2018 and 5 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Post #251
chianq
14 May 2008, 03:57

hi,

just stumble on this thread while looking for solution for my problem.

To cut the long story short, I've brick my DWL-2100 while trying to replace the vxwork with redboot (compiled myself).
I've tryied to debrick it by using macraigor usb2demon & OCD Commander (I can't use urjtag or jtag-0.6-cvs because there is no support for USB2demon as far as i know).

however, ocd commander won't work properly unless I've written some init code (macro) to initialize the board first.
Apparently my init code is messedup.. the SDRAM didn't function properly after running the macro file. sad

i'm quite surprise that urjtag/jtag tool do not need any init code to bring the board's sdram into operational state before writing into flash.

anybody can spare some help?

thanks in advance.

Post #252
chianq
15 May 2008, 06:20

I have found the solution, thanks anyway.

Post #254
g_motruk
22 May 2008, 15:36

hi all, i bought 2100ap A4 with S29GL032M flash, flashed redboot and openwrt from ramponis, all works fine!!! but the problem with S29AL032D flash on other A4 is still open... could not make redboot to work with this flash...

Post #255
shera037
23 May 2008, 12:20

Hi all, I have 5 DWL-2100AP rev.A2 can someone post the whole image of his flash with working OpenWRT firmware . Thanks in advance.

Post #257
shera037
24 May 2008, 13:42

Thanks, I instaled the OpenWRT and it`s work good. But where can I see the list of wireless clients on my AP ?

(Last edited by shera037 on 24 May 2008, 13:42)

Post #258
g_motruk
24 May 2008, 16:35

wlanconfig ath0 list

Post #259
L-ZiX
26 May 2008, 07:46

Please help.
After connecting to AP my 2100 write it in console and wireless not work:

br-lan: port 2(ath0) entering disabled state
br-lan: port 2(ath0) entering learning state
br-lan: topology change detected, propagating
br-lan: port 2(ath0) entering forwarding state
br-lan: port 2(ath0) entering disabled state
br-lan: port 2(ath0) entering learning state
br-lan: topology change detected, propagating
br-lan: port 2(ath0) entering forwarding state
br-lan: port 2(ath0) entering disabled state
br-lan: port 2(ath0) entering learning state
br-lan: topology change detected, propagating
br-lan: port 2(ath0) entering forwarding state

Image from ramponis.
How fix this bug?

Post #260
alternative
23 Jun 2008, 15:22

hi people.nice work.just reflashed my 2100 A3 version with redboot(lzma) and then kamikaze 7.09 from ramponis site,
and that works good in ap and client mode(not bridged client).download speed throug ftp is about 1,3-1,6 MB ,that not as origin fw (2,8-3.0MB) but its not bad.now i think it possible to use pppoe connection.(try this later)I'd like to know, how to make power led work. many thanks.

Post #261
lp0cua0
27 Jul 2008, 13:03

I'm not much of a coder, but I do have a little information on _maybe_ making this a serial only upgrade.

Login to your routers CLI.
type alpha
password is sdd21234
now, type set supermode
now, type bootrom

I have no clue what the 'mips format filed' it wants, boot seems like it might be possible to put a small
loader in the original boot area, and either load redboot from 'main' flash, or use it during the next boot
to update flash partitions, etc during the next boot.

BTW, once supermode is enabled, superftp <desktop pc ip> will allow you to grab any file you like into the flash,
tfp or not.

After enabling supermode, check the 'new' help command list.
What _is_ an HAD file?

Post #262
omegatotal
31 Aug 2008, 18:12

so i have a dwl-2100a HWrev a2, i thought it might have been bricked, turns out the flash decided to erase it self or has become corrupted

ar531x rev 0x00005850 firmware startup...
SDRAM TEST...PASSED

  WAP-G02A  Boot Procedure                       V1.0                                                     
---------------------------------------------------------                                                         
  Start ..Boot.B12..Please check the ethernet cable on port 1                                                             

Atheros AR5001AP default version 3.0.0.43A                                          


 0  
auto-booting...               

Attaching to TFFS... done.                          
Loading /fl/APIMG1...                     

  Please wait, loading  image ...                                 

  image check fail!!!                     


error loading file: status = 0x3d0001.

Error loading RUNTIME file: errno = 0xd0003.
Loading /fl/backup...

  Please wait, loading  image ...

  image check fail!!!


error loading file: status = 0xd0003.

Error loading BACKUP file: errno = 0xd0003.
Can't load boot file!!

... and repeat

this was via serial, i wanted to know how i should go about re-flashing this router back with a dlink fw, and which one i could/should flash it with, im trying to do this with what i have on hand, *serial cable, network, windows/linux*

(Last edited by omegatotal on 31 Aug 2008, 18:14)

Post #263
omegatotal
2 Sep 2008, 00:45

bump? i need the elf file i can tftp for a stock firmware if possible, or a method to get the stock firmware back on this unit, there could be paypal money involved if it works

Post #266
heruan
13 Sep 2008, 13:56

Is there any trick to flash redboot without jtag? I have no jtag or solder sad
The original bootloader wants a TFP image format, why OpenWRT can't build one of this kind?

Post #267
omegatotal
14 Sep 2008, 03:46

so i tried running the commands from the pdf file (even tho i couldn't read 99% of the file) these are basically the same commands i have seen elsewhere

i still cannot copy anything via tftp/ftp to the router, all i can do is 

$ae(1,0)pc:/flash/art h=192.168.0.1 e=192.168.0.2:0xffffff00 f=0x80

which gets me to the art console, but after endering all the commands i cant get any files to the AP

Post #268
antoxa
16 Mar 2009, 11:47

Hi All!
sorry for my english.

I have DWL-2100 AP Rev. A4
I have made Serial cable with 3 pins from my Siemens data cable.
I have compiled my own kernel with RAMdisk from kamikaze svn.
Ok, kernel booting from tftp and all works fine.

ar531x rev 0x00005850 firmware startup...
SDRAM TEST...PASSED



  WAP-G02A  Boot Procedure                       V1.0
---------------------------------------------------------
  Start ..Boot.B14..

theros AR5001AP default version 3.0.0.43A


 1
[Boot]: p

boot device          : ae
unit number          : 1
processor number     : 0
file name            : vmlinux.elf
inet on ethernet (e) : 172.16.0.198:ffffff00
host inet (h)        : 172.16.0.2
flags (f)            : 0x80
other (o)            : ae
[Boot]: @
Attached TCP/IP interface to ae1.
Attaching network interface lo0... done.
Loading... 4653936
Starting at 0x80200130...

Linux version 2.6.26.8 (antoxa@antoxa) (gcc version 4.1.2) #1 Mon Mar 16 14:37:54 ALMT 2009
CPU revision is: 0001800a (MIPS 4Kc)
Determined physical RAM map:

.....

inside OpenWRT

antoxa@antoxa:~$ telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------


BusyBox v1.11.3 (2009-03-16 13:24:01 ALMT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r14892) -------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@OpenWrt:/#

I want to make OpenWRT permanent OS for DWL-2100.
I suppose, what I must change boot loader?
Can I use redboot image (BootLoader Redboot Sperimentale per il 2100AP Rev. A4. (NOT TESTED! USE AT YOUR RISK!)) from http://xoomer.virgilio.it/ramponis/Pages/flash.htm ?
How I can program flash without WIGGLER cable?
After that how I can program flash with my kernel?

Thank You.

Post #269
bitbucket
16 Mar 2009, 12:00
antoxa wrote:

I want to make OpenWRT permanent OS for DWL-2100.

All information about openwrt build for 2100ap on wiki http://wiki.openwrt.org/OpenWrtDocs/Har … DWL-2100AP

First, you must have a jtag cable in case of a reflashing failure. If you have it, and it works - you can try to flash a bootloader , make 'fis init' and some other magic actions (flash kernel, rootfs) . Openwrt works on DWL2100AP A.4.

Post #270
antoxa
16 Mar 2009, 13:47
bitbucket wrote:
antoxa wrote:

I want to make OpenWRT permanent OS for DWL-2100.

All information about openwrt build for 2100ap on wiki http://wiki.openwrt.org/OpenWrtDocs/Har … DWL-2100AP

First, you must have a jtag cable in case of a reflashing failure. If you have it, and it works - you can try to flash a bootloader , make 'fis init' and some other magic actions (flash kernel, rootfs) . Openwrt works on DWL2100AP A.4.

Do I must change bootloader?
Where I can try this command 'fis init'? In standart bootloader?
I have tried load redboot.elf from tftp but I got this error

Attached TCP/IP interface to ae1.
Attaching network interface lo0... done.
Loading... 103392
Error loading file: errno = 0x610007.
Can't load boot file!!
Post #271
omegatotal
16 Mar 2009, 18:48

can you post your .elf so i can try it on my dwl-2100ap?

Post #272
antoxa
17 Mar 2009, 04:29
omegatotal wrote:

can you post your .elf so i can try it on my dwl-2100ap?

This file I have downloaded from site http://xoomer.virgilio.it/ramponis/Pages/flash.htm
Link to file http://xoomer.alice.it/ramponis/firmwar … mental.rar
Also I can't build my own redboot from this archive http://www.dm.ufscar.br/profs/waldeck/ecos-2.0.tar.bz2
I assume, that I need redboot RAM file for boot through tftp and ROM file to write into flash.
ELF openwrt, that I have build from kamikaze-svn, boots through tftp fine.
What do I need to do after that?
Write kernel to flash?
Please see below output when I build redboot. I use Debian Lenny as my OS.

source ecosenv.sh
./gen_platform
Choose a plaform by selecting from the list below:
   1) ap30
   2) ap33
   3) ap38
   4) ap43
   5) ap48
   6) ap51
   7) GENERATE NEW PLATFORM
 Your choice --> 6
ap51
U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
make -r -C hal/mips/arch/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/arch/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/arch/v2_0'
make -r -C hal/mips/mips32/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/mips32/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/mips32/v2_0'
make -r -C hal/mips/ar5312/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/ar5312/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/ar5312/v2_0'
make -r -C hal/mips/ap51/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/ap51/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/ap51/v2_0'
make -r -C devs/eth/mips/ar531x/current headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/devs/eth/mips/ar531x/current'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/devs/eth/mips/ar531x/current'
make -r -C hal/common/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/hal/common/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/hal/common/v2_0'
make -r -C infra/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/infra/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/infra/v2_0'
make -r -C redboot/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/redboot/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/redboot/v2_0'
make -r -C isoinfra/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/isoinfra/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/isoinfra/v2_0'
make -r -C language/c/libc/string/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/language/c/libc/string/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/language/c/libc/string/v2_0'
make -r -C net/ns/dns/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/net/ns/dns/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/net/ns/dns/v2_0'
make -r -C services/crc/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/services/crc/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/services/crc/v2_0'
make -r -C services/memalloc/common/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/services/memalloc/common/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/services/memalloc/common/v2_0'
make -r -C services/compress/zlib/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/services/compress/zlib/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/services/compress/zlib/v2_0'
make -r -C io/eth/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/io/eth/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/io/eth/v2_0'
make -r -C io/fileio/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/io/fileio/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/io/fileio/v2_0'
make -r -C io/flash/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/io/flash/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/io/flash/v2_0'
make -r -C io/common/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/io/common/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/io/common/v2_0'
make -r -C error/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/error/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/error/v2_0'
make -r -C compat/linux/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/compat/linux/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/compat/linux/v2_0'
make -r -C kernel/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/kernel/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/kernel/v2_0'
make -r -C devs/flash/cfi/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/devs/flash/cfi/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/devs/flash/cfi/v2_0'
headers finished
make -r -C hal/mips/ap51/v2_0 /home/antoxa/eCos/build.RAM_ap51/install/include/cyg/hal/plf_defs.inc
make[1]: Entering directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/ap51/v2_0'
mipsisa32-elf-gcc -mips32 -EB -msoft-float -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -G0 -mlong-calls  -I/home/antoxa/eCos/build.RAM_ap51/install/include -I/home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0 -I/home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0/src -I/home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0/tests -I. -Wp,-MD,plf_defs.tmp -o plf_mk_defs.tmp -S /home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0/src/plf_mk_defs.c
fgrep .equ plf_mk_defs.tmp | sed s/#// > /home/antoxa/eCos/build.RAM_ap51/install/include/cyg/hal/plf_defs.inc
tail: cannot open `+2' for reading: No such file or directory
make[1]: *** [/home/antoxa/eCos/build.RAM_ap51/install/include/cyg/hal/plf_defs.inc] Error 1
make[1]: Leaving directory `/home/antoxa/eCos/build.RAM_ap51/hal/mips/ap51/v2_0'
make: *** [build] Error 2
U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
make -r -C hal/mips/arch/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/arch/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/arch/v2_0'
make -r -C hal/mips/mips32/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/mips32/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/mips32/v2_0'
make -r -C hal/mips/ar5312/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ar5312/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ar5312/v2_0'
make -r -C hal/mips/ap51/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ap51/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ap51/v2_0'
make -r -C devs/eth/mips/ar531x/current headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/devs/eth/mips/ar531x/current'
make[1]: Nothing to be done for `headers'.
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/devs/eth/mips/ar531x/current'
make -r -C hal/common/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/hal/common/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/common/v2_0'
make -r -C infra/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/infra/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/infra/v2_0'
make -r -C redboot/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/redboot/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/redboot/v2_0'
make -r -C isoinfra/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/isoinfra/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/isoinfra/v2_0'
make -r -C language/c/libc/string/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/language/c/libc/string/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/language/c/libc/string/v2_0'
make -r -C net/ns/dns/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/net/ns/dns/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/net/ns/dns/v2_0'
make -r -C services/crc/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/services/crc/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/services/crc/v2_0'
make -r -C services/memalloc/common/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/services/memalloc/common/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/services/memalloc/common/v2_0'
make -r -C services/compress/zlib/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/services/compress/zlib/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/services/compress/zlib/v2_0'
make -r -C io/eth/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/io/eth/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/io/eth/v2_0'
make -r -C io/fileio/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/io/fileio/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/io/fileio/v2_0'
make -r -C io/flash/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/io/flash/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/io/flash/v2_0'
make -r -C io/common/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/io/common/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/io/common/v2_0'
make -r -C error/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/error/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/error/v2_0'
make -r -C compat/linux/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/compat/linux/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/compat/linux/v2_0'
make -r -C kernel/v2_0 headers
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/kernel/v2_0'
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/kernel/v2_0'
headers finished
make -r -C hal/mips/ap51/v2_0 /home/antoxa/eCos/build.ROM_ap51/install/include/cyg/hal/plf_defs.inc
make[1]: Entering directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ap51/v2_0'
mipsisa32-elf-gcc -mips32 -EB -msoft-float -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -G0 -mlong-calls  -I/home/antoxa/eCos/build.ROM_ap51/install/include -I/home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0 -I/home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0/src -I/home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0/tests -I. -Wp,-MD,plf_defs.tmp -o plf_mk_defs.tmp -S /home/antoxa/eCos/ecos-2.0/packages/hal/mips/ap51/v2_0/src/plf_mk_defs.c
fgrep .equ plf_mk_defs.tmp | sed s/#// > /home/antoxa/eCos/build.ROM_ap51/install/include/cyg/hal/plf_defs.inc
tail: cannot open `+2' for reading: No such file or directory
make[1]: *** [/home/antoxa/eCos/build.ROM_ap51/install/include/cyg/hal/plf_defs.inc] Error 1
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ap51/v2_0'
make: *** [build] Error 2
./gen_platform: line 154: cd: install/bin: No such file or directory
mipsisa32-elf-objcopy: redboot.elf: No such file or directory
Post #273
antoxa
17 Mar 2009, 13:30
antoxa wrote:
omegatotal wrote:

can you post your .elf so i can try it on my dwl-2100ap?

This file I have downloaded from site http://xoomer.virgilio.it/ramponis/Pages/flash.htm
Link to file http://xoomer.alice.it/ramponis/firmwar … mental.rar
Also I can't build my own redboot from this archive http://www.dm.ufscar.br/profs/waldeck/ecos-2.0.tar.bz2
I assume, that I need redboot RAM file for boot through tftp and ROM file to write into flash.
ELF openwrt, that I have build from kamikaze-svn, boots through tftp fine.
What do I need to do after that?
Write kernel to flash?
Please see below output when I build redboot. I use Debian Lenny as my OS.

source ecosenv.sh
./gen_platform
tail: cannot open `+2' for reading: No such file or directory
make[1]: *** [/home/antoxa/eCos/build.ROM_ap51/install/include/cyg/hal/plf_defs.inc] Error 1
make[1]: Leaving directory `/home/antoxa/eCos/build.ROM_ap51/hal/mips/ap51/v2_0'
make: *** [build] Error 2
./gen_platform: line 154: cd: install/bin: No such file or directory
mipsisa32-elf-objcopy: redboot.elf: No such file or directory

I have tried to build redboot RAM by hand from this message http://forum.openwrt.org/viewtopic.php?pid=50311#p50311
It works.
I have modified gen_platform script and build all of the available platform.
They are booting through tftp, but don't work sad

ar531x rev 0x00005850 firmware startup...
SDRAM TEST...PASSED



  WAP-G02A  Boot Procedure                       V1.0
---------------------------------------------------------
  Start ..Boot.B14..

Atheros AR5001AP default version 3.0.0.43A


 0
auto-booting...

Attached TCP/IP interface to ae1.
Attaching network interface lo0... done.
Loading... 367216
Starting at 0x80010000...

+
RedBoot startup
FLASH: driver init failed: Driver does not support device
FLASH: driver init failed: Driver does not support device
Ethernet eth0: MAC address 00:21:91:88:81:ed
IP: 0.0.0.0/255.255.255.0, Gateway: 0.0.0.0
Default server: 0.0.0.0, DNS server IP: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [RAM]
Non-certified release, version v2_0 - built 18:22:19, Mar 17 2009
With changes made by Waldeck Schutzer <waldeck@dm.ufscar.br>


Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x80010000-0x81000000, 0x80069a70-0x80ff4000 available
RedBoot>

at this point bootloader don't answer for console input.
Only after power cycle reset I can modify standart bootloader parameters.
I think there is unknown flash installed on my DWL-2100.
Please help me.

Post #274
antoxa
17 Mar 2009, 13:40

Flash on my DWL-2100 board is marked as S29AL032D90TFI04 (c)04 SPANSION

Post #275
bitbucket
17 Mar 2009, 21:24
antoxa wrote:

Flash on my DWL-2100 board is marked as S29AL032D90TFI04 (c)04 SPANSION

You can add support for your flash IC in RedBoot (described on wiki), or try to use a bootloader from this http://xoomer.virgilio.it/ramponis/Pages/flash.htm page. If you have working JTAG cable - you can't brick the device. You need firmware with lzma decompression.