**** BEGIN LOGGING AT Tue Jul 24 02:59:57 2007 Jul 24 03:03:26 sn9: if the device is up, the voltage there floats around (think it's looks like these because my multimeter can't measure at such i high voltage) and it's at about 300kHz. there are some short moments where there is nothing on the pin Jul 24 03:11:31 i think you're supposed to pull it high to enable jtag Jul 24 03:13:11 sn9: hmmm, ok, could you lease count the pins too? don't want to pull the wrong pin high :D -> http://openwrt.vcp-springe.de/wl-153/100_3521.jpg Jul 24 03:15:57 check the datasheet to verify first; i haven't Jul 24 03:16:57 sn9: i have, it's pin 40 Jul 24 03:17:08 on the ar525w, pin 40 goes under the ram chip, so i can't trace it easily, but the ohmeter shows it goes to one of the pins on the ram chip Jul 24 03:20:58 it is the one marked in yellow in the photo Jul 24 03:22:58 sn9: yellow? which photo? Jul 24 03:23:19 http://openwrt.vcp-springe.de/wl-153/100_3521.jpg Jul 24 03:23:57 sn9: you mean my probe? Jul 24 03:24:29 it's hard to tell what that is; the lighting is awful Jul 24 03:29:23 sn9: http://www.order.conrad.com/xl/1000_1999/1200/1220/1221/122182_AB_00_FB.EPS.jpg nice things they are, but i only have two :/ Jul 24 03:44:01 sn9: think i'll try the jtag stuff again later, it's nearly 6am here - time for some sleep :) Jul 24 04:58:03 <[mbm]> sn9: interesting; sounds almost exactly identical Jul 24 05:00:36 [mbm]: you still didn't say which fry's it was at Jul 24 05:00:53 <[mbm]> think it was the one over near sunnyvale Jul 24 05:01:13 on arques? Jul 24 05:01:31 <[mbm]> yep Jul 24 05:02:04 <[mbm]> hmm serial pinout and console output seems to match the posts near the end of the thread Jul 24 05:02:35 i gotta remember to check that one. $70 including hard disk, eh? Jul 24 05:03:30 <[mbm]> no disk, just an enclosure Jul 24 05:03:40 3.5"? Jul 24 05:03:46 <[mbm]> yep Jul 24 05:03:55 unbelievable Jul 24 05:04:20 <[mbm]> not much on looks Jul 24 05:04:59 one doesn't have to overpay on the hd just because it's already in an enclosure Jul 24 05:07:00 <[mbm]> there's room for one drive internally, but I see no reason why you couldn't plug in both ide and sata drives Jul 24 05:07:41 <[mbm]> also two usb ports on it, with a button that claims to dump the contents of the usb to the internal disk Jul 24 05:10:11 the sata could be esata, too, i bet Jul 24 05:10:28 <[mbm]> probably could be used that way Jul 24 05:11:01 <[mbm]> there's also a spot on the board for a minipci card, although it's missing some components Jul 24 05:11:33 for wifi? it doesn't have wifi? Jul 24 05:11:51 <[mbm]> it doesn't, but it looks like the firmware might include some wifi capability Jul 24 05:12:19 then the asus wl-700gE still has something over it Jul 24 05:14:35 <[mbm]> just need to figuer out who made the original board and see if some details can be tracked down Jul 24 05:14:54 what does it say on the board? Jul 24 05:15:25 <[mbm]> hmm .. don't remember seeing any names on the board itself Jul 24 05:15:53 surely, there are some kind of markings... Jul 24 05:20:49 <[mbm]> just looked again, nothing particularly interesting, just labeling of components and connectors Jul 24 05:21:59 no string of alphanumeric digits anywhere? Jul 24 05:26:20 <[mbm]> no identifiers printed on the board beyond component placement Jul 24 05:26:32 <[mbm]> sticker with a barcode on the backside Jul 24 05:26:38 hmm Jul 24 05:26:55 does the fcc id yield any clues? Jul 24 05:27:18 <[mbm]> no radio, probably doesn't even have an fcc id Jul 24 05:27:31 look on the label on the case Jul 24 05:29:00 <[mbm]> hmm what'd I do with the case .. Jul 24 05:29:57 <[mbm]> nope; label is pretty bare.. model, serial, mac .. made in china, input voltage .. Jul 24 05:30:09 <[mbm]> in an oversized and ugly font Jul 24 05:31:45 <[mbm]> let's see .. chances are that the same board is available from another vendor, but with a wifi card Jul 24 05:31:59 * [mbm] looks to see what model appeared in the thread Jul 24 05:32:34 same board does not mean same firmware Jul 24 05:32:52 <[mbm]> true, and I did dump the flash chip Jul 24 05:35:26 can you determine the firmware's entry point? Jul 24 05:36:35 <[mbm]> not easily, the kernel on the flash has been stripped of elf headers Jul 24 05:37:07 on the ar525w, the redboot partition begins 128k before the end Jul 24 05:37:26 <[mbm]> what exactly did you have in mind anyway? Jul 24 05:38:15 cataloguing the differences among rdc devices to broaden support in the port Jul 24 05:39:43 crazy_imp's device is intriguing, because it looks supportable despite 2MB flash/8MB ram Jul 24 05:41:33 but on his device, jtag is the only way to get a dump, because part of the chip is left inaccessible via mtd block devices Jul 24 05:41:59 <[mbm]> on this they made it trivial, they did the entire flash as a single mtdblock Jul 24 05:42:11 and that part likely contains at least part of redboot Jul 24 05:42:23 <[mbm]> there's no sign of redboot on this Jul 24 05:42:24 no, not the _entire_ flash Jul 24 05:42:45 oh, you mean on your device Jul 24 05:42:55 <[mbm]> this = mine Jul 24 05:42:57 <[mbm]> :P Jul 24 05:44:14 <[mbm]> bootup looks pretty similar to http://forum.openwrt.org/viewtopic.php?pid=35637#p35637 .. same build host, same kernel version .. mine has a slightly newer compile of the kernel which includes an lzma ramdisk, but the userspace looks pretty similar Jul 24 05:44:48 <[mbm]> clearly both firmwares came from the sam source Jul 24 05:44:53 <[mbm]> same Jul 24 05:46:41 <[mbm]> there is something called mnBIOS at the end of my flash dump Jul 24 05:47:38 there was speculation in the thread that it mimics a pc bios Jul 24 05:47:42 <[mbm]> with oddly marked sections "RTC BEGIN" "RTC END" "VIDEO BEGIN" "VIDEO END" .. etc Jul 24 05:47:57 tried sending a GPL violation notice to airlink? Jul 24 05:48:44 <[mbm]> I'll poke some people about it Jul 24 05:49:08 Bartman007: believe me, you don't want to deal with that where airlink101 is concerned Jul 24 05:49:29 sn9: never dealt with them, figured it was worth mentioning. Jul 24 05:50:07 <[mbm]> sections mentioned above are TABLE, POST, CHIPSET, RTC, SIO, VIDEO, INTS, KBD, MESSAGE, DOC Jul 24 05:50:18 they apparently don't consider shipping a firmware inside a device to be "software distribution" unless it was downloaded from their website Jul 24 05:50:53 sn9: they do have a firmware update for "Vista compatability and 500GB drives" on their website. Jul 24 05:51:25 that's less than half the battle Jul 24 05:51:35 <[mbm]> it's hard to say where the sources got dropped, I'd like to know who originally did the board, and it looks like amit.com.tw was involved Jul 24 05:52:02 [mbm]: know how to say GPL violation in chinese? Jul 24 05:53:05 the only gpl source they ever released for anything was the ar525w tarball for one of the three versions of the ar525w firmware they released, and it was mostly .o files Jul 24 05:53:08 <[mbm]> looks like this is an MGB111 from http://www.amit.com.tw/HomeEntertainment.html Jul 24 05:55:43 was the model anas250 or anas350? Jul 24 05:55:51 <[mbm]> this is a 350 Jul 24 05:56:18 i wonder what's different in the 250 Jul 24 05:57:32 Bartman007: there's no vista download for the 350. where did you see that? Jul 24 05:57:41 <[mbm]> you have to google for it Jul 24 05:57:47 <[mbm]> I know the link bartman is talking about Jul 24 05:57:51 lovely... Jul 24 05:57:53 sn9: on their support site. Jul 24 05:58:19 <[mbm]> http://www.airlink101.com/support/index.php?cmd=files&id=105 Jul 24 05:59:15 http://www.airlink101.com/support/index.php?cmd=announcements&_a=viewannouncement&id=19 Jul 24 06:00:29 <[mbm]> poking at the SMC site now, looks like they have a newer firmware Jul 24 06:02:45 looks like the firmware gets pushed out over tftp Jul 24 06:03:32 <[mbm]> airlink has a wndows executable that does some discovery packet and then hits the http server Jul 24 06:03:59 i'm strings-ing it now Jul 24 06:04:45 <[mbm]> post on one of the forums said something about recovery mode if you hold down the buttons as you plug it in Jul 24 06:05:09 what does that show over serial? Jul 24 06:05:21 * [mbm] goes to try that Jul 24 06:06:48 interesting strings excerpt (long paste, but not too long) : Jul 24 06:07:00 default sequence of upgrade method used. Jul 24 06:07:00 HTTP upgrade method first used. Jul 24 06:07:00 FTP upgrade method first used. Jul 24 06:07:00 TFTP upgrade method first used. Jul 24 06:08:17 <[mbm]> Jon Recovery System Version J0.02 2005/05/05 Jul 24 06:08:20 <[mbm]> Flash chip AMD generic (7F-22F6), addr 0xFFC00000, size 0x400000 Jul 24 06:08:23 <[mbm]> IP=192.168.123.254 MASK=255.255.255.0 Jul 24 06:10:59 that address does appear in strings Jul 24 06:11:10 <[mbm]> seems to be running a webserver which spits out a page simply saying "Recovery Mode" with nothing else shown Jul 24 06:17:21 heh, the gpl-devices wiki has been hit by driveby linkspam. Jul 24 06:19:03 <[mbm]> you can't run any sort of user edited site these days without getting hit by spammers Jul 24 06:22:50 looks like mnBIOS is at the beginning of the smc image, not at the end Jul 24 06:23:13 the magic gets repeated at 0x4040 Jul 24 06:24:00 <[mbm]> think it's a modular update, and the modules aren't provided in the same order as they're written to flash Jul 24 06:24:27 they are compressed, too Jul 24 06:24:56 well, some of them Jul 24 06:26:39 <[mbm]> I expect the ekrnel and ramdisk are compressed, anything else? Jul 24 06:27:17 some kind of markup data Jul 24 06:28:00 <[mbm]> which section are you looking at? Jul 24 06:28:39 i think it was the second or third one Jul 24 06:32:27 apparently a filesystem near the end Jul 24 06:32:41 with more compressed stuff Jul 24 06:33:49 <[mbm]> there's a compressed ext2 ramdisk in there somewhere Jul 24 06:34:11 <[mbm]> not sure what offsets you're looking at Jul 24 06:36:26 [florian]: are you up yet? Jul 24 06:36:38 <[mbm]> oh, yeah, blatent filesystem at the end of the smc image Jul 24 06:36:56 <[mbm]> not compressed Jul 24 06:37:21 there's compressed javascript after the directory Jul 24 06:44:58 <[mbm]> ok, found the gzipped ext2 filesysten on the smc image Jul 24 06:45:05 <[mbm]> 0xFFA00 Jul 24 06:45:41 what do you expect to get out of that? Jul 24 06:45:55 <[mbm]> nothing, just trying to understand the packing Jul 24 06:46:18 <[mbm]> sections seem to be marked by "Queen" Jul 24 06:46:33 <[mbm]> prefixed by a model number Jul 24 06:47:27 <[mbm]> looks like hat header gets stripped before the section is written to flash Jul 24 06:47:46 of course Jul 24 06:50:02 * sn9 is gradually dozing off... Jul 24 06:51:10 <[mbm]> don't quire understand why the www stuff is outside the ext2 image Jul 24 07:05:19 noz: ping? Jul 24 07:53:45 <[florian]> sn9: yes, up and running Jul 24 08:56:06 <[florian]> sn9: what about you ? Jul 24 09:15:17 florian * r8139 / (2 files in 2 dirs): Fix the handling of unsupported ioctls (eth0 appeared in iwconfig for instance) Jul 24 10:56:34 sn9: should i pull strap11 up with 1.8v or 3.3v? Jul 24 10:58:39 florian * r8140 /trunk/package/ar7-atm/patches/ (3 files): Add ar7-atm fixes by DerAgo, also fix compilation (the use of dumb inlining in prototypes caused it to fail) Jul 24 11:05:20 florian * r8141 /trunk/target/linux/ar7-2.6/ (5 files in 4 dirs): Add more ar7 fixes by DerAgo. Fix vlnyq initialistion on fritzbox, add prom_printf required for kgdb, make kgbd finally work, thanks ! Jul 24 11:44:38 noz: ping Jul 24 13:58:00 nbd * r8142 /branches/whiterussian/openwrt/package/qos-scripts/files/usr/lib/qos/generate.sh: sync with kamikaze Jul 24 14:21:17 crazy_imp: i didn't realize there were any 1.8 lines on the board Jul 24 14:22:10 [florian]: no, i fell asleep Jul 24 14:22:45 sn9: there are at least 7 connected to the chip, named VCC_CORE Jul 24 14:23:01 sn9: and there is VCC_IO with 3.3v Jul 24 14:23:26 just lake a look at page 21 in the datasheet Jul 24 14:23:37 hmm. no clues in the datasheet? Jul 24 14:25:52 sn9: nothing :/. but it strap11 goes above 2v sometimes, so i think 3.3v should be ok Jul 24 14:26:13 ok Jul 24 14:26:27 you used 3.3v for your pin? Jul 24 14:26:49 or can you tell me on which level it is on your device? Jul 24 14:37:24 sn9: ah, great found a hint on page 22, "5V I/O Tolerant" -> Y Jul 24 14:38:45 i was gonna look at the datasheets again, but i don't remember which machine i downloaded them onto, and rdc seems to have removed them from their website Jul 24 14:43:02 sn9: huh? they got a new site while i was sleeping?..... :D Jul 24 14:43:44 apparently. all old url's are broken Jul 24 14:44:23 bleh, also with sound... Jul 24 14:56:13 crazy_imp: i've uploaded it to the wiki Jul 24 14:57:14 ok Jul 24 14:57:41 should i put a resistor between the 3.3v and strap11? Jul 24 15:04:36 Memory Address MA[12:7]. Normally, these pins are used as the row and column address for SDRAM. Jul 24 15:05:42 that would explain why it's connected to the ram chip on the ar525w Jul 24 15:07:45 <[florian]> sn9: I am back online, without the rdc board right now Jul 24 15:08:12 rwhitby: Had my nslu2 running wrt (kamikaze 7.07) over the weekend, it seemed to have died on me for some reason. Rebooted it and its fine. Jul 24 15:08:42 And silly me had not set it to write logs anywhere smart. Jul 24 15:09:33 sn9: do i need to pull up strap11 all the time while using jtag, think i need to do this, right? Jul 24 15:10:10 [florian]: i didn't see where you put the updated driver. did you try it? Jul 24 15:10:18 crazy_imp: i don't know Jul 24 15:11:16 rwhitby: Could be related to some usb-things i had in it, pl2303(usb to serial conv.) and bluetoothdongle. Jul 24 15:11:22 <[florian]> sn9: the updated driver is in trunk Jul 24 15:11:37 * sn9 looks Jul 24 15:11:49 <[florian]> sn9: I just put back the port priority stuff but had no time testing Jul 24 15:13:06 sn9: i'm going to give it a short run to see how much current flows there, hope i don't kill it Jul 24 15:13:37 datasheet says 16mA Jul 24 15:13:53 sn9: multimeter says 75mA - aua! Jul 24 15:15:21 sn9: which page says 16mA ? Jul 24 15:15:48 23 Jul 24 15:16:29 note 1, i see Jul 24 15:17:42 but i think it's changing something on the device, it doesn't light up the leds the way it normally does Jul 24 15:18:41 good, think it acts like a button to push one time :) Jul 24 15:21:07 [florian]: the way you put it back isn't making much sense to me yet, and the switch register activation is still not there Jul 24 15:21:40 in the old driver, the port priority was in response to an ioctl Jul 24 15:22:01 rwhitby: But there seems to be something strange with the whole usb "backend", unless I am the one broken. ;) Jul 24 15:25:26 <[florian]> sn9: it was a dumb ioctl command Jul 24 15:25:54 any idea when it was called? Jul 24 15:26:38 sn9: detect still shows nothing :( Jul 24 15:28:54 crazy_imp: using which pinout? mine or yours? Jul 24 15:29:16 sn9: my one Jul 24 15:29:31 if one doesn't work, try the other Jul 24 15:31:21 rwhitby: May be since I havent loaded u/o-hci, just ehci modules. Ill get back to you with more. Jul 24 15:31:55 <[florian]> sn9: what I added will be called when you ifup the device Jul 24 15:32:58 i noticed Jul 24 15:33:19 i asked when the ioctl was called in the old Jul 24 15:35:25 Any idea why I cant load kmod-usb-ohci, ipkg install gives me error when it tries to get the modules from another version of the kernel. Jul 24 15:35:57 The point is, there is one for my kernel version. But ipkg dont seem to want to dl that one. Jul 24 15:41:25 sn9: still the same..... lets exclude my wiggler from the list of possible failures - i'll try to jtag one of my wrt54g's Jul 24 15:41:40 ok Jul 24 15:44:50 sn9: btw, does jtag expect to have the trst line if i'm using wiggler as cable? Jul 24 15:45:24 oh, minor versions not a match. Feel free to ignore my rambelings. Guess rwhitby buildt a new one over the weekend. Jul 24 15:46:44 crazy_imp: not according to http://en.wikipedia.org/wiki/Jtag Jul 24 16:20:31 juhosg * r8143 / (3 files in 3 dirs): [adm5120] fix kernel command line Jul 24 16:31:28 sn9: my cable is fine -> http://pastebin.ca/632122 Jul 24 16:33:43 <[florian]> sn9: the ioctl was called anytime args was valid Jul 24 16:34:49 [florian]: i'm not so sure that would have happened with the switch registers activated. stand by for a replacement driver Jul 24 16:35:13 crazy_imp: verify that you can still get serial out of the device Jul 24 16:35:29 sn9: on the wl153? Jul 24 16:35:36 yes Jul 24 16:35:50 ok, wait a moment Jul 24 16:36:45 sn9: bad, need to turn it up side down, so i have to release my miniclips :/ Jul 24 16:41:34 sn9: it's still alive :) Jul 24 16:43:26 hmm Jul 24 16:43:28 bbs Jul 24 17:21:08 crazy_imp: the way i understand it, the pin should already be pulled high while power is first applied to the device Jul 24 17:22:06 sn9: ? so i should use an externel 3.3v source or is it ok with the internal one? Jul 24 17:22:34 "pulled high" == using an existing signal Jul 24 17:23:09 otherwise it's not relative to the same ground Jul 24 17:23:13 maybe the pin i used to get the 3.3v from gets turned on too late, i'll take a look for another 3.3v source (think i'll use the one i use to power the jtag) Jul 24 17:23:29 good idea Jul 24 17:23:50 use the one on the jtag header Jul 24 17:24:14 i would connect the ground from the externel one to the ground of the router (ran in some problems with gnd on other devices since then i obey the law :D) Jul 24 17:27:35 that would introduce unnecessary variables Jul 24 18:25:17 sn9: lets see, i soldered a wire to R66 (zero ohm to strap11), should be much easier to do the rest now Jul 24 18:40:14 * crazy_imp starts to hate the router Jul 24 18:52:46 wtf is the difference between a "zero ohm resistor" and a jumper wire? Jul 24 18:53:47 naah, you got me wrong, zero ohm connection to strap11, the resistor itself is 33ohm Jul 24 18:55:50 ok, but i've seen schematics before with resistors labeled "0R" Jul 24 18:56:02 [mbm]: could you try to jtag your wl-153 (think you have one too :) Jul 24 18:56:34 his rdc device is an AirLink101 ANAS350 Jul 24 18:56:59 sn9: hehe, think i have some devices here with zero ohm resistorbanks :D Jul 24 18:57:27 sn9: i know, but he should also have a wl-153 (at least he got one on the 23c3) Jul 24 18:57:48 23c3? Jul 24 18:58:33 sn9: 23. Chaos Communication Congress Jul 24 18:58:50 url? Jul 24 19:01:14 sn9: https://events.ccc.de/congress/2006/23rd_Chaos_Communication_Congress (but it doesn't load here at the moment) Jul 24 19:02:46 404 Jul 24 19:08:53 sn9: https://events.ccc.de/congress/2006/ Jul 24 19:28:33 ah, so it's the european version of defcon... Jul 24 19:36:06 <[florian]> sn9: ccc has been here for 23 year already Jul 24 19:37:07 the name did not jog my memory Jul 24 19:37:41 btw, i rebuilt the driver with the ioctl back in, and debug on, and it isn't getting called Jul 24 19:44:07 there must be something it needs from userspace Jul 24 19:46:55 <[florian]> sn9: usually you do this with ifconfig or ethtool Jul 24 19:52:32 i just loaded the stock firmware again to check. i was wrong -- eth0 _is_ wan Jul 24 19:52:43 if u guys are talking about what I think your talking about (joind half way through this) I put a printk in cpmac and tried to run miidiag and ethtool but nothing was output like the register read wasn't being called.... bit it was outputting some random ones Jul 24 19:53:38 Wipster: i'm not sure what u are talking about Jul 24 19:59:44 <[florian]> sn9: ok, I guess it is ther order the ports are registered Jul 24 20:28:23 juhosg * r8144 / (3 files in 3 dirs): [adm5120] reorder rootfstypes to allow both squashfs and jffs2 images to boot Jul 24 20:33:31 blogic * r8145 /trunk/target/linux/au1000-2.6/patches/ (015-pci-resource.patch 016-pci-io_map.patch): fixed up the au1000 pci support, was caused by the au1000 having a 36bit io bus and the max add being set to 32bit Jul 24 20:35:32 blogic * r8146 /trunk/target/linux/au1000-2.6/patches/015-pci-resource.patch: oops, wrong file for au1000 pci fix Jul 24 20:48:01 [florian]: in the stock firmware, a binary called "setPhy" uses the ioctl Jul 24 21:11:26 blogic * r8147 /trunk/target/linux/au1000-2.6/patches/014-au1000_eth_ioctl.patch: fixed au1000 eth0 ioctl patch Jul 24 21:28:54 <[florian]> sn9: no source with it ? Jul 24 21:29:44 just .o files Jul 24 21:31:12 <[florian]> sn9: if you want to do an ioctl with a user-space program, you can have a look at what is done with the admswconfig utility in trunk/package/admswconfig Jul 24 21:34:04 is there anything in base-files that might do it for testing? Jul 24 21:37:12 <[florian]> sn9: doubt so Jul 24 21:43:39 yay, think today we got the biggest #openwrt-devel log this year :D Jul 24 21:49:58 blogic * r8148 /tags/kamikaze_7.07/target/linux/au1000-2.6/patches/ (3 files): added the au1000 pci and eth0 fixes to the 7.07 tag Jul 24 22:10:06 blogic * r8149 /trunk/package/base-files/files/etc/init.d/network: wireless config gets regenerated not only when it does not exist, buit also if it is 0 len Jul 24 22:11:09 blogic * r8150 /tags/kamikaze_7.07/package/base-files/files/etc/init.d/network: wireless config gets regenerated not only when it does not exist, buit also if it is 0 len -- 7.07 tag Jul 24 22:40:20 blogic * r8151 /trunk/target/linux/au1000-2.6/patches/017-usb-power.patch: on the au1000 usb could never work as the power switch was never enabled :P Jul 24 22:52:08 blogic * r8152 /tags/kamikaze_7.07/target/linux/au1000-2.6/patches/017-usb-power.patch: on the au1000 usb could never work as the power switch was never enabled :P -- 7.07 Jul 24 23:04:35 gah! http://sfgate.com/cgi-bin/article.cgi?f=/c/a/2007/07/24/BAG9NR67253.DTL&tsp=1 Jul 24 23:09:23 sn9: why did it happend? Jul 24 23:10:43 not sure, but i lost power for eight hours or so llast week. i can't help but think it might be related Jul 24 23:12:23 one of the traffic lights the article mentions is less than two blocks away Jul 24 23:22:59 [mbm]: heyho Jul 24 23:25:28 <[mbm]> yo Jul 24 23:26:28 [mbm]: do you still the the wl-153? Jul 24 23:26:40 (think it was one, right?) Jul 24 23:26:47 <[mbm]> yeah but I haven't played with it much since 23c3 Jul 24 23:27:14 * crazy_imp thinks it's time to start :) Jul 24 23:27:27 <[mbm]> why, what have you got planned? Jul 24 23:27:50 <[mbm]> had serial hooked up to it, got a stupid login window if I remember right Jul 24 23:30:49 [mbm]: sn9 asked me for a dump from the flash because something is different compare to other devices, but i can't get jtag working :/. so i thought you might get jtag working :) Jul 24 23:31:43 <[mbm]> hmm not sure what I did with my jtag cable Jul 24 23:31:59 <[mbm]> wonder if it can be dumped over serial from the bootloader Jul 24 23:32:27 hmmm, true, i'll have a look later (playing gw atm :D) Jul 24 23:33:13 <[mbm]> btw do you remember what the power erquierments aer for the wl-153? it isn't marked on the unit Jul 24 23:34:20 * [mbm] guesses it to be a 12v unit Jul 24 23:34:21 [mbm]: 12V@1A, negative pole on the outside of the plug Jul 24 23:34:42 dc Jul 24 23:35:01 <[mbm]> ok, same as all the other crap I have around here Jul 24 23:52:11 as i said before, not the entire flash is mapped in the wl-153, so the only way to get a complete dump is jtag Jul 24 23:57:04 <[mbm]> and? Jul 24 23:57:50 <[mbm]> I'm guessing that you're booting another kernel since the sitecom kernel has an annoying password prompt Jul 24 23:58:05 <[mbm]> which means that you should be able to have your kernel map whatever you want Jul 25 00:01:56 at the moment i don't have a custom kernel for it Jul 25 00:02:18 <[mbm]> so what'd you use for a partial dump? Jul 25 00:03:08 didn't dumped anything so far :| Jul 25 00:07:05 <[mbm]> heh cute, just noticed something Jul 25 00:07:18 <[mbm]> when you boot it does that annoying password thing Jul 25 00:07:33 <[mbm]> but if you hold down reset at that point it does a "reset to defaults" and reboots Jul 25 00:08:00 <[mbm]> and while it shuts down you have a root console Jul 25 00:08:01 i didn't see any password prompt in crazy_imp's bootlog Jul 25 00:08:34 sn9: there is one, at the end Jul 25 00:08:48 sn9: ....---- Select Exit EnterPlease enter your Name and PasswordUser Name: Jul 25 00:13:01 ah Jul 25 00:17:16 [mbm]: it's a 2MB flash using redboot, and the map ends 64k early. i want to see whether redboot starts at that mark, or at the 128k-before-end spot of the ar525w. also, i want to see the header at the start of the flash Jul 25 00:17:58 that will give me an idea of how compatible my flash map driver is with other rdc devices Jul 25 00:18:44 *other rdc redboot devices Jul 25 00:20:08 <[mbm]> just a sec.. need to figure out if I can keep the commandline using the above bug Jul 25 00:29:11 <[mbm]> hmm Jul 25 00:29:22 <[mbm]> need to abort a shutdown in progress Jul 25 00:43:34 "just" :D Jul 25 01:07:40 [mbm]: made some progress? don't think the redboot on it offers a way to dump the flash Jul 25 01:34:50 <[mbm]> been trying to boot my own kernel Jul 25 01:36:51 <[mbm]> this version of redboot is annoying Jul 25 01:39:56 don't put your own kernel on until you've backed up the _entire_ flash Jul 25 01:40:07 <[mbm]> tftp booting :P Jul 25 01:40:47 the tftp will overwrite the flash Jul 25 01:41:21 <[mbm]> load ...; linux ... Jul 25 01:41:35 <[mbm]> it doesn't overwrite anything on the flash unless the flash command is used Jul 25 01:41:52 <[mbm]> this is just downloading a kernel into ram and executing it Jul 25 01:41:59 or the "dflash" command, or the "tftpd" command Jul 25 01:42:19 "load" can put it in ram, yes Jul 25 01:43:04 i'll be back in half an hour -- gone to radio shack Jul 25 01:44:31 [mbm]: can you paste your load line? would like to know how it should look like :) Jul 25 01:44:49 <[mbm]> heh, I haven't figured that part out yet Jul 25 01:45:16 hehe, i hoped you did :D Jul 25 01:45:38 <[mbm]> go bug florian, he's the one playing with rdc boards Jul 25 01:45:42 <[mbm]> ;) Jul 25 01:46:04 i'm quite sure he's sleeping right now :D Jul 25 01:48:24 <[mbm]> guessing it to be a "load -r -b 0x... bzImage" "linux -c "console=ttyS0,38400"" Jul 25 01:50:29 ok, i'll give it a try, with the bzImage from the sources Jul 25 01:50:42 <[mbm]> which sources? Jul 25 01:53:11 [mbm]: http://sitecom.com/showdownload.php?id=2400 (but it think you know them, we poked around in there iirc) Jul 25 01:53:33 remember the strange passwd file in there? Jul 25 01:53:40 <[mbm]> somewhat Jul 25 01:56:31 ideas how i can find out the ? Jul 25 01:56:38 <[mbm]> objdump Jul 25 01:57:28 is it called base address or is it the start address i should look for? Jul 25 01:57:46 <[mbm]> the default boot script uses -b 0x400000 Jul 25 01:58:44 ok, i'll try that Jul 25 01:58:49 what does -r ? Jul 25 01:59:05 read? Jul 25 01:59:07 <[mbm]> linux -b 0x400000 -l 0x0009c2d4 -s 0x001017da -c "console=ttyS0,38400" Jul 25 01:59:19 <[mbm]> oh .. -r on the load is for raw Jul 25 02:00:28 Raw file loaded 0x00400000-0x004a8f1f, assumed entry at 0x00400000 Jul 25 02:03:04 ok, it's working with the one from the sources :) Jul 25 02:03:23 <[mbm]> mine keeps booting from flash Jul 25 02:04:05 [mbm]: i used "linux -b 0x400000 -l 0x000a8f48 -s 0x0013c296 -c "console=ttyS0,38400"" after loading the image Jul 25 02:04:25 <[mbm]> right, and are you sure it booted the kernel you tftp'd and not from flash? Jul 25 02:05:42 i think if it was unable to load the one i've copyed into the ram, it should reboot, and there was no reboot Jul 25 02:06:10 <[mbm]> go hexedit a few bytes in the version string of the one you're trying to tftp boot Jul 25 02:06:18 hm, can i change something in there with hexedit? Jul 25 02:06:20 ^^ :D Jul 25 02:26:25 [mbm]: hmmm, it's crashing i think. how can i get the the right value for -s ? Jul 25 02:26:35 <[mbm]> see above Jul 25 02:27:07 <[mbm]> if you specified -c you should be able to see it trying to load Jul 25 02:27:53 [mbm]: you use a differnet bzImage then i do, and in the bootlog from the current firmware there is another value, so i think it's something variable Jul 25 02:28:37 all i get if i start it without the -s but with the command line options is: mem_size: 1000000 Jul 25 02:28:41 initrd fa3000 len 3d000 Jul 25 02:46:59 <[mbm]> can't get anything to boot on this braindead version of redboot Jul 25 02:51:04 [mbm]: do you get also only two lines and then nothing? Jul 25 02:53:18 * [mbm] using an openwrt image Jul 25 02:54:14 [mbm]: can you dcc me an rdc bzImage? don't have build one here atm **** ENDING LOGGING AT Wed Jul 25 02:59:57 2007