Menu
▾
▴
isl3893-devel — developpers mailing-list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(6) |
Apr
(10) |
May
(22) |
Jun
(17) |
Jul
(17) |
Aug
(36) |
Sep
(9) |
Oct
(3) |
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(2) |
Mar
(15) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(29) |
Aug
(9) |
Sep
(15) |
Oct
(6) |
Nov
|
Dec
(7) |
| 2006 |
Jan
(8) |
Feb
(3) |
Mar
(58) |
Apr
(58) |
May
(19) |
Jun
|
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2008 |
Jan
(13) |
Feb
(15) |
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: john <jo...@hi...> - 2024-07-13 06:53:10
|
Hi， This is John from Hi-Top Mold Group Ltd, a factory in China. We provide custom parts, good at all CNC machining, CNC turning, plastic injection mold, plastic molding parts and die-casting mold .you can directly send your drawings or samples to me for custom made. Thanks. I look forward to the opportunity to cooperate with you. Or please forward this email to your colleague who is in charge of purchasing parts, Thank you. It may only take you one minute to reply the email, but it means a lot to me, looking forward to your reply. Thanks. Best Regards John Yang Hi-Top Mold Group Ltd 806 TianDiWuXian RD,Xing'An ,Chang'an , DongGuan , GuangDong ,China 523880 Tel: 86-769-85306531 Fax: 86-769-85305523 jo...@hi... www.hi-topmold.com If you don't want to receive our emails, you can easily unsubscribe here. |
|
From: Sebastian S. <seb...@st...> - 2014-10-09 19:53:51
|
First of all, you gentlemen are totally awesome! I got several great answers and the sources, i didnt thought of this the whole day. The reason I was looking for it was that I found some boxes in the basement and was looking for a way to reanimate them. The idea was to use them as simple network/wireless usb data logger or similarly simple tasks. Since I'm coming from the bottom up (started with microcontrollers) missing or limited resources wont be that much of a problem. Anyway unbelieveable to get such answers after half an hour, thank you very much! Sebastian S. |
|
From: Erich S. <er...@de...> - 2014-10-09 18:55:04
|
Have you tried the medion download? I think it is the same hardware. Back then I was able to get it to build, but I don't think I have a copy anymore... Working on the device was quite a pain. See: it doesn't have a MMU. There is not much preventing you from overwriting even system memory accidentially. Also, fork() does not work - again, no MMU. No way to clone a process with independent memory! This prevents lots of software from compiling! Unless you have prior experience on MMUless systems - it's much more painful than you'd expect. A bug in the C library realloc() call (yes, it has a nonstandard malloc, too) prevented SSL libraries from working (I managed to fix that somehow). Forget about updating the kernel in any way. I was unable to even identify what version was used, yet to get a clean diff. I guess it was a Frankenstein kernel, with directories originaring in very different kernel versions... Either way, I wouldn't touch it again, ever. I'd rather get a raspberry Pi now, or a hackable fritz version or anything else. Regards, Erich |
|
From: Sebastian S. <seb...@st...> - 2014-10-09 18:00:49
|
To anyone _still_ reading this ml: Hi, I'm looking for the sources for the AP-600RP Fujitsu-Siemens router. This mailing list seems dead since 2009 but its my last hope, since there's hardly any info left about that router on the webs. Fujitsu-siemens.com is down and I gathered anything I could find, kernel patches, toolchain and minimal-image but I couldn't find the sources itself anywhere. Even web.archive.org has some backups of the sf /download/.. folders, but not the src ones. In a mail from 2006 the files are annouced to be cleaned up ( http://article.gmane.org/gmane.linux.uclinux.isl3893.devel/289 ), maybe anyone still has a backup or local copy he could send me? I'm also sending this mail to any email address I could find about that topic, so please don't be annoyed and forgive me for the double spam. Hope that someone can help me out Sebastian S. |
|
From: ulf k. <u....@gm...> - 2009-08-09 22:31:37
|
this sounds like an broken firmware, which is looking for a firmware while starting. bootloader 0.0.6 is the standard isl bootloader but version 1.00.020 i never saw. bye ulf 2009/8/7 Benjamin Henrion <bh...@ud...> > Nice email... > > ---------- Forwarded message ---------- > From: ello jusi <ell...@gm...> > Date: Fri, Aug 7, 2009 at 11:07 PM > Subject: firmware > To: zo...@gm... > > > hei > > do you know with firware buy this router' > SMC2804WBR > > Numbers of DHCP Clients: 1 > Runtime Code Version: > V1.00.020 > Boot Code Version: V0.00.06 > LAN MAC Address: > 00-04-E2-AF-A5-14 > WAN MAC Address: > 00-0D-9D-81-4D-54 > WLAN MAC Address: > 00-04-E2-AF-A5-14 > Hardware Version: 01 > Serial Num: S408041736 > help me > > > -- > Benjamin Henrion <bhenrion at ffii.org> > FFII Brussels - +32-484-566109 - +32-2-4148403 > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Isl3893-devel mailing list > Isl...@li... > https://lists.sourceforge.net/lists/listinfo/isl3893-devel > |
|
From: Benjamin H. <bh...@ud...> - 2009-08-07 21:11:20
|
Nice email... ---------- Forwarded message ---------- From: ello jusi <ell...@gm...> Date: Fri, Aug 7, 2009 at 11:07 PM Subject: firmware To: zo...@gm... hei do you know with firware buy this router' SMC2804WBR Numbers of DHCP Clients: 1 Runtime Code Version: V1.00.020 Boot Code Version: V0.00.06 LAN MAC Address: 00-04-E2-AF-A5-14 WAN MAC Address: 00-0D-9D-81-4D-54 WLAN MAC Address: 00-04-E2-AF-A5-14 Hardware Version: 01 Serial Num: S408041736 help me -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 |
|
From: ulf k. <u....@gm...> - 2009-01-30 15:33:06
|
hi, folks nice to see, that all you still reading the mailing list - even after 5 years of isl3893 hacking - haha benjamin and i remade the website last year, so more pictures more infos are on isl3893.wikidot.com the msi device has only 2megabyte of flash. and using a rtl switch chip. bye ulf 2009/1/30 Ruben Faelens <par...@gm...>: > Imrich Konkol wrote: >> Hello, >> >> Erich Schubert <erich <at> debian.org> writes: >> >> >> >>> Actually, Googling for that number returned be 16 mbit, which would be >>> 2 MB Flash. I think most isl3893 devices had 4 MB Flash, which would >>> explain why you got that error. >>> >> >> I took the description from hacking web page, >> but the final capacity is 2M in my undestanding. >> >> >>> Did you try recovery with the MSI firmware? >>> >>> >> http://global.msi.com.tw/index.php?func=downloaddetail&type=firmware&maincat_no=131&prod_no=91 >> >> I've downloaded lot of firmware versions for MSI nad Minitar. All are .gzh files. >> This is not binary image I can flash. >> When I issue "tftp -i 192.0.2.93 PUT firmware.gzh" I always get error. >> >> When I open the file in hex editor I see completely different file structure for >> .bin and .gzh. >> I can see meaningful sections in .img file. >> Lines: xMVC, xSYS and other readable strings. >> >> The .gzh file structure is different. I see just raw data very similar to ZIP >> file, but initial line is not ZIP compatible and unzip cannot read it. >> >> If I type Linux 'file' command, I just get: "firmware.gzh: data" >> >> Best regards, >> Imrich >> > > Don't forget that some manufacturers dumben down their user, and call > the web pages used to configure the AP "firmware". I think Eric provided > you with the best course of action: try some of the 3com firmware and > hope that they used the same switch chips... > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Isl3893-devel mailing list > Isl...@li... > https://lists.sourceforge.net/lists/listinfo/isl3893-devel > |
|
From: Ruben F. <par...@gm...> - 2009-01-30 15:26:21
|
Imrich Konkol wrote: > Hello, > > Erich Schubert <erich <at> debian.org> writes: > > > >> Actually, Googling for that number returned be 16 mbit, which would be >> 2 MB Flash. I think most isl3893 devices had 4 MB Flash, which would >> explain why you got that error. >> > > I took the description from hacking web page, > but the final capacity is 2M in my undestanding. > > >> Did you try recovery with the MSI firmware? >> >> > http://global.msi.com.tw/index.php?func=downloaddetail&type=firmware&maincat_no=131&prod_no=91 > > I've downloaded lot of firmware versions for MSI nad Minitar. All are .gzh files. > This is not binary image I can flash. > When I issue "tftp -i 192.0.2.93 PUT firmware.gzh" I always get error. > > When I open the file in hex editor I see completely different file structure for > .bin and .gzh. > I can see meaningful sections in .img file. > Lines: xMVC, xSYS and other readable strings. > > The .gzh file structure is different. I see just raw data very similar to ZIP > file, but initial line is not ZIP compatible and unzip cannot read it. > > If I type Linux 'file' command, I just get: "firmware.gzh: data" > > Best regards, > Imrich > Don't forget that some manufacturers dumben down their user, and call the web pages used to configure the AP "firmware". I think Eric provided you with the best course of action: try some of the 3com firmware and hope that they used the same switch chips... |
|
From: Imrich K. <ik...@in...> - 2009-01-30 13:59:59
|
Hello, Erich Schubert <erich <at> debian.org> writes: > Actually, Googling for that number returned be 16 mbit, which would be > 2 MB Flash. I think most isl3893 devices had 4 MB Flash, which would > explain why you got that error. I took the description from hacking web page, but the final capacity is 2M in my undestanding. > Did you try recovery with the MSI firmware? > http://global.msi.com.tw/index.php?func=downloaddetail&type=firmware&maincat_no=131&prod_no=91 I've downloaded lot of firmware versions for MSI nad Minitar. All are .gzh files. This is not binary image I can flash. When I issue "tftp -i 192.0.2.93 PUT firmware.gzh" I always get error. When I open the file in hex editor I see completely different file structure for .bin and .gzh. I can see meaningful sections in .img file. Lines: xMVC, xSYS and other readable strings. The .gzh file structure is different. I see just raw data very similar to ZIP file, but initial line is not ZIP compatible and unzip cannot read it. If I type Linux 'file' command, I just get: "firmware.gzh: data" Best regards, Imrich |
|
From: Erich S. <er...@de...> - 2009-01-30 13:43:59
|
Hello Imrich, > Yes, definitely. The flash is 29LV160BB - 8Mb flash (2M x 32 bits) - > as described in hacking page > (http://satin.sensation.net.au/rowan/MSI-RG54G2-hack.html) Actually, Googling for that number returned be 16 mbit, which would be 2 MB Flash. I think most isl3893 devices had 4 MB Flash, which would explain why you got that error. As for the .gzh file: Judging from the recovery section of the manual for that 'similar' access point, it is the raw firmware image, you do not need to do anything to it. It seems as if they changed the magic header, so they might have modified the low level boot loader of the AP. Did you try recovery with the MSI firmware? http://global.msi.com.tw/index.php?func=downloaddetail&type=firmware&maincat_no=131&prod_no=91 Do the same thing like you did with the .img file. Regards, Erich |
|
From: Imrich K. <ik...@in...> - 2009-01-30 13:19:14
|
Hello Erich, Erich Schubert <erich <at> debian.org> writes: > That might indicate that your accesspoint has a smaller flash chip only. > I remember having seen some reports on isl3893 based devices that were > not running Linux and only had a smaller flash chip. You might still be > able to get Linux on there (not sure how small you can get), but you'll > have to choose a different partitioning and generated the appropriate > images yourself. Yes, definitely. The flash is 29LV160BB - 8Mb flash (2M x 32 bits) - as described in hacking page (http://satin.sensation.net.au/rowan/MSI-RG54G2-hack.html) > > If I recall it corretly (that was like 5 years ago?), it was maybe the > 3com devices. You could try a firmware for these devices instead (the > web page should have the model numbers that are isl3893 based). My current goal is to restore the basic functionality on my AP. For this I need binary image of original firmware. Then I can play with Linux bit more. Do you have any advice in this area? How to convert .gzh file to .bin? Thanks. Best regards, Imrich |
|
From: Erich S. <er...@de...> - 2009-01-30 12:58:08
|
Hello, > Creating 3 MTD partitions on "Physically mapped flash": > 0x00000000-0x00010000 : "Bootloader" > 0x00010000-0x00380000 : "Access Point Firmware" > mtd: partition "Access Point Firmware" extends beyond the end of device "Physica > lly mapped flash" -- size truncated to 0x1f0000 > 0x00380000-0x00200000 : "Flash Filesystem" > mtd: partition "Flash Filesystem" is out of reach -- disabled > Division by zero in kernel. That might indicate that your accesspoint has a smaller flash chip only. I remember having seen some reports on isl3893 based devices that were not running Linux and only had a smaller flash chip. You might still be able to get Linux on there (not sure how small you can get), but you'll have to choose a different partitioning and generated the appropriate images yourself. If I recall it corretly (that was like 5 years ago?), it was maybe the 3com devices. You could try a firmware for these devices instead (the web page should have the model numbers that are isl3893 based). Regards, erich |
|
From: Imrich K. <ik...@in...> - 2009-01-30 11:29:00
|
Ruben Faelens <parasietje <at> gmail.com> writes: > > > You should REALLY try to connect a serial console. If you have an oscilloscope, try testing out various empty PCB pin header connections and look for a typical serial signal. Don't forget the MAX232!For example:http://isl3893.sourceforge.net/intersil-39300.gifTry all the pin headers, including the ones where no parts have been placed (the soldering pads left of the right bottom grey capacitator) Hi all, I'm back with my investigation. I found serial port on PCB pin header JP2. The connection is in attachment 1. I use standard Nokia cable as RS-232 level converter. After connecting the terminal, I could see the boot loader repeating same message and AP was rebooting over and over again (attachment 2). After long push of reset button prompt to enter password appeared (attachment 3) I tried all possible combinations, but this seems to be vendor specific. So I followed the procedure for flashing the firmware and tried apfw.minimal. I could boot linux, but no newtork nor wireless adapters have been found (attachment 4) The network bridge in this model is RTL8305. The logical step was to restore original firmware. But MSI or Minitar is providing only some strange version of firmware which is not binary image of flash memory. The extension is GZH, but gunzip cannot do anything wiht it. What needs to be done to flash this firmware? Or is there any way if I have the same piece of harware to get the the binary image from it? Of course without removing any chips or doing big hardware changes. Thanks for your help. Best regards, Imrich ------------------------------------------------- Attachment 1: ------------------------------------------------- JP2 serial port pinout ====================== 1> 3V3 ---[] O--- NC RxD ---O O--- NC TxD ---O O--- NC NC ---O O--- NC GND ---O O--- NC Serial port settings: 115200,8N1,no flow control ------------------------------------------------- Attachment 2: ------------------------------------------------- Rescueing Boot for the ISL3893, version 0.5.3.0 Copyright (C) 1993-2002 Intersil Americas Inc. All Rights Reserved. No valid MacAddress found in PDA, defaulting to 02.10.91.38.93.00 Forcing soft reset from Bootloaderđ Rescueing Boot for the ISL3893, version 0.5.3.0 Copyright (C) 1993-2002 Intersil Americas Inc. All Rights Reserved. No valid MacAddress found in PDA, defaulting to 02.10.91.38.93.00 Boot: start searching for image... Found Boot: Checking Image CRC32... Okay. . Rescueing Boot for the ISL3893, version 0.5.3.0 Copyright (C) 1993-2002 Intersil Americas Inc. All Rights Reserved. No valid MacAddress found in PDA, defaulting to 02.10.91.38.93.00 Forcing soft reset from Bootloaderđ Rescueing Boot for the ISL3893, version 0.5.3.0 Copyright (C) 1993-2002 Intersil Americas Inc. All Rights Reserved. No valid MacAddress found in PDA, defaulting to 02.10.91.38.93.00 Boot: start searching for image... Found Boot: Checking Image CRC32... Okay. CRC32... Okay. etc... ------------------------------------------------- Attachment 3: ------------------------------------------------- Boot: start searching for image... Found Boot: Checking Image CRC32... Okay. đpassword: ------------------------------------------------- Attachment 4: ------------------------------------------------- Rescueing Boot for the ISL3893, version 0.5.3.0 Copyright (C) 1993-2002 Intersil Americas Inc. All Rights Reserved. No valid MacAddress found in PDA, defaulting to 02.10.91.38.93.00 Forcing soft reset from Bootloader? Rescueing Boot for the ISL3893, version 0.5.3.0 Copyright (C) 1993-2002 Intersil Americas Inc. All Rights Reserved. No valid MacAddress found in PDA, defaulting to 02.10.91.38.93.00 Entering recovery mode. Trying ethernet... Using Static IP address 192.0.2.93 apipa: got IP address 169.254.129.129 dhcp: got IP address 192.0.2.93, leasetime = -1, t1 = 4294966, t2 = 4294966 valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code valid_bootrecord() -> ERROR: Illegal code XXXXXXXXXXXXXXXXXXCRC check ok OKA Uncompressing Linux (bzip2)... done, booting the kernel. Linux version 2.4.19-uc1 (hds@atlas) (gcc version 2.95.3.2 20010315 (release)) # 2 Fri Jul 29 21:43:51 CEST 2005 Processor: ARM ARM946 revision 1 Architecture: ISL3893 Boot Struct at 0003f000 Boot parameter block at 0003ffc8 SRAM size 0x7b7b40 On node 0 totalpages: 2039 zone(0): 0 pages. zone(1): 2039 pages. zone(2): 0 pages. Kernel command line: Calibrating delay loop... 72.29 BogoMIPS Memory: 7MB = 7MB total Memory: 4920KB available (1248K code, 1583K data, 44K init) Dentry cache hash table entries: 1024 (order: 1, 8192 bytes) Inode cache hash table entries: 512 (order: 0, 4096 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 2048 (order: 1, 8192 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Invalid Boot Parameter Block 0003ffc8 (magic 0) Starting kswapd JFFS version 1.0, (C) 1999, 2000 Axis Communications AB pty: 256 Unix98 ptys configured ISL3893 UART serial driver version 1.0 (2002-07-11) with no serial options enabl ed ttyS00 at 0xc0000500 (irq = 8) is a ISL3893 UART dev_elem, type 2, mtu 1568, head 224, tail 32 eth0: Prism Embedded MVC v2 packet IF version 0.4.0.0 found,<3>Couldn't get MAC address for eth0 from PDA... aborting... dev_elem, type 1, mtu 1568, head 224, tail 32 eth1: Prism Embedded MVC v2 packet IF version 0.4.0.0 found,<3>Couldn't get MAC address for eth1 from PDA... aborting... dev_elem, type 2, mtu 1568, head 224, tail 32 eth2: Prism Embedded MVC v2 packet IF version 0.4.0.0 found,<3>Couldn't get MAC address for eth2 from PDA... aborting... Blkmem copyright 1998,1999 D. Jeff Dionne Blkmem copyright 1998 Kenneth Albanowski Blkmem 2 disk images: 0: 186AA4-2B3EA3 [VIRTUAL 186AA4-2B3EA3] (RO) 1: 812AA00-83801FF [VIRTUAL 812AA00-83801FF] (RO) loop: loaded (max 8 devices) PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered physmap flash device: 400000 at 8000000 Amd/Fujitsu Extended Query Table v1.0 at 0x0040 number of CFI chips: 1 Creating 3 MTD partitions on "Physically mapped flash": 0x00000000-0x00010000 : "Bootloader" 0x00010000-0x00380000 : "Access Point Firmware" mtd: partition "Access Point Firmware" extends beyond the end of device "Physica lly mapped flash" -- size truncated to 0x1f0000 0x00380000-0x00200000 : "Flash Filesystem" mtd: partition "Flash Filesystem" is out of reach -- disabled Division by zero in kernel. Function entered at [<00052404>] from [<00163db8>] Function entered at [<000f2b7c>] from [<0004786c>] Function entered at [<00047790>] from [<00040688>] r5 = 0004AD90 r4 = 0004AD2C Function entered at [<0004066c>] from [<000406cc>] r5 = 0030F100 r4 = 002C8738 Function entered at [<000406a0>] from [<0004b04c>] Function entered at [<0004b03c>] from [<0004ed74>] r7 = 002BFB94 r6 = 002BFB98 r5 = 0030F100 r4 = 002C8738 Division by zero in kernel. Function entered at [<00052404>] from [<00163db8>] Function entered at [<000f2b7c>] from [<0004786c>] Function entered at [<00047790>] from [<00040688>] r5 = 0004AD90 r4 = 0004AD2C Function entered at [<0004066c>] from [<000406cc>] r5 = 0030F100 r4 = 002C8738 Function entered at [<000406a0>] from [<0004b04c>] Function entered at [<0004b03c>] from [<0004ed74>] r7 = 002BFB94 r6 = 002BFB98 r5 = 0030F100 r4 = 002C8738 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 512 bind 512) ip_conntrack (63 buckets, 504 max) PPTP netfilter connection tracking: registered PPTP netfilter NAT helper: registered ip_tables: (C) 2000-2002 Netfilter core team NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NET4: Ethernet Bridge 008 for NET4.0 cramfs: wrong magic JFFS: Trying to mount a non-mtd device. VFS: Mounted root (romfs filesystem) readonly. Mounting proc on /proc init started: BusyBox v0.51 (2005.07.29-19:38+0000) multi-call binary jffs_scan_flash(): Did not find even a single chunk of free space. This is BAD! # SIOCSIFADDR: No such device SIOCGIFFLAGS: No such device # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) # ------------------------------------------------- |
|
From: Ruben F. <par...@gm...> - 2009-01-26 19:29:32
|
You should REALLY try to connect a serial console. If you have an oscilloscope, try testing out various empty PCB pin header connections and look for a typical serial signal. Don't forget the MAX232! For example: http://isl3893.sourceforge.net/intersil-39300.gif Try all the pin headers, including the ones where no parts have been placed (the soldering pads left of the right bottom grey capacitator) On Mon, Jan 26, 2009 at 4:25 PM, Benjamin Henrion <bh...@ud...> wrote: > On Mon, Jan 26, 2009 at 4:18 PM, Imrich Konkol <ik...@in...> wrote: > >> Benjamin Henrion <bh <at> udev.org> writes: > > > >> > >> On Sun, Jan 25, 2009 at 8:17 PM, ikon <ikon <at> inmail.sk> wrote: > >> > Hi, > >> > > >> > my MSI RG54G2 is unable to boot since this morning. > >> > I cannot connect to the IP of the router via cable nor wifi. > >> > > >> > Power LED is on, but all other LEDs flash every 2-3 seconds > >> > for few miliseconds. > >> > It seems like Flash corruption - boot fails. > >> > When RESET button is pressed WLAN LED flashes > >> > until power is removed. > >> > > >> > Is there any way how to reprogram original firmware > >> > while flash chip is in-system? > >> > Does anybody have any experience with JTAG on RG54G2? > >> > >> I still have to test JTAG on isl3893 based devices, but tomorrow I am > >> working on a JTAG session in the evening. > >> > >> I will try to get JTAG access on some device I have here. > >> > >> BTW, does the RG54G2 runs linux? > >> > > > > > > Hi Benjamin, > > > > I'm not sure what OS is running on RG54G2, but read on some forums there > is some > > violation of GPL. So I guess some Linux is in there. > > > > In addition, I don't have any information of JP1 and JP2, which is JTAG > and if > > these is any serial port available for reflashing the firmware. > > > > Thanks for testing JTAG and posting your results. > > Otherwise, there might be some "reset button" you could press for > 20secs or more at boot, it might wipe out some bad config you might > have done. > > There is also some minimal image somewhee you could give to the > bootloader if you have a serial console: > > > http://isl3893.sourceforge.net/download/firmware/siemens-wlanap600rp/apfw.minimal.img > > -- > Benjamin Henrion <bhenrion at ffii.org> > FFII Brussels - +32-484-566109 - +32-2-4148403 > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Isl3893-devel mailing list > Isl...@li... > https://lists.sourceforge.net/lists/listinfo/isl3893-devel > |
|
From: Benjamin H. <bh...@ud...> - 2009-01-26 15:25:19
|
On Mon, Jan 26, 2009 at 4:18 PM, Imrich Konkol <ik...@in...> wrote: >> Benjamin Henrion <bh <at> udev.org> writes: > >> >> On Sun, Jan 25, 2009 at 8:17 PM, ikon <ikon <at> inmail.sk> wrote: >> > Hi, >> > >> > my MSI RG54G2 is unable to boot since this morning. >> > I cannot connect to the IP of the router via cable nor wifi. >> > >> > Power LED is on, but all other LEDs flash every 2-3 seconds >> > for few miliseconds. >> > It seems like Flash corruption - boot fails. >> > When RESET button is pressed WLAN LED flashes >> > until power is removed. >> > >> > Is there any way how to reprogram original firmware >> > while flash chip is in-system? >> > Does anybody have any experience with JTAG on RG54G2? >> >> I still have to test JTAG on isl3893 based devices, but tomorrow I am >> working on a JTAG session in the evening. >> >> I will try to get JTAG access on some device I have here. >> >> BTW, does the RG54G2 runs linux? >> > > > Hi Benjamin, > > I'm not sure what OS is running on RG54G2, but read on some forums there is some > violation of GPL. So I guess some Linux is in there. > > In addition, I don't have any information of JP1 and JP2, which is JTAG and if > these is any serial port available for reflashing the firmware. > > Thanks for testing JTAG and posting your results. Otherwise, there might be some "reset button" you could press for 20secs or more at boot, it might wipe out some bad config you might have done. There is also some minimal image somewhee you could give to the bootloader if you have a serial console: http://isl3893.sourceforge.net/download/firmware/siemens-wlanap600rp/apfw.minimal.img -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 |
|
From: Imrich K. <ik...@in...> - 2009-01-26 15:18:34
|
> Benjamin Henrion <bh <at> udev.org> writes: > > On Sun, Jan 25, 2009 at 8:17 PM, ikon <ikon <at> inmail.sk> wrote: > > Hi, > > > > my MSI RG54G2 is unable to boot since this morning. > > I cannot connect to the IP of the router via cable nor wifi. > > > > Power LED is on, but all other LEDs flash every 2-3 seconds > > for few miliseconds. > > It seems like Flash corruption - boot fails. > > When RESET button is pressed WLAN LED flashes > > until power is removed. > > > > Is there any way how to reprogram original firmware > > while flash chip is in-system? > > Does anybody have any experience with JTAG on RG54G2? > > I still have to test JTAG on isl3893 based devices, but tomorrow I am > working on a JTAG session in the evening. > > I will try to get JTAG access on some device I have here. > > BTW, does the RG54G2 runs linux? > Hi Benjamin, I'm not sure what OS is running on RG54G2, but read on some forums there is some violation of GPL. So I guess some Linux is in there. In addition, I don't have any information of JP1 and JP2, which is JTAG and if these is any serial port available for reflashing the firmware. Thanks for testing JTAG and posting your results. Best regards, Imrich |
|
From: Benjamin H. <bh...@ud...> - 2009-01-26 13:36:57
|
On Sun, Jan 25, 2009 at 8:17 PM, ikon <ik...@in...> wrote: > Hi, > > my MSI RG54G2 is unable to boot since this morning. > I cannot connect to the IP of the router via cable nor wifi. > > Power LED is on, but all other LEDs flash every 2-3 seconds > for few miliseconds. > It seems like Flash corruption - boot fails. > When RESET button is pressed WLAN LED flashes > until power is removed. > > Is there any way how to reprogram original firmware > while flash chip is in-system? > Does anybody have any experience with JTAG on RG54G2? I still have to test JTAG on isl3893 based devices, but tomorrow I am working on a JTAG session in the evening. I will try to get JTAG access on some device I have here. BTW, does the RG54G2 runs linux? -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 |
|
From: ikon <ik...@in...> - 2009-01-26 13:25:11
|
Hi, my MSI RG54G2 is unable to boot since this morning. I cannot connect to the IP of the router via cable nor wifi. Power LED is on, but all other LEDs flash every 2-3 seconds for few miliseconds. It seems like Flash corruption - boot fails. When RESET button is pressed WLAN LED flashes until power is removed. Is there any way how to reprogram original firmware while flash chip is in-system? Does anybody have any experience with JTAG on RG54G2? Thanks for your help in advance. Best regards, Imrich |
|
From: Benjamin H. <bh...@ud...> - 2008-08-23 01:21:06
|
Hi, I have grabbed the latest uCdist distribution: uClinux-dist-20080808.tar.bz2 where I am trying to compile an isl3893 kernel. I will try tomorrow to get it running. I attach my .config file for the kernel v2.4.34.5-uc0. You should type, after having installed the binary toolchain here in your /opt dir: http://mesh.dl.sourceforge.net/sourceforge/isl3893/isl3893-tools-20060321-bin-i386.tar.bz2 $ cd uClinux-dist/linux-2.4.x edit Makefile and replace: CROSS_COMPILE = /opt/uclinux_tools_1.6.0.0/bin/arm-elf- $ make menuconfig ARCH=armnommu Then it has some options: (Intersil) ARM system type [*] Generate big endian code [*] Set flash/sdram size and base addr (00800000) (S)DRAM Base Address (00800000) (S)DRAM Size (00400000) FLASH Base Address (00400000) FLASH Size (ROM) Kernel executes from --- Intersil Specific Settings [*] SIDED support [*] Use ARM9 Memory Protection Unit (MPU) [*] Use bzip2 instead of gzip for kernel compression --- MAC Controller related settings (ISL3893) Intersil MAC Chip [*] Enable MVC DEBUG device [ ] Enable PCI device [*] Enable micro AP device module [*] Enable Console on MVC DEBUG device [*] Standalone Operation (No bootloader or MVC)? (00420000) Compressed Kernel Link Address [*] Expert settings? (88000000) Asyncronous Clock Frequency (88000000) Syncronous Clock Frequency But when I try to compile it complains: $ make dep [...] $ make /opt/uclinux_tools_1.6.0.0/bin/arm-elf-gcc -D__KERNEL__ -I/home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-builtin-sprintf -pipe -DKBUILD_BASENAME=main -c -o init/main.o init/main.c In file included from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/io.h:74, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/blkdev.h:11, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/blk.h:4, from init/main.c:25: /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/arch/io.h:59: warning: `__arch_getl' redefined /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/io.h:37: warning: this is the location of the previous definition /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/arch/io.h:60: warning: `__arch_putl' redefined /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/io.h:40: warning: this is the location of the previous definition In file included from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/string.h:20, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/fs.h:23, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/capability.h:17, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/binfmts.h:4, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/sched.h:9, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/mm.h:4, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/slab.h:14, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/proc_fs.h:5, from init/main.c:15: /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/string.h:16: warning: conflicting types for built-in function `memcpy' /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/string.h:26: warning: conflicting types for built-in function `memset' In file included from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/fs.h:23, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/capability.h:17, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/binfmts.h:4, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/sched.h:9, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/mm.h:4, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/slab.h:14, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/proc_fs.h:5, from init/main.c:15: /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/string.h:80: warning: conflicting types for built-in function `memcmp' In file included from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda_fs_i.h:14, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/fs.h:312, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/capability.h:17, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/binfmts.h:4, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/sched.h:9, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/mm.h:4, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/slab.h:14, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/proc_fs.h:5, from init/main.c:15: /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:259: parse error before `u_quad_t' /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:259: warning: no semicolon at end of struct or union /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:267: parse error before `va_bytes' /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:267: warning: type defaults to `int' in declaration of `va_bytes' /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:267: warning: data definition has no type or storage class /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:268: parse error before `va_filerev' /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:268: warning: type defaults to `int' in declaration of `va_filerev' /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:268: warning: data definition has no type or storage class /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:435: field `attr' has incomplete type /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:443: field `attr' has incomplete type /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:485: field `attr' has incomplete type /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:494: field `attr' has incomplete type /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:539: field `attr' has incomplete type /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:546: field `attr' has incomplete type /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/coda.h:566: field `attr' has incomplete type In file included from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/pgalloc.h:20, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/highmem.h:5, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/pagemap.h:16, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/locks.h:8, from /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/linux/blk.h:5, from init/main.c:25: /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/proc/cache.h: In function `flush_page_to_ram': /home/zoobab/soft/uclinux/uClinux-dist/linux-2.4.x/include/asm/proc/cache.h:60: warning: implicit declaration of function `__phys_to_virt' init/main.c: In function `start_kernel': init/main.c:448: warning: implicit declaration of function `__virt_to_phys' make: *** [init/main.o] Error 1 Any body has some time to help? I am on IRC, I have a put a mibbit plugin for people to join: http://isl3893.wikidot.com/irc I will try tomorrow to get JTAG working and to setup a free router where you could load your images online. I am online if you want to talk. See ya, -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 |
|
From: Fathi K. Z. <fa...@sn...> - 2008-04-07 07:51:34
|
Sorry again, For rt73 wifi usb, >Inside http://homepages.tu-darmstadt.de/~p_larbig/wlan/rt73-k2wrlz->2.0.1.tar.bz2 . >For use my rt73 wifi usb, I change: >1. file rtmp.h - I change the line #include <linux/kthread.h> to #include ><linux/threads.h> 2. file rtmp_main.c - I commented out the line >pAd->>net_dev->weight = 64; 3. Makefile O_TARGET := rt73.o #export-objs := vfatfs_syms.o EXTRA_CFLAGS += -I. EXTRA_CFLAGS += -DRTMP_EMBEDDED -DAGGREGATION_SUPPORT -DWMM_SUPPORT EXTRA_CFLAGS += -mstructure-size-boundary=8 obj-y := rtmp_main.o mlme.o connect.o rtusb_bulk.o rtusb_io.o sync.o assoc.o auth.o auth_rsp.o rtusb_data.o rtmp_init.o sanity.o rtmp_wep.o rtmp_info.o rtmp_tkip.o wpa.o md5.o obj-m := $(O_TARGET) include $(TOPDIR)/Rules.make and some other changes in Config.in and Makefile inside parent dir. >I can compile and use it right now when looking >extra interface (rausb0), but I haven't go any further than that. What I >know only I can't ping others while successfully associates to the AP. I >don't know if above are not the right ways. Noted, in my Ubuntu 2.6.x, I >see it is using kernel thread by looking into process view, it shows >'[rt73]'. |
|
From: Fathi K. Z. <fa...@sn...> - 2008-04-07 07:31:08
|
Correction: >Inside http://homepages.tu-darmstadt.de/~p_larbig/wlan/rt73-k2wrlz->2.0.1.tar.bz2 . >For use my rt73 wifi usb, I change: >1. file rtmp.h - I change the line #include <linux/kthread.h> to #include ><linux/threads.h> 2. file rtmp_main.c - I commented out the line pAd->>net_dev->weight = 64; I can compile and use it right now when looking >extra interface (rausb0), but I haven't go any further than that. What I >know only I can ping others while successfully associates to the AP. I >don't know if above are not the right ways. Noted, in my Ubuntu 2.6.x, I >see it is using kernel thread by looking into process view, it shows >'[rt73]'. What I know only I can't ping others while successfully associates to the AP Thanks -----Original Message----- From: isl...@li... [mailto:isl...@li...] On Behalf Of Fathi Kamil Zainuddin Sent: Monday, April 07, 2008 3:25 PM To: 'ulf kypke'; 'Ruben Faelens' Cc: isl...@li... Subject: Re: [Isl3893-devel] ZCOM XG-2000 USB Access Point Hi again, Thanks. Yes I am from Malaysia. Nice to meet you too. People in Malaysia are not go in deep into computer engineering with Linux very much but I am willing to do. =) Lately, I'm busy with my work. Not much progress in hacking isl3893. 1. I see the similarity between isl3893 and prism54 (isl3890) in the source code (drivers/net/intersil/). The OIB registers are almost the same. I think the management part is done in MVC. That's why somebody called them Firmware AP (referring to isl3890). Comparing between both isl3890 firmware and the isl3893 MVC, I started to think the MVC is just like a firmware and they communicate by using OID referring to mvc2 blob header, correct me if I am wrong. I realized that the current MVC doesn't support IW_MODE_MONITOR when I check into the mvc2 header files and compare between prism54 source code and 'strings' the MVC (not mentioned about IW_MODE_MONITOR). Prism54/isl3890 firmware support OID_INL_MODE = 0xFF020003 and OID_INL_CONFIG = 0xFF020008 while isl3893 doesn't for monitor mode. 2. What is the MVC latest version for isl3893? Mine is 1.0.1.0. And where can I get the MVC latest version? >> I've test it with my rt2571/rt73 wireless >> USB. It seems that the kernel version missing net_device->weight (it is >>set >> to 64 ? ttl ?) and I just commented it with '//' cause I'm not a kernel >where? Inside http://homepages.tu-darmstadt.de/~p_larbig/wlan/rt73-k2wrlz-2.0.1.tar.bz2 . For use my rt73 wifi usb, I change: 1. file rtmp.h - I change the line #include <linux/kthread.h> to #include <linux/threads.h> 2. file rtmp_main.c - I commented out the line pAd->net_dev->weight = 64; I can compile and use it right now when looking extra interface (rausb0), but I haven't go any further than that. What I know only I can ping others while successfully associates to the AP. I don't know if above are not the right ways. Noted, in my Ubuntu 2.6.x, I see it is using kernel thread by looking into process view, it shows '[rt73]'. >what do you mean? >you build a firmware and flash it on the device, you have max. 4 mb of >flash size. >or do you mean, that you now have an image, that is too big for the >flash event, because it stops with flashsize exceeded? for this you >should search the mailing list. I have a 4MB flash memory. But I want to allocate the size of the cramfs partition to 1.5MB max, so the rest 2.5MB I can use the space for jffs partition. I don't know what the impact is if I change the size inside 'make menuconfig' in uClinux path or I have to do some other extra works. Hi Ruben, Glad for replying my e-mail. >Did you read my site, http://student.kuleuven.be/~s0169612/isl3893.html >? I think some questions are answered there. Thanks a lot for the link. Before this I tried to use my own way without guidance. I will take it as references. >Could you post a little log of what you did EXACTLY? This could be very >useful information... Sorry, I never realize there was a 'make menuconfig' command inside uClinux path Excerpt from my site: > Some people who have built the kernel image this way have been having > "cramfs: wrong magic" error. This is because the kernel also tries to > mount a cramfs partition. It starts with E=.(, but you should search > for the string Compressed ROMFS and then substract 16 bytes from the > offset. My cramfs image was at offset 0x18F200. You can extract it > with cramfsck. It is just a minor file which contains space for extra > modules which should be loaded on boot. So before you bunzip, you > should cut that part of the file, and then re-add it when making your > own firmware. Thanks a lot. I will try this. Thanks guys. -----Original Message----- From: ulf kypke [mailto:u....@gm...] Sent: Friday, April 04, 2008 7:13 PM To: Fathi Kamil Zainuddin Subject: Re: [Isl3893-devel] ZCOM XG-2000 USB Access Point 2008/4/4, Fathi Kamil Zainuddin <fa...@sn...>: > Thanks Ulf for the quick answers. > > Sorry for my mistakes. =) I realized there is a command 'make menuconfig' > under uClinux folder last night because it didn't show when I type 'make' to yes in uClinux you make a makemenuconfig and you can do this as well in uClinux/kernel to define kernel settings (nfs, ipip, ipv6, wireless ext., usb, scsi driver, etc.) > show the options. I have tested wireless extension patches provided by > isl3893.sf.net and I stole iwconfig binary (it's static) from apfw-minimal > firmware using fw extractor =). i am almost finished with a ready to go toolchain, patch and software packages so you just need some tar.gz files and do some steps (i am writing my diploma paper about wireless embedded devices) I've test it with my rt2571/rt73 wireless > USB. It seems that the kernel version missing net_device->weight (it is set > to 64 ? ttl ?) and I just commented it with '//' cause I'm not a kernel where? > programmer, I don't know how to debug everything and don't have guidance on > kernel documentation. I added a line '#define IW_MODE_MONITOR 6' in > linux/wireless.h, i am not a kernel dev. as well, but yes why not. I don't know if this is a correct way or there must have > some additional code. Right now, I can use my wireless usb and turn into > monitor mode (I never test it with tcpdump yet) but I can't ping others in > managed mode with WEP enable. wep you can do out of the box with setoid wpa you need wpa supplicant, check the wet54gs v2 sources from linksys. tcpdump would be great, but libpthread is a problem with the old uclibc source in the tarball. for example for olsrd i needed to ad the lib math which was not included. > > 1. Is the mlme part is done inside MVC or inside the driver? I just want to > confirm if it's done in MVC because of the OID. i dont know, i stuck with the mlme stuff as well > 2. Can I reduce the size of the APFW? So I can use the rest for jffs. what do you mean? you build a firmware and flash it on the device, you have max. 4 mb of flash size. or do you mean, that you now have an image, that is too big for the flash event, because it stops with flashsize exceeded? for this you should search the mailing list. the deal is, that while booting the image the flashpartition is defined. so you create a small image <1.5mb and in this settings you define the flash size for. after flashing, you start again, with the now size and flash the big file. default the size is defined to 2mb flash size but some routers have 4mb flash. and you can use nfs to mount more space, or even an usb stick ;-) so have fun, with some hacking and warm greeting from germany. ps. where are you? from malaysia? > > > Thanks in advance. > > > -----Original Message----- > From: ulf kypke [mailto:u....@gm...] > Sent: Friday, April 04, 2008 3:02 PM > To: Fathi Kamil Zainuddin > Subject: Re: [Isl3893-devel] ZCOM XG-2000 USB Access Point > > 2008/4/3, Fathi Kamil Zainuddin <fa...@sn...>: > > Hi great guys, > > > > I've got a ZCOM XG-2000 AP with USB which is using isl3893 chipset > inside, > > flash 4MB and memory 16MB. I already compiled everything together with > > patches provided by isl3893.sf.net (but no wireless extension yet. I just > > tried it last night). Thanks, I can connect several usb device on usb hub > > connected to my AP. I found that there are a lot of problems when > compiling > > with the source code comes from Siemens website. I have 4 questions here: > > > > 1. Is there other better source code which I can download without fixing > so > > much compile bug? I changed everywhere for firmware size and packages > > selection until it success when I directly change the appbuild/dirs.mk, > > rockhopper.h & flash_layout.h files. > i was using the fujitsu siemens source, they had the newest mvc at that time > > > > 2. Is there any way to fix the 'cramfs wrong magic' warning message > during > > booting? I think it is used to mount kernel modules path. > i have not found any fix for that > > > > > 3. Is there any possibility to change wireless mode to monitor mode thus > > support raw packet transmission? > > ohhh good question. well to use the wireless in other ways, like you > want, i never did any hacks with success. but you can change the mode > from master (accesspoint mode) to any other. > first you need the wireless ext. in your build, i added the iwconfig > tools to my apps-gpl. > > in some c file under kernel driver net wireless intersil..... there > is some code for default start mode for the driver > you need to change MODE_AP to MODE_CLIENT > then you can use getoid eth1 0x10000000 long x > x is 0 auto > 1 managed > 2 adhoc > > in mode 1 you can switch from mode client to mode ap with iwconfig > there is a scan funktion with getoid eth1 0x1c000043 bsslist > most of the oids are defined on mvc2 bolb.2 in include directory. > > > > > > 4. Is there any working on reverse-engineering isl3893 MVC other than > > freemac? I don't see how if freemac can be used as a change of the > current > > MVC going to work. Using OID is too obvious. > no but, this you have to ask sebastien > > > > 5. I've heard that team isl3893.wikidot.com created a firmware based on > > OpenWRT. Any references on it? > > well, you said four questions.... ;-) > no this architecture is not supported jet in openwrt, the whole > guildroot is very old and we have a nommu system, openwrt developers > hate no mmu systemes ;-) > and is (for me) almost inpossible to upgrade the kernel from 2.4.19 to 2.6.x > but if you have the skills to to that, feel free to do so. > > > > > > Thanks for the answers. > you are very welcome > regards ulf kypke > > > > > > Fatah > > IT Security Consultant > > > > Reference: > > http://fatah.afraid.org/files/apfw-minimal-usb.img > > > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne _______________________________________________ Isl3893-devel mailing list Isl...@li... https://lists.sourceforge.net/lists/listinfo/isl3893-devel |
|
From: Fathi K. Z. <fa...@sn...> - 2008-04-07 07:26:27
|
Hi again, Thanks. Yes I am from Malaysia. Nice to meet you too. People in Malaysia are not go in deep into computer engineering with Linux very much but I am willing to do. =) Lately, I'm busy with my work. Not much progress in hacking isl3893. 1. I see the similarity between isl3893 and prism54 (isl3890) in the source code (drivers/net/intersil/). The OIB registers are almost the same. I think the management part is done in MVC. That's why somebody called them Firmware AP (referring to isl3890). Comparing between both isl3890 firmware and the isl3893 MVC, I started to think the MVC is just like a firmware and they communicate by using OID referring to mvc2 blob header, correct me if I am wrong. I realized that the current MVC doesn't support IW_MODE_MONITOR when I check into the mvc2 header files and compare between prism54 source code and 'strings' the MVC (not mentioned about IW_MODE_MONITOR). Prism54/isl3890 firmware support OID_INL_MODE = 0xFF020003 and OID_INL_CONFIG = 0xFF020008 while isl3893 doesn't for monitor mode. 2. What is the MVC latest version for isl3893? Mine is 1.0.1.0. And where can I get the MVC latest version? >> I've test it with my rt2571/rt73 wireless >> USB. It seems that the kernel version missing net_device->weight (it is >>set >> to 64 ? ttl ?) and I just commented it with '//' cause I'm not a kernel >where? Inside http://homepages.tu-darmstadt.de/~p_larbig/wlan/rt73-k2wrlz-2.0.1.tar.bz2 . For use my rt73 wifi usb, I change: 1. file rtmp.h - I change the line #include <linux/kthread.h> to #include <linux/threads.h> 2. file rtmp_main.c - I commented out the line pAd->net_dev->weight = 64; I can compile and use it right now when looking extra interface (rausb0), but I haven't go any further than that. What I know only I can ping others while successfully associates to the AP. I don't know if above are not the right ways. Noted, in my Ubuntu 2.6.x, I see it is using kernel thread by looking into process view, it shows '[rt73]'. >what do you mean? >you build a firmware and flash it on the device, you have max. 4 mb of >flash size. >or do you mean, that you now have an image, that is too big for the >flash event, because it stops with flashsize exceeded? for this you >should search the mailing list. I have a 4MB flash memory. But I want to allocate the size of the cramfs partition to 1.5MB max, so the rest 2.5MB I can use the space for jffs partition. I don't know what the impact is if I change the size inside 'make menuconfig' in uClinux path or I have to do some other extra works. Hi Ruben, Glad for replying my e-mail. >Did you read my site, http://student.kuleuven.be/~s0169612/isl3893.html >? I think some questions are answered there. Thanks a lot for the link. Before this I tried to use my own way without guidance. I will take it as references. >Could you post a little log of what you did EXACTLY? This could be very >useful information... Sorry, I never realize there was a 'make menuconfig' command inside uClinux path Excerpt from my site: > Some people who have built the kernel image this way have been having > "cramfs: wrong magic" error. This is because the kernel also tries to > mount a cramfs partition. It starts with E=.(, but you should search > for the string Compressed ROMFS and then substract 16 bytes from the > offset. My cramfs image was at offset 0x18F200. You can extract it > with cramfsck. It is just a minor file which contains space for extra > modules which should be loaded on boot. So before you bunzip, you > should cut that part of the file, and then re-add it when making your > own firmware. Thanks a lot. I will try this. Thanks guys. -----Original Message----- From: ulf kypke [mailto:u....@gm...] Sent: Friday, April 04, 2008 7:13 PM To: Fathi Kamil Zainuddin Subject: Re: [Isl3893-devel] ZCOM XG-2000 USB Access Point 2008/4/4, Fathi Kamil Zainuddin <fa...@sn...>: > Thanks Ulf for the quick answers. > > Sorry for my mistakes. =) I realized there is a command 'make menuconfig' > under uClinux folder last night because it didn't show when I type 'make' to yes in uClinux you make a makemenuconfig and you can do this as well in uClinux/kernel to define kernel settings (nfs, ipip, ipv6, wireless ext., usb, scsi driver, etc.) > show the options. I have tested wireless extension patches provided by > isl3893.sf.net and I stole iwconfig binary (it's static) from apfw-minimal > firmware using fw extractor =). i am almost finished with a ready to go toolchain, patch and software packages so you just need some tar.gz files and do some steps (i am writing my diploma paper about wireless embedded devices) I've test it with my rt2571/rt73 wireless > USB. It seems that the kernel version missing net_device->weight (it is set > to 64 ? ttl ?) and I just commented it with '//' cause I'm not a kernel where? > programmer, I don't know how to debug everything and don't have guidance on > kernel documentation. I added a line '#define IW_MODE_MONITOR 6' in > linux/wireless.h, i am not a kernel dev. as well, but yes why not. I don't know if this is a correct way or there must have > some additional code. Right now, I can use my wireless usb and turn into > monitor mode (I never test it with tcpdump yet) but I can't ping others in > managed mode with WEP enable. wep you can do out of the box with setoid wpa you need wpa supplicant, check the wet54gs v2 sources from linksys. tcpdump would be great, but libpthread is a problem with the old uclibc source in the tarball. for example for olsrd i needed to ad the lib math which was not included. > > 1. Is the mlme part is done inside MVC or inside the driver? I just want to > confirm if it's done in MVC because of the OID. i dont know, i stuck with the mlme stuff as well > 2. Can I reduce the size of the APFW? So I can use the rest for jffs. what do you mean? you build a firmware and flash it on the device, you have max. 4 mb of flash size. or do you mean, that you now have an image, that is too big for the flash event, because it stops with flashsize exceeded? for this you should search the mailing list. the deal is, that while booting the image the flashpartition is defined. so you create a small image <1.5mb and in this settings you define the flash size for. after flashing, you start again, with the now size and flash the big file. default the size is defined to 2mb flash size but some routers have 4mb flash. and you can use nfs to mount more space, or even an usb stick ;-) so have fun, with some hacking and warm greeting from germany. ps. where are you? from malaysia? > > > Thanks in advance. > > > -----Original Message----- > From: ulf kypke [mailto:u....@gm...] > Sent: Friday, April 04, 2008 3:02 PM > To: Fathi Kamil Zainuddin > Subject: Re: [Isl3893-devel] ZCOM XG-2000 USB Access Point > > 2008/4/3, Fathi Kamil Zainuddin <fa...@sn...>: > > Hi great guys, > > > > I've got a ZCOM XG-2000 AP with USB which is using isl3893 chipset > inside, > > flash 4MB and memory 16MB. I already compiled everything together with > > patches provided by isl3893.sf.net (but no wireless extension yet. I just > > tried it last night). Thanks, I can connect several usb device on usb hub > > connected to my AP. I found that there are a lot of problems when > compiling > > with the source code comes from Siemens website. I have 4 questions here: > > > > 1. Is there other better source code which I can download without fixing > so > > much compile bug? I changed everywhere for firmware size and packages > > selection until it success when I directly change the appbuild/dirs.mk, > > rockhopper.h & flash_layout.h files. > i was using the fujitsu siemens source, they had the newest mvc at that time > > > > 2. Is there any way to fix the 'cramfs wrong magic' warning message > during > > booting? I think it is used to mount kernel modules path. > i have not found any fix for that > > > > > 3. Is there any possibility to change wireless mode to monitor mode thus > > support raw packet transmission? > > ohhh good question. well to use the wireless in other ways, like you > want, i never did any hacks with success. but you can change the mode > from master (accesspoint mode) to any other. > first you need the wireless ext. in your build, i added the iwconfig > tools to my apps-gpl. > > in some c file under kernel driver net wireless intersil..... there > is some code for default start mode for the driver > you need to change MODE_AP to MODE_CLIENT > then you can use getoid eth1 0x10000000 long x > x is 0 auto > 1 managed > 2 adhoc > > in mode 1 you can switch from mode client to mode ap with iwconfig > there is a scan funktion with getoid eth1 0x1c000043 bsslist > most of the oids are defined on mvc2 bolb.2 in include directory. > > > > > > 4. Is there any working on reverse-engineering isl3893 MVC other than > > freemac? I don't see how if freemac can be used as a change of the > current > > MVC going to work. Using OID is too obvious. > no but, this you have to ask sebastien > > > > 5. I've heard that team isl3893.wikidot.com created a firmware based on > > OpenWRT. Any references on it? > > well, you said four questions.... ;-) > no this architecture is not supported jet in openwrt, the whole > guildroot is very old and we have a nommu system, openwrt developers > hate no mmu systemes ;-) > and is (for me) almost inpossible to upgrade the kernel from 2.4.19 to 2.6.x > but if you have the skills to to that, feel free to do so. > > > > > > Thanks for the answers. > you are very welcome > regards ulf kypke > > > > > > Fatah > > IT Security Consultant > > > > Reference: > > http://fatah.afraid.org/files/apfw-minimal-usb.img > > > |
|
From: Ruben F. <par...@gm...> - 2008-04-06 18:56:16
|
Fathi Kamil Zainuddin schreef: > Hi great guys, > > I've got a ZCOM XG-2000 AP with USB which is using isl3893 chipset > inside, flash 4MB and memory 16MB. I already compiled everything > together with patches provided by isl3893.sf.net (but no wireless > extension yet. I just tried it last night). Thanks, I can connect > several usb device on usb hub connected to my AP. I found that there > are a lot of problems when compiling with the source code comes from > Siemens website. I have 4 questions here: Did you read my site, http://student.kuleuven.be/~s0169612/isl3893.html ? I think some questions are answered there. > > 1. Is there other better source code which I can download without > fixing so much compile bug? I changed everywhere for firmware size > and packages selection until it success when I directly change the > appbuild/dirs.mk, rockhopper.h & flash_layout.h files. Could you post a little log of what you did EXACTLY? This could be very useful information... http://student.kuleuven.be/~s0169612/isl3893.html#compiling-from-source -> Firmware from linksys is pretty well kept and compiles without any issues. > > 2. Is there any way to fix the 'cramfs wrong magic' warning message > during booting? I think it is used to mount kernel modules path. Excerpt from my site: > Some people who have built the kernel image this way have been having > "cramfs: wrong magic" error. This is because the kernel also tries to > mount a cramfs partition. It starts with E=.(, but you should search > for the string Compressed ROMFS and then substract 16 bytes from the > offset. My cramfs image was at offset 0x18F200. You can extract it > with cramfsck. It is just a minor file which contains space for extra > modules which should be loaded on boot. So before you bunzip, you > should cut that part of the file, and then re-add it when making your > own firmware. > > 3. Is there any possibility to change wireless mode to monitor mode > thus support raw packet transmission? Don't know, good luck with that... > > 4. Is there any working on reverse-engineering isl3893 MVC other than > freemac? I don't see how if freemac can be used as a change of the > current MVC going to work. Using OID is too obvious. When I first joined in on isl3893-devel, there were high hopes of using the freemac source to create a replacement open-source MVC. However, freemac didn't progress fast enough, and isl3893 died before we could use the work provided in freemac. The isl3893 is not a popular chipset anymore; everyone uses OpenWRT on linksys-based devices these days. Anyone who would like to try bypassing the MVC, trying direct hardware access is more than welcome! I don't have the know-how or the time to learn. > > 5. I've heard that team isl3893.wikidot.com created a firmware based > on OpenWRT. Any references on it? First thing I hear about this! I know there was a workshop planned at CCC in december 2007, but http://isl3893.wikidot.com/openwrt is all that remains. Anyone can contact Benjamin Henrion? |
|
From: Fathi K. Z. <fa...@sn...> - 2008-04-03 08:49:41
|
Hi great guys, I've got a ZCOM XG-2000 AP with USB which is using isl3893 chipset inside, flash 4MB and memory 16MB. I already compiled everything together with patches provided by isl3893.sf.net (but no wireless extension yet. I just tried it last night). Thanks, I can connect several usb device on usb hub connected to my AP. I found that there are a lot of problems when compiling with the source code comes from Siemens website. I have 4 questions here: 1. Is there other better source code which I can download without fixing so much compile bug? I changed everywhere for firmware size and packages selection until it success when I directly change the appbuild/dirs.mk, rockhopper.h & flash_layout.h files. 2. Is there any way to fix the 'cramfs wrong magic' warning message during booting? I think it is used to mount kernel modules path. 3. Is there any possibility to change wireless mode to monitor mode thus support raw packet transmission? 4. Is there any working on reverse-engineering isl3893 MVC other than freemac? I don't see how if freemac can be used as a change of the current MVC going to work. Using OID is too obvious. 5. I've heard that team isl3893.wikidot.com created a firmware based on OpenWRT. Any references on it? Thanks for the answers. Fatah IT Security Consultant Reference: http://fatah.afraid.org/files/apfw-minimal-usb.img |
|
From: Gene S. <gd...@ch...> - 2008-02-15 04:55:57
|
Benjamin Henrion wrote, On 02/14/2008 08:16 PM: > On Fri, Feb 15, 2008 at 1:17 AM, gds <gd...@ch...> wrote: >> Benjamin Henrion wrote: > > Do you have the FCC-ID and/or pictures of the board for version3? > > The best way is to open it and find out which SoC and OS it runs. Just saw this page on the Linksys website which references version 3: http://tinyurl.com/39orn5 |
5 messages has been excluded from this view by a project administrator.