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.

ivan8 wrote:

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.

You could update the wiki and put the redboot loader for that flash chip too, for all others users, so they don't have to go all the way you did!

Well, actually I just built it. It's not working right:


+                                                                     
RedBoot startup                                                                 
FLASH: driver init failed: Driver does not support device                       
FLASH: driver init failed: Driver does not support device                       
Ethernet eth0: MAC address 14:d6:4d:53:d0:e7                                   
IP: 192.168.0.50/255.255.255.0, Gateway: 192.168.0.1                           
Default server: 0.0.0.0, DNS server IP: 0.0.0.0                                 
                                                                               
RedBoot(tm) bootstrap and debug environment [ROM]                               
Non-certified release, version v2_0 - built 16:46:07, Aug 30 2011               
With changes made by Waldeck Schutzer <waldeck@dm.ufscar.br>                   
                                                                               
                                                                               
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.                                   
                                                                               
RAM: 0x80000400-0x81000000, 0x80000400-0x807e4ce0 available                     
RedBoot> fis list                                                               
FLASH: driver init failed: Driver does not support device                       
Sorry, no FLASH memory is available                                             
RedBoot> fis init -f                                                           
FLASH: driver init failed: Driver does not support device                       
Sorry, no FLASH memory is available                                             
RedBoot>

SOLVED

The problem was with device id detection. Hardcoding solved the problem.

diff -ur redboot/ecos-2.0/packages/devs/flash/amd/am29xxxxx/v2_0/include/flash_am29xxxxx.inl redboot-new//ecos-2.0/packages/devs/flash/amd/am29xxxxx/v2_0/include/flash_am29xxxxx.inl
--- redboot/ecos-2.0/packages/devs/flash/amd/am29xxxxx/v2_0/include/flash_am29xxxxx.inl    2011-09-02 09:27:55.000000000 +0800
+++ redboot-new//ecos-2.0/packages/devs/flash/amd/am29xxxxx/v2_0/include/flash_am29xxxxx.inl    2011-09-02 09:31:12.000000000 +0800
@@ -155,8 +155,28 @@
 } flash_dev_info_t;
 
 static const flash_dev_info_t* flash_dev_info;
+#define _LAST_BOOTBLOCK (-1)
 static const flash_dev_info_t supported_devices[] = {
-#include <cyg/io/flash_am29xxxxx_parts.inl>
+    {   // AM29LV320D
+        device_id  : FLASHWORD(0xF9),
+        block_size : 0x10000 * CYGNUM_FLASH_INTERLEAVE,
+        block_count: 64,
+        device_size: 0x400000 * CYGNUM_FLASH_INTERLEAVE,
+        base_mask  : ~(0x400000 * CYGNUM_FLASH_INTERLEAVE - 1),
+        bootblock  : true,
+        bootblocks : { 0x000000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       0x002000 * CYGNUM_FLASH_INTERLEAVE,
+                       _LAST_BOOTBLOCK
+                     },
+        banked     : false
+    },
 };
 #define NUM_DEVICES (sizeof(supported_devices)/sizeof(flash_dev_info_t))
 
@@ -240,7 +260,7 @@
 flash_hwr_init(void)
 {
     flash_data_t id[4];
-    int i;
+//    int i;
 
     CYGHWR_FLASH_AM29XXXXX_PLF_INIT();
 
@@ -248,6 +268,7 @@
 
     // Look through table for device data
     flash_dev_info = supported_devices;
+/*
     for (i = 0; i < NUM_DEVICES; i++) {
         if (!flash_dev_info->long_device_id && flash_dev_info->device_id == id[1])
             break;
@@ -261,7 +282,7 @@
     // Did we find the device? If not, return error.
     if (NUM_DEVICES == i)
         return FLASH_ERR_DRV_WRONG_PART;
-
+*/
     // Hard wired for now
     flash_info.block_size = flash_dev_info->block_size;
     flash_info.blocks = flash_dev_info->block_count * CYGNUM_FLASH_SERIES;

Hello.Please help me !I get this message when I am using jtag :

a@a-d10547ac3a8a4 ~
$ jtag
JTAG Tools 0.6-cvs-20051228
Copyright (C) 2002, 2003 ETC s.r.o.
JTAG Tools is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for JTAG Tools.

Warning: JTAG Tools may damage your hardware! Type "quit" to exit!

Type "help" for help.

jtag> include athsw
Initializing Macraigor Wiggler JTAG Cable on parallel port at 0x378
IR length: 5
Chain length: 1
Device Id: 00000000000000000000000000000001
  Manufacturer: Atheros
  Part:         ar2312
  Stepping:     1
  Filename:     /usr/local/share/jtag/atheros/ar2312/ar2312
ImpCode=01000000010000000100000000000000
EJTAG version: 2.6
EJTAG Implementation flags: R4k ASID_8 NoDMA MIPS32
dev ID=005b   man ID=00c2
Using CFI flash chip detection, not jedec
Flash not found!
No. Manufacturer              Part                 Stepping Instruction
  Register
--------------------------------------------------------------------------------
-------------
   0 Atheros                   ar2312               1        EJTAG_DATA
  EJDATA

Active bus:
*0: EJTAG compatible bus driver via PrAcc (JTAG part No. 0)
        start: 0x00000000, length: 0x20000000, data width: 8 bit
        start: 0x20000000, length: 0x20000000, data width: 16 bit
        start: 0x40000000, length: 0x20000000, data width: 32 bit
jtag>

The id's are for Macronix MX29LV800BTC-90. Can anybody help me to fix this problem?It is easy to add this flash in the list of the flashes?Thank you very much.

Hello.I have the same situation like Ramponis. Only I do not have a Atmel flash ,I have a Macronix flash MX29LV800 which is identical with SST 39LF800 and ST M29W800. Can I get some instructions on how to make jtag detect and work with mu flash? The output of the jtag is :


a@a-d10547ac3a8a4 ~
$ jtag
JTAG Tools 0.6-cvs-20051228
Copyright (C) 2002, 2003 ETC s.r.o.
JTAG Tools is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for JTAG Tools.

Warning: JTAG Tools may damage your hardware! Type "quit" to exit!

Type "help" for help.

jtag> include athsw
Initializing Macraigor Wiggler JTAG Cable on parallel port at 0x378
IR length: 5
Chain length: 1
Device Id: 00000000000000000000000000000001
  Manufacturer: Atheros
  Part:         ar2312
  Stepping:     1
  Filename:     /usr/local/share/jtag/atheros/ar2312/ar2312
ImpCode=01000000010000000100000000000000
EJTAG version: 2.6
EJTAG Implementation flags: R4k ASID_8 NoDMA MIPS32
dev ID=005b   man ID=00c2
Using CFI flash chip detection, not jedec
Flash not found!
No. Manufacturer              Part                 Stepping Instruction
  Register
--------------------------------------------------------------------------------
-------------
   0 Atheros                   ar2312               1        EJTAG_DATA
  EJDATA

Active bus:
*0: EJTAG compatible bus driver via PrAcc (JTAG part No. 0)
        start: 0x00000000, length: 0x20000000, data width: 8 bit
        start: 0x20000000, length: 0x20000000, data width: 16 bit
        start: 0x40000000, length: 0x20000000, data width: 32 bit
jtag>

As you can see the manufacturer ID is 00c2 - Macronix and dev ID is 005b - MX29LV800.I am very close to fix my bootloader.Thank you.

Here i wrote a detailed step-by-step guide on installing OpenWRT on d-link dwl2100-ap rev a4 router using serial

P1vo Don't give up!

You are right TJTAG is the problem. But not because of the Atmel AT49BV322A flash.
The problem is that TJTAG does not read/write properly to the Atheros ar2313A MIPS CPU because it's bus is 8 bit.

I now use jtag-waldeck created by the very knowledgeable OpenWrt member ramcheck!

ramcheck made his excellent work available at link http://www.dm.ufscar.br/profs/waldeck/j … ck.tar.bz2
You can read further info at the previous page 9 of this General Discussion about Bootloader/Image for a DLink DWL-2100AP

As for a fullflash original image, that can be found at http://xoomer.alice.it/ramponis/firmware/fullflash.rar
For just the original bootloader goto http://xoomer.alice.it/ramponis/firmware/Bootloader.rar

You should really check out all the excellent work by the also very knowledgeable OpenWrt member ramponis !!!

ramponis, a true pioneer with the DWL-2100AP, made his excellent hard work available at http://xoomer.virgilio.it/ramponis/

Good Luck !!!

(Last edited by NewLearner on 12 Oct 2011, 15:10)

andreiu

You may want to talk with andreiursan. I see he is also trying to get support for MX29LV800
His chips are CPU: AR2313A and Flash : MX29LV800BTC-90 (ID=005b   man ID=00c2)
You can read andreiursan's posts here:
http://www.dd-wrt.com/phpBB2/viewtopic. … start=1185
And don't miss the posts by LOM and RogFanther ! They are all trying to help with write to your same flash.

I see andreiursan is also trying to obtain help from sourceforge and the URjtag project.
http://sourceforge.net/tracker/?func=de … tid=944728

I now use jtag-waldeck for my DWL-2100AP which is version A3 with the AR2313A CPU and Atmel AT49BV322A flash chip.
URjtag had the boot blocks reversed for my chip so I went to jtag-waldeck and it works fine for my flash. Please see my previous post.

Macronix (0x00C2) and some of their flash chips are listed in jtag-waldeck But, unfortunately, I did not see support for your flash chip.

Form what I read it is relatively easy, but yet very technical, to add a flash chip. But honestly I don't know exactly how to do it.
Perhaps the URjtag project will come through with the addition?

Good Luck !!!

(Last edited by NewLearner on 17 Oct 2011, 15:16)

Hi all,

I have a Conceptronic C54APT which is equivalent to a DWL-2100v2, with Atmel flash. Any chance for a redboot ELF that can be first loaded in via the vxworks bootloader? So far I've found images only for other flashtypes. (I know I can update it via JTAG, but a redboot image that can be run first would be useful.)

Thanks,
-w-

Hi,
I'm trying to flash my old 2100ap via serial port. I'm using standard TTL converter and is able to see boot log with minicom or putty. But when I try to press ESC key nothing happens - boot process continues as usually without any boot prompt as said above. What I'm doing wrong?
I checked my serial connection and according to the openwrt wiki it's perfectly correct

(Last edited by alexey.kv on 8 Dec 2012, 17:08)

If your serial adapter is working then you should be able to login into system after firmware loads.
If you cannot enter username and password then your TX (RX on DWL board) is not connected properly.

I compile microredboot from dd-wrt and flash from jtag (finally need as fully softprogram flash)

NOT START, not any activities. hangs.

-------------------------------

RedBoot from Ubiquiti Nanostation 5 in DWL-2100AP is start normally, detect MX29LV320D, EN29LV320AB, S29AL032D (not detect AT49BV322A, but one byte patch is make loading kernel (reflash and urescue on AT49BV322A not work))

To compile "make ap48" was error, i by hand patch microredboot files diff "tail +2" to "tail -n +2"

--------------------------------

How make redboot print "hello, world" ("Redboot starting") in com-port and other debug info about process loading?

can switch on full debug about redboot starting on com port?

---------------------------------

Please help!

If you can compile last version of microredboot with support many flash chips to loading in DWL-2100AP, can help?
I make three days many test in DWL-2100AP, but can not starting self-compile microredboot..

http://www.lan23.ru/forum/showthread.ph … #post96175

I need help.. to make program reflashing 2100AP in Ubiquiti Nanostation 5 (Powerstation 5 Ext more like)
one D-Link DWL-2100AP already work as Ubiquiti PowerStation 5 Ext (of course, not 5GHz, DWL-2100AP is 2.4 GHz device)
1. Work as client in 2312-2484 MHz (extended range).
2. Work as AP in 1-14 standart and one non-stanard channel 2312MHz. (may be make all non-standard channels by compile SDK 4.0.2)
3. Work as AirMax client (tested with Nanostation Loco M2)

http://www.lan23.ru/forum/showthread.ph … #post96144

non work in Ubiquiti mode:
1. 40MHz bandwidht (108g)
2. wds-mode with D-link (wds-mode with other Ubiquiti device is work)

-------------------------------------------

In Ubiquiti mode planning make two featured options:
1. Open 40MHz bandwidth and 108Mbps speed - perhaps, SuperG will be popular in other models in the Ubiquiti AR2313 ..
2. Change DSSS settings (this options from one russian firmware BB Bluebox) to make work on one channel two-three Non-Standard Wifi DSSS retranslations, not hear standard wifi DSSS devices.

--------------------------------------------

Loader will flash DWL-2100AP as Ubiquiti Nanostation 5 to openwrt development as new life of 2100AP devices.

(Last edited by unicorp99 on 18 Mar 2013, 05:15)

Hi all,

I tried to Boot  OpenWrt with an elf Image via PXE but it seems to have a Problem "Kernel panic".

Device Revision: A4

Flash Chip:  Spansion s29al032d90tfi04

Has anyone an Idea What could be the Problem?

Thanks for the Help.

Linux version 2.6.30.10 (jow@nd-build-02.linux-appliance.net) (gcc version 4.3.3 (GCC) ) #5 Wed Dec 21 03:48:30 CET 2011
console [early0] enabled
CPU revision is: 0001800a (MIPS 4Kc)
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00001000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00001000
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 4064
Kernel command line: console=ttyS0,9600 rootfstype=squashfs,jffs2
Primary instruction cache 16kB, VIPT, 4-way, linesize 16 bytes.
Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 16 bytes
NR_IRQS:128
PID hash table entries: 64 (order: 6, 256 bytes)
console handover: boot [early0] -> real [ttyS0]
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 13000k/16384k available (2182k kernel code, 3384k reserved, 415k data, 136k init, 0k highmem)
Calibrating delay loop... 183.50 BogoMIPS (lpj=917504)
Mount-cache hash table entries: 512
net_namespace: 1008 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET: Registered protocol family 1
Radio config found at offset 0x10000(0x100)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
msgmni has been set to 25
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered (default)
gpiodev: gpio device registered with major 254
gpiodev: gpio platform device registered with access mask FFFFFFFF
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0xbc000003 (irq = 37) is a 16550A
eth0: Atheros AR231x: xx:xx:xx:xx:xx:xx, irq 4
ar231x_eth_mii: probed
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01)
physmap platform flash device: 00800000 at 1e000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
CFI mfr 0x00000001
CFI id  0x000000f9
Amd/Fujitsu Extended Query Table at 0x0040
  Amd/Fujitsu Extended Query version 1.1.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x3d0000
Searching for RedBoot partition table in physmap-flash.0 at offset 0x3e0000
Searching for RedBoot partition table in physmap-flash.0 at offset 0x3f0000
No RedBoot partition table detected in physmap-flash.0
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
eth0: Configuring MAC for full duplex
Please append a correct "root=" boot option; here are the available partitions:
1f00            4096 mtdblock0 driver: physmap-flash
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

(Last edited by hirakim on 1 May 2013, 15:08)

hirakim wrote:

I tried to Boot  OpenWrt with an elf Image via PXE but it seems to have a Problem "Kernel panic".
Device Revision: A4
Flash Chip:  Spansion s29al032d90tfi04

Linux version 2.6.30.10 (jow@nd-build-02.linux-appliance.net) (gcc version 4.3.3 (GCC) ) #5 Wed Dec 21 03:48:30 CET 2011
console [early0] enabled
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Try to use other versions of openwrt.. and older and laster

What method of boot you make?
You want to try reflash 2100ap to analog of Ubituiti NS2 (PowerStation 5 Ext in web, but some Bullet2 in work)?

Hey guys,

just a story of success from me, as I did not see anybody here who tried an "Conceptronic C54APT" (which is basically just a relabled DWL-2100AP): I works :-)

It is an A2 HV-Rev with an AMD AM29LV320DB flash chip, so i could use the redboot-loader linked at the wiki (http://wiki.openwrt.org/toh/d-link/dwl-2100ap). I first tried to boot from ramdisk, which unfortunatly did not work. I alway got a "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)", also with different version (backfire, attitude adjustments). I was brave an just flashed the redboot via serial, which worked witout problems then :-).
Attitude adjustment is definitely too heavy for this little device (as I read later in release notes of aa, too; i am a total newbie to openwrt) but backfire works quite nice.

(Last edited by pasdVn on 3 Nov 2013, 11:27)

pasdVn wrote:

just a story of success from me, as I did not see anybody here who tried an "Conceptronic C54APT" (which is basically just a relabled DWL-2100AP): I works :-)

Hi! Thanks!

If it story, please tell "step by step" about process for newbie too.

I have D-Link DWL-2100AP v4 (with ar2313a-001 and S29GL032M).

I get error when try boot  "Redboot Sperimentale per il 2100AP Rev. A4. (NOT TESTED! USE AT YOUR RISK!)" from http://xoomer.virgilio.it/ramponis/Pages/flash.htm

[Boot]: $ae(1,0)hai:redboot.elf h=192.168.1.11 e=192.168.1.20:0xffffff00 f=0x80 
Attached TCP/IP interface to ae1.                                               
Attaching network interface lo0... done.                                        
Loading... 103392                                                               
Error loading file: errno = 0x610007.

I tried compile redboot from source with patch and make script from ramcheck post (http://forum.openwrt.org/viewtopic.php?pid=50311#p50311)
but compiled version didn't work. GCC is 4.7.2 under ubuntu based linux.

RAM version (img or  elf)

[Boot]: $ae(1,0)hai:redboot.img h=192.168.1.11 e=192.168.1.20:0xffffff00 f=0x80 
  
<--- Nothing show, just boot normaly to default firmware/bootloader
Attached TCP/IP interface                                                       
ar531x rev 0x00005850 firmware startup...                                       
SDRAM TEST...PASSED  

ROM version

[Boot]: $ae(1,0)hai:redboot.img h=192.168.1.11 e=192.168.1.20:0xffffff00 f=0x80 
tttached TCP/IP i                                                               
                                                                                
Inevalide CPU access: 0x80000a16 at phys addr 0x1fc00000 write size 2           
task:                                                                           
exception frame: 0x80729e80                                                     
epc: 0x806955ec                                                                 
ra:  0x806f50f0                                                                 
  sr: 0x1000d003  ca: 0xeeeeeeee  gp: 0x80711d60  at: 0x00000000                
  a0: 0x80fc02a4  a1: 0xbfc00000  a2: 0x00000200  a3: 0xbfc001fc                
  t0: 0x00000000  t1: 0x24080fa0  t2: 0x00000000  t3: 0x00000000                
  t4: 0xbfc00030  t5: 0x00000000  t6: 0x3f3c02a4  t7: 0x00000000                
  t8: 0x00000000  t9: 0x00000000  v0: 0xNMI (watchdog): ErrorPC: 0x80682a00     
      epc: 0x806955ec bva: 0x0c1ae272 sr:  0x10489004 cse: 0x0080c000           
  R0: r0:  0x00000000 at:  0x00080000 v0:  0x80ff45c0 v1:  0x80ff45c0           
  R4: a0:  0xbfc00200 a1:  0xbc000000 a2:  0x8068299c a3:  0xbfc001fc           
  R8: t0:  0x00000078 t1:  0x00000020 t2:  0x0000001c t3:  0x00000062           
 R12: t4:  0x00000000 t5:  0x00000000 t6:  0x3f3c02a4 t7:  0x00000000           
 R16: s0:  0x806fba2c s1:  0x00000000 s2:  0x80729e80 s3:  0x2aaaaaab           
 R20: s4:  0x806fba2c s5:  0x00000000 s6:  0x00000000 s7:  0x00000000           
 R24: t8:  0x00000000 t9:  0x00000000 k0:  0x00000000 k1:  0x00000000           
 R28: gp:  0x80711d60 sp:  0x80729e18 fp:  0x80ff5688 ra:  0x80685a0c           
                                                                                
                                                                                
trying NMI callback: 0x80687658                                                 
watchdog: tripped by an spl abuser                                              
intContext: true                                                                
ErrorPC: 0x80682a00                                                             
3.0.0.43A                                                                       
Task Id: 0x80ff6120                                                             
stack dump: 0x80729e18                                                          
  0x00000000  0x00000000 *0x806d3f08 *0xeeeeeeee  0x3200eeee *0xeeeeeeee        
  0x00000001 *0x80709d80  0x00000061  0x00000001 *0x80ff5da0 *0x80ffa2b4        
 *0x80fffa60  0x00670045 *0x8068a7f8 *0xeeeeeeee *0xeeeeeeee *0xeeeeeeee        
 *0x806846f8  0x00000001  0x00000200 *0x80ff56c8 *0x80ff5688  0x00000200        
 *0x80fc02a4 *0x806932e0 *0xeeeeeeee *0xeeeeeeee *0xeeeeeeee *0xeeeeeeee        
  0x00000044  0x00804000 *0xeeeeeeee *0xeeeeeeee *0xeeeeeeee *0xeeeeeeee        
  0x1000d003 *0x806955ec *0xcccccccd  0x00000000  0x00000000  0x00000000        
 *0xbfc00200 *0x80fc02d0 *0x80fc02a4 *0xbfc00000  0x00000200 *0xbfc001fc        
  0x00000000  0x24080fa0  0x00000000  0x00000000 *0xbfc00030  0x00000000        
  0x3f3c02a4  0x00000000  0x00000200 *0x80ff56c8 *0x80ff5688  0x00000200        
 *0x80fc02a4  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000        
 *0xeeeeeeee *0xeeeeeeee *0x80711d60 *0x80ff55e8 *0xeeeeeeee *0x806f50f0        
 *0xeeeeeeee *0xeeeeeeee  0x00000000  0x00000010 *0xfdc6ffff  0x7bfff9df        
 *0x80729f40  0x0088cee1 *0xd7fdffff *0xec7fffdd  0x00000000  0x00000000        
 *0xffffffff  0x5e7dffff *0xfdef5bdf *0xffffff7f *0xeff57ffb *0xfdfeefff        
 *0xffffdf9f *0xc1fbffff *0xf66df7bb *0xfffbf7fd  0x7ef7fefb *0xf7beffdf        
  0x799fffef *0xcb77ffff *0xffffefff *0xe7fbeeff  0x7fbfbfff *0xa96f5bbe        
 *0xef3ffffb *0xf7af7fff *0xbf7f7eff *0xefbafeff *0xdffff47f *0xefffffff        
 *0xf5bdbfff *0xee6fbffd  0x3ffc7fff *0xb9bfffee  0x7df67ffb *0xfd7afdb7        
  0x7f7bffef *0xbaffefff *0xf7fffeff *0xf7fffff7 *0xedf6efff  0x7deddfff        
  0x7adfffff *0xdffffbfd *0xff7bfffd *0xdedff5ff *0xefafdffb *0xd4c7ffff        
 *0xc7ffffff  0x6efbffff *0xcffffffd *0xfdadffff *0xcd7fffff *0xcebfbfff        
  0x7fefffff *0xbbfffffb *0xbbddffff *0xff6fffff  0x7e6efdbf  0x4eeefffb        
  0x7ad7ffff *0xfbafffdf  0x6bd7b7ef  0x764effdf *0xf67efbff *0xf5cfffff 

[Boot]: $ae(1,0)hai:redboot.elf h=192.168.1.11 e=192.168.1.20:0xffffff00 f=0x80 
Attached TCP/IP interface to ae1.                                               
Attaching network interface lo0... done.                                        
Loading... 90680                                                                
Error loading file: errno = 0x610007. 

But if I try boot redboot220.img (this file from wiki for S29GL032D)

[Boot]: $ae(1,0)hai:redboot220.img h=192.168.1.11 e=192.168.1.20:0xffffff00 f=00
Attached TCP/IP interface to ae1.                                               
Attaching network interface lo0... done.                                        
Loading... 279808                                                               
Starting at 0x80010000...                                                       
                                                                                
+                                                                               
RedBoot startup                                                                 
FLASH configuration checksum error or invalid key                               
Can't get BOOTP info, using default IP address                                  
Ethernet eth1: MAC address 00:19:5b:2d:bf:e2                                    
IP: 192.168.1.1, Default server: 0.0.0.0                                        
                                                                                
RedBoot(tm) bootstrap and debug environment [RAM]                               
Non-certified release, version v2_0 - built 17:10:53, Nov 22 2009               
With changes made by Artur Korobov <elgenius@yandex.ru>                         
                                                                                
                                                                                
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.                                   
                                                                                
RAM: 0x80010000-0x80800000, 0x80054500-0x807e1000 available                     
FLASH: 0xbe000000 - 0xbe3e0000, 62 blocks of 0x00010000 bytes each.             
RedBoot> 

So, what is wrong? Problem in GCC?

(Last edited by Vl@d on 28 Aug 2014, 17:14)

I have a Netgear WG102 that uses the same hardware. It uses a Samsung K8D3216UBC flash instead of a Macronix flash. Is there a redboot bootloader available for this flash? I couldn't find one precompiled and I'm not sure what is involved to build a redboot bootloader for this. Anyone have any information?

Redboot for revision a5 (Macronix MX29LV320D both T/B types flash). Also support Atmel and Spansion flash (a3 and a4 revisions).
http://rghost.ru/58414270

Actually this is already posted here redboot220, but support for AMD flash replaced with MX.

(Last edited by _DS_ on 8 Oct 2014, 16:43)

Tested it with my S29GL032M
Loaded but didn't recognize my flash:

+
RedBoot startup
FLASH configuration checksum error or invalid key
Can't get BOOTP info, using default IP address
Ethernet eth1: MAC address 00:19:5b:2d:bf:e2
IP: 192.168.1.1, Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [RAM]
Non-certified release, version v2_0 - built 17:10:53, Nov 22 2009
With changes made by Artur Korobov <elgenius@yandex.ru>


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

RAM: 0x80010000-0x80800000, 0x80054500-0x807e1000 available
FLASH: 0xbe000000 - 0xbe3e0000, 62 blocks of 0x00010000 bytes each.
RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
AR531Xtffs:(0,0):/fl/apimg1 e=192.168.1.20:0xffffff00 o=ae  0x3A2F666C  0x2F617069  0x6D673120  0x653D3139
RedBoot>

What toolkit and OS you use? How do you compile? What source?

Your flash was successfully recognized:
FLASH: 0xbe000000 - 0xbe3e0000, 62 blocks of 0x00010000 bytes each.

Line FLASH configuration checksum error or invalid key
displayed because config space is empty, this message removed after first fconfig save.

Just follow wiki documentation.

I'm not compiled it, binary patching only smile

(Last edited by _DS_ on 6 Oct 2014, 17:13)

_DS_, Thank you!
Yesterday I successfully flashed my D-Link.
How did you do binary patch? Just replace at the HEX editor?

Yes, hiew and ida rulez smile

Tried 12.09 and 14.07 - router freezes(Load Average 9) when I try configure WiFi network through Lucie...

Not only Wifi - ethernet too...

(Last edited by Vl@d on 9 Oct 2014, 12:17)