Hi All! At first I want to say that all of you made excellent work!
Apparently this have taken hours and lots and lots of hard time ....
Thank You ..

We will describe our Demand briefly..
we have like 1000 (one thousand) Dwl2100 aps operating in an outdoor network infrastructure,
All in WDS mode, each machine have up to 8 other machines connected to it; not to forget some aps repeating to others.

So it started small and now its a bit very tricky to maintain such size network.

We already started a network consisted of Mikrotik RouterBoards, Base Side and clients side.
But the problem is that :
We are looking to establish a parallel network, keeping all the exisiting clients CPEs.
So we need to make the DWL2100AP Works with ROuterBoard in WDS mode, ( AP client mode gives only one client after it) 

We are using firmware version: 2.01.eu-r137 with regulatory domain off and ovverridetxpower ...   

Is there any one that is interested in providing Support 1 us step by step configuration for the dwl2100,
We are looking for a solution and support. (Even Commercial One... if any anyone have the solution will pay for it...)

Thank You in advance and looking Forward to Hear From You ASAP..

Hi,

Can anyone (ANTOXA?) please post a link to a compiled vmlinux image (kernel with RAMdisk from kamikaze svn) that can be loaded from the original bootloader via tftp (not redboot) ?
If possible, also post your tftp loadable redboot.

thanks.

In RB.7z you will find redboot with LZMA & S29AL032D support (only this flash chip) and slightly OC CPU (220 MHz) in ROM and RAM variants.
http://narod.ru/disk/15900141000/RB.7z.html
Soon will add firmware.

Waiting your firmware

Still have no time to finish FW. Have not yet solved problems with Madwifi (open full power on <2412). If somebody knows how:)... You are welcome:)

Hi mans!
amnesis:
  dwl-2100ap + RedBoot
preambule:
  load -b 0x80041000 openwrt-atheros-vmlinux.elf => crash
  otherwise
  load -r -b 0x80041000 openwrt-atheros-vmlinux.lzma
  fis create -r 0x80041000 linux
  fis load -l linux
  exec => linux loaded ,,,
ambule:
  how i  do to boot .elf image of linux-kernel , it is possible?

vladimir-its, try
load openwrt-atheros-vmlinux.elf or (if crashed) load -b 0x80041000 openwrt-atheros-vmlinux.elf
go
For size reducing LZMA decomp works only when loading from fis.

Hi there
I found in this thread how to revive my 2100ap. I almost revived it but now I'm stuck.
My ap was completely dead, it was always rebooting but very quickly and I wasn’t able to get in serial console so I made a full flash with a jtag cable and I was able get the web interface. I tried to upgrade to the last version but it didn’t go well and could only communicate with the ap by telnet.
So, I followed the Ramponi manual and I tried to upgrade the ap via tftp and ftp. Everything went well in the upgrade but the ap still cannot start.
It has a watchdog error…

Atheros AR5001AP default version 3.0.0.43A
 0
auto-booting...
Attaching to TFFS... done.
Loading /fl/apimg1...
Please wait, loading  image ..
  image check ok!!!
NMI (watchdog): ErrorPC: 0x800c2fd4
      epc: 0x800c3a08 bva: 0x7fffff84 sr:  0x1048c006 cse: 0x1080c00c
  R0: r0:  0x00000000 at:  0x00080000 v0:  0x800c3a04 v1:  0x1000c000
  R4: a0:  0x00000017 a1:  0x80000010 a2:  0x80000038 a3:  0x00008000
  R8: t0:  0x00000000 t1:  0x00000007 t2:  0xffffffff t3:  0x00000038
 R12: t4:  0x802fbdfc t5:  0x802fbda0 t6:  0x802fbe04 t7:  0x802fbe24
 R16: s0:  0x10000000 s1:  0x00000017 s2:  0x80000148 s3:  0x80000170
 R20: s4:  0x00000046 s5:  0x00000000 s6:  0x00000000 s7:  0x00000000
 R24: t8:  0xbe000000 t9:  0x00000000 k0:  0x00000000 k1:  0x00000000
 R28: gp:  0x802df210 sp:  0x7fffff98 fp:  0x80ff5da8 ra:  0x800c3118
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...
Attaching to TFFS... done.
Loading /fl/apimg1...
  Please wait, loading  image ...
  image check ok!!!
NMI (watchdog): ErrorPC: 0x800c2fd4
      epc: 0x800c3a08 bva: 0x7fffff84 sr:  0x1048c006 cse: 0x1080c00c
  R0: r0:  0x00000000 at:  0x00080000 v0:  0x800c3a04 v1:  0x1000c000
  R4: a0:  0x00000017 a1:  0x80000010 a2:  0x80000038 a3:  0x00008000
  R8: t0:  0x00000000 t1:  0x00000007 t2:  0xffffffff t3:  0x00000038
 R12: t4:  0x802fbdfc t5:  0x802fbda0 t6:  0x802fbe04 t7:  0x802fbe24
 R16: s0:  0x10000000 s1:  0x00000017 s2:  0x80000148 s3:  0x80000170
 R20: s4:  0x00000046 s5:  0x00000000 s6:  0x00000000 s7:  0x00000000
 R24: t8:  0xbe000000 t9:  0x00000000 k0:  0x00000000 k1:  0x00000000
 R28: gp:  0x802df210 sp:  0x7fffff98 fp:  0x80ff5da8 ra:  0x800c3118

What can i do?

Hi there

question to ramponis: What is the right way to compile kernel and madwifi for DWL-2100AP from latest trunk?

When i compile using 'make menuconfig' i chose target Ateros AR231x/AR5312. Then after flashing i get this at boot:

Please HELP!!!

What is the correct version of gcc?

hi,
Somebody can tell me what last revision boot successfully on DLink 2100AP ?

@reiter, ramponis

Hi!

I'am noob with DWL-2100, if possible, can you please explain how to change from stock to openwrt firmware having only serial interface attached to?

Thanks!

(Last edited by vpritiskovic on 16 Oct 2010, 17:08)

Sorry for not reply so long - I have no time for that. I will add some instructions.

I need that instructions too please.

Finally I found some time ...:)
In order to flash Redboot ROM version to the built-in flash to do the following:
1. Run something like http://smallsrv.com/ on host pc, put redboot220.img into www dir.
2. Run terminal (9600 8 N 1).
3. Plug your's 2100 and press ESC until you are prompted to [boot] in terminal window.
4. Send "p". Remember or write all lines from terminal output (to restore if needed), then  change settings:

boot device                   : ae1
unit number                  : 0
processor number         : 0
file name                      : /www/redboot220.img
inet on ethernet (e)       : 192.168.1.50:ffffff00
host inet (h)                  : 192.168.1.10
gateway inet (g)            :
flags (f)                         : 0x80
other (o)                       : ae

Where "inet on ethernet (e)       : 192.168.1.50:ffffff00" - AP address
And    "host inet (h)                  : 192.168.1.10" - host PC address (where http and ftpd servers will be located).

5. Reboot AP, redboot RAM version have to load, next - run tftpd32 (with redboot_ROM.bin in home directory) on the host pc.
6. Flash redboot ROM with next commands:
fis init -f
load -r -b %{FREEMEMLO} redboot_ROM.bin
fis create RedBoot
7. Reboot AP, redboot ROM version have to load.
Next - flash openwrt, run, enjoy:)

Tnx Reiter!

Please confirm if the 'redboot220.img' from 'http://narod.ru/disk/15900141000/RB.7z.html' is the right one, and please give us link to 'redboot_ROM.bin' file.
Do we need lzma support in bootloader?

Tnx agin!

Edit:

I have Atmel flash chip so I am not sure what file do I need?

(Last edited by vpritiskovic on 10 Nov 2010, 17:30)

vpritiskovic, that loader for S29AL032D ONLY! With LZMA support when loading from flash (only) - for size optimization.

Ok, have found som spare time and succeded to intsall redboot into Atmel flash! Great work!!!

RedBoot startup
Ethernet eth0: MAC address 00:0f:3d:af:eb:05
IP: 192.168.0.50/255.255.255.0, Gateway: 192.168.0.1
Default server: 192.168.0.10, DNS server IP: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version v2_0 - built 16:27:48, Jul  1 2007
With changes made by Waldeck Schutzer <waldeck@dm.ufscar.br>


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

RAM: 0x80000400-0x81000000, 0x80000400-0x807d1ce0 available
FLASH: 0xbfc00000 - 0xbffe0000, 62 blocks of 0x00010000 bytes each.
== Executing boot script in 5.000 seconds - enter ^C to abort
^C
RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xBFC00000  0xBFC00000  0x00030000  0x00000000
RedBoot config    0xBFFC0000  0xBFFC0000  0x00001000  0x00000000
FIS directory     0xBFFD0000  0xBFFD0000  0x00010000  0x00000000
vmlinux           0xBFC30000  0x80041000  0x000D0000  0x80041000
rootfs            0xBFD00000  0x80041000  0x001C0000  0x00000000

For those who need a backfire build for this AP i have done some testing.

If you need to compile trunk with default toolchain and kernel 2.6.32.26 - kernel hangs...
Solution for this issue when compiling trunk with default toolchain is to use kernel 2.6.33.7 or 2.6.34.7.
Resulting firmwares are booting normal.

Hi guys.
Im writing here becouse i become a owner of that small AP.
i would like to change software permanetly to OpenWRT

Inside my box i found Atmel FLASH so im not sure its supported (rev A2 of the device).
Vpritiskovic wrote sth about  successfull redboot flashing on that Atmel chip but he didnt add any file or additional info..
So if somone could help i would be greatfull

Regards
Bander

(Last edited by p1vo on 30 Apr 2011, 17:42)

https://forum.openwrt.org/viewtopic.php … 25#p134325

Argh its too late
I kiled it.
I mange to install redboot but had some issues with free space:

RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xBE000000  0xBE000000  0x00050000  0x00000000
RedBoot config    0xBE3C0000  0xBE3C0000  0x00001000  0x00000000
FIS directory     0xBE3D0000  0xBE3D0000  0x00010000  0x00000000

fis free
  0xBE030000 .. 0xBE050000

After that i tried to flash redboot once more time nad i killed my device..
Curently im struggling with jtag: it works but i cannot write to the flash (i can read it, erase but no write)
so anyone who knows what is the issue pls help.

tjtag just hang:

Probing bus ... Done

Instruction Length set to 5

CPU Chip ID: 00000000000000000000000000000001 (00000001)
*** Found a Atheros AR531X/231X CPU chip ***

    - EJTAG IMPCODE ....... : 01000000010000000100000000000000 (40404000)
    - EJTAG Version ....... : 2.6
    - EJTAG DMA Support ... : No
    - EJTAG Implementation flags: R4k ASID_8 NoDMA MIPS32
    *** DMA Mode Forced Off ***

Issuing Processor / Peripheral Reset ... Done
Enabling Memory Writes ... Skipped
Halting Processor ... <Processor Entered Debug Mode!> ... Done
Clearing Watchdog ... Done

Enabling Atheros Flash Read/Write ... Done

.RE-Probing Atheros processor....
Probing Flash at (Flash Window: 0x1fc00000) ...
Done

Flash Vendor ID: 00000000000000000000000000011111 (0000001F)
Flash Device ID: 00000000000000000000000011001000 (000000C8)
*** Found a AT49BV322A 2Mx16 BotB      (4MB) Flash Chip ***

    - Flash Chip Window Start .... : 1fc00000
    - Flash Chip Window Length ... : 00400000
    - Selected Area Start ........ : 1fc00000
    - Selected Area Length ....... : 00040000

*** You Selected to Flash the CFE.BIN ***

=========================
Flashing Routine Started
=========================
Total Blocks to Erase: 11

Erasing block: 1 (addr = 1fc00000)...Done
Erasing block: 2 (addr = 1fc02000)...Done
Erasing block: 3 (addr = 1fc04000)...Done
Erasing block: 4 (addr = 1fc06000)...Done
Erasing block: 5 (addr = 1fc08000)...Done
Erasing block: 6 (addr = 1fc0a000)...Done
Erasing block: 7 (addr = 1fc0c000)...Done
Erasing block: 8 (addr = 1fc0e000)...Done
Erasing block: 9 (addr = 1fc10000)...Done
Erasing block: 10 (addr = 1fc20000)...Done
Erasing block: 11 (addr = 1fc30000)...Done

Loading CFE.BIN to Flash Memory...

im giving up on it...
i have problem with jtag - cant write anything on the orginal Atmel flash... its funny becuse i soldered AMD AM29LV320DB Flash (with redboot on it but the device didnt start) and guess what.. yes i can. So im confused. it seems that tjtag has problem with Atmel flash. However the case is that i need wholeflash image (can be orgianal firmware or openwrt). so if anyone can aid me i would be gratefull.

A question regarding ramcheck's post:
      https://forum.openwrt.org/viewtopic.php … 609#p61609

What I did was:

cd ~/redboot_download_from_openwrt/
wget http://downloads.openwrt.org/reference/redboot.tar.bz2
wget http://www.dm.ufscar.br/profs/waldeck/redboot.ramcheck.diff
Save 'eCos configuration file' part of the post to file dwl-2100ap.ecc
tar jxf redboot.tar.bz2
sudo chown -R user: redboot
sudo chmod -R a+w redboot
cd redboot/
patch -p1 < ../redboot.ramcheck.diff
find . -type f | xargs perl -i -pe 's/tail \+2/tail -n +2/g'

Edit 'gen_platform' like this:
--- redboot/gen_platform    2011-08-29 14:39:53.000000000 +0800
+++ redboot-new/gen_platform    2011-08-29 14:38:24.000000000 +0800
@@ -138,6 +138,7 @@
 cd build.RAM_$AP
 ecosconfig new atheros_$AP redboot
 ecosconfig import $ECOS_REPOSITORY/hal/mips/$AP/v2_0/misc/redboot_RAM.ecm
+ecosconfig import /home/user/redboot_download_from_openwrt/dwl-2100ap.ecc
 ecosconfig tree
 make

Then run ./gen_platform and select 'ap51'

It fails to build.

ramcheck, please help

P.S. Is there any work still in progress with redboot ? It would be great to have the current patches published somewhere.

EDIT:

SOLVED

Instead of gen_platform above use this:

#!/bin/bash
AP="ap51"
. ./ecosenv.sh
mkdir buildROM_$AP
cd buildROM_$AP
ecosconfig new atheros_$AP redboot
ecosconfig import $ECOS_REPOSITORY/hal/mips/$AP/v2_0/misc/redboot_ROM.ecm
ecosconfig import /home/user/redboot_download_from_openwrt/dwl-2100ap.ecc
ecosconfig tree
make
cd install/bin
mipsisa32-elf-objcopy -O binary redboot.elf redboot.rom

(Last edited by ivan8 on 2 Sep 2011, 06:42)

I successfully built the patched redboot.
The problem was that in gen_platform both ram and rom images were built.
If ram part removed - all is ok.