--- Log for 30.09.104 Server: burroughs.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 15 hours and 46 minutes ago 00.00.17 # <[IDC]Dragon> then it's just too slow 00.00.59 # hardware poweroff is (for the fm/v2) 5 seconds... 00.01.14 # <[IDC]Dragon> goodnight folks 00.01.20 # nite idc 00.01.36 NHeal (timeout) burroughs.freenode.net irc.freenode.net 00.01.45 Quit [IDC]Dragon () 00.04.15 # bye ... 00.04.21 Quit webguest71 ("CGI:IRC (EOF)") 00.14.06 *** Saving seen data "./dancer.seen" 00.15.42 Quit _aLF ("bye") 00.21.40 # I killed the file system... 00.22.32 # Uhh, not exactly. Let's see what is wrong... 00.22.50 # HAHA. 00.22.52 # :) 00.25.31 # Dunno what went wrong. Archos firmware says there is no valid partitio, but windows does read it fine. Anyway, I just reformatted. 00.31.44 # RoLo works on the Ondio! 00.31.57 # wouh! nice work! :) 00.32.37 # Fonts and languages too (not from the menu though) 00.34.29 # that's great 00.34.31 # post pics :) 00.38.02 # Trying to dump the rom into files doesn't work. All I get are zero length files, and the first try caused the file system corruption 00.38.35 # i see.. :\ 00.39.02 # Anyway, I need to sleep now. 00.39.06 # Nite 00.39.16 # nite 00.39.26 Part amiconn 01.01.38 Join NelsonM [0] (~nelson@adsl-63-194-75-26.dsl.snfc21.pacbell.net) 01.01.54 # help, my rockbox won't boot anymore! 01.02.12 # please describe the problem a bit. i've got no idea what has happened or could be wrong. 01.02.22 # I can't turn it on in play mode or USB mode anymore. Is there a way to disable the rockbox bios and just boot from firmware? 01.02.33 # I have a 20 gig recorder that's been working for a year. I haven't tried to flahs the bios. 01.02.45 # when I turn it on it comes on for a few seconds, then turns off and reboots. I don't think it's out of power. 01.02.56 # could you plug it in to be sure? 01.03.20 # yeah, I should do that, I don't have the charger here. 01.03.58 # is there some way to tell the Archos firmware not to load an OS from the hard drive? I thought F1+on may do that, but I'm not sure. 01.04.21 # won't 01.04.32 # f1+on doesn't do that? 01.05.09 # brb. 01.05.10 # no. 01.05.12 # thanks 01.09.15 # bac 01.09.17 # back, rather 01.09.25 # thanks for the help. I love rockbox. 01.09.28 # hmm 01.09.55 # is the backlight or lcd dim? that would indicate very low batteries.. 01.10.11 # yeah, it's not, and I just charged it up. But maybe the batteries have gotten old, I should try again. 01.10.44 # I sure wish Rockbox worked on hardware that had a Li-Polymer battery. These NiCd batteries are junk. 01.11.03 # NiMH, actually. if you get higher capacity you get better runtime 01.11.15 # will AA NiMH work fine in the rockbox charger circuit? 01.11.22 # ships with 1500mah, ~8h. you can get 2100 or 2200mah, ~12h. 01.11.28 # yep. any nimh. 01.11.42 # What do rockbox developers do if they put a broken OS on the hard drive? Is there any way to recover it other than plugging the drive into a laptop? 01.12.15 Join bagawk [0] (Lee@bagawk.user) 01.12.21 # no, you can go into usbmode without booting the firmware really 01.12.27 # to delete rockbox if needed 01.12.38 # plug in usb, then turn it on. as opposed to booting it then plugging in usb. 01.12.44 # ah, I thought the rockbox OS got involved in USB mode too. 01.13.04 # it does. 01.13.22 # but archos firmware starts before rockbox. and if usb is in right when it's started it automatically does that instead of harddisk firmware 01.13.39 # oh, cool 01.13.58 # you can try it, not sure if it will help. 01.14.04 # sounds like the batteries may be the problem. 01.14.10 # can you feel the harddisk spin up? 01.14.54 # just barely, a bit of spin up but no seek 01.15.03 # quarter second or so. 01.15.43 # ok, that must be the batteries. 01.15.51 # I hope so, that's an easy fix :-) 01.15.58 # just have to go home and plug it in. 01.16.10 # yeps.. hopefully that's it :) 01.16.11 # btw, rockbox got 10x more useful to me when it implemented bookmarks. Great for audiobooks 01.16.24 Join edx [0] (edx@p54879875.dip.t-dialin.net) 01.16.45 # yeah, they are 01.19.25 Quit mecraw ("Trillian (http://www.ceruleanstudios.com)") 01.23.51 Quit NelsonM ("Leaving") 01.46.21 Quit edx (Read error: 238 (Connection timed out)) 01.51.10 Quit bagawk ("umount /dev/brain") 02.00.22 Join ashridah [0] (ashridah@220.253.121.29) 02.14.08 *** Saving seen data "./dancer.seen" 02.14.12 Join Chronic007 [0] (~Miranda@24.30.163.142) 02.38.36 Quit Chronic007 ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 02.51.42 Join scott666_ [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 03.23.58 Join edx [0] (edx@pD9EAB452.dip.t-dialin.net) 04.14.11 *** Saving seen data "./dancer.seen" 04.50.42 Quit scott666_ ("i'll be back...eventually...") 05.10.00 Quit pyros- (Read error: 242 (No route to host)) 05.38.07 Join LinusN [0] (~linus@labb.contactor.se) 06.14.14 *** Saving seen data "./dancer.seen" 06.23.33 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 06.36.13 Quit ashridah ("gone") 06.49.07 Quit edx () 07.01.03 Quit dwihno (Remote closed the connection) 07.08.49 Join DomasoFan [0] (~d433e0ae@labb.contactor.se) 07.09.10 Quit DomasoFan (Client Quit) 07.10.58 Join PaulS [0] (~437e19f6@labb.contactor.se) 07.11.25 # hi PaulS 07.11.30 # Hey, Linus. My first attempt at JTAG was met with mixed success. 07.12.04 # it struck me that the pins are configured as bdm pins 07.12.54 # My first realization (even before I started) is that the TEST[3:0] pins need to be set correctly for the Coldfire to go into JTAG vs BDM mode. Thanks to you nudie pics, I found the 10K resisitor that pulled the chip into BDM mode and shorted it to ground like TEST[3:1] were. 07.13.08 # ok good 07.15.09 # My second challenge was that I couldn't actually find a test pad for TCK like the other JTAG pins hanging out by the BDM pads. I did a little light probing (don't want to do too much on a populated board), and still couldn't find it. Again, thanks to your nudie pics, I was able to find the backside of a via that carries TCK. It's strange, though. I'd imagine that if there's a via, that signal must be going somewhere. 07.17.17 # My next challeng was finding software that understood the Coldfire in debug mode. I picked up the OpenWinCE jtag tools, and wrote a part definition based on the BSDL file from Freescale, and then wrote a bus definition based on the datasheet. 07.17.39 # s/debug/JTAG/ 07.19.06 # My current challenge is to get my laptop parallel port working with either ppdev or direct iopl() so I can test all of the above. Hopefully I'll get some time tomorrow night to try that out. 07.24.30 # a qick search for the TCLK signal gave me nothing on the PCB 07.25.26 # i.e no test pad or pullup resistor... 07.25.48 # I also tried some of the pins of the (unpopulated) flex connector on the backside of the board (the ones that weren't obscured by the LCD padding) and still couldn't find TCK.. Odd. It seems, BTW, that anyone who's serious about playing with BDM/JTAG on the iRiver would pick up that flex connector. There are little cable assemblies you can buy to stick into them, so all you have to do is solder your wiggler to that -- of course this is all modulo sig 07.26.16 Join dwihno [0] (~dw@81.8.224.89) 07.27.07 # i'd like to find a good place to buy such a connector 07.27.33 # Isn't it odd that there's still a via next to the pad though? 07.27.54 # indeed 07.29.00 # found it, R35 07.29.28 # 220k 07.30.09 # pullup to VCC it seems 07.30.24 Join amiconn [0] (~jens@pD9E7FF9B.dip.t-dialin.net) 07.30.41 # R35 is located right below the CPU 07.32.23 Join [IDC]Dragon [0] (~idc-drago@pD9FF8A31.dip.t-dialin.net) 07.32.43 # What pitch would you say those debug connector pins are? I'm guessing something along the lines of http://rocky.digikey.com/WebLib/Hirose/Web%20Data/FH18%20Series.pdf would work, which would make digikey.com be a reasonable source. 07.33.00 # LinusN: R35: Oo. Let me take a peek. 07.34.23 # I tested the other pads from the vias over to the test pads and I didn't get any nasty surprises, so I think I'm in good shape otherwise. 07.34.36 # but that connector has two rows of pins, doesn't it? 07.35.39 # Whups.. Let me find the right part.. 07.37.46 Part LinusN 07.37.57 Join LinusN [0] (~linus@labb.contactor.se) 07.40.36 # Check out http://rocky.digikey.com/WebLib/Hirose/Web%20Data/FH12%20Series.pdf. Unfortunately the 24 pin version is not in stock at Digikey. Also, you need to confirm that the pin pitch is actually 0.5mm on the iRiver. That was just my guess. 07.41.01 Join DomasoFan [0] (~d433e0ae@labb.contactor.se) 07.42.00 # too bad the LCD connector is only 18 pins, otherwise i could just have used the one from the naked board :-( 07.43.24 Quit DomasoFan (Client Quit) 07.48.48 Quit PaulS ("CGI:IRC (EOF)") 07.49.29 Join PaulS [0] (~437e19f6@labb.contactor.se) 07.50.46 # Here's a part DigiKey has in stock: XF2H-2415-1 http://rocky.digikey.com/WebLib/Omron%20Web%20Data/XF2H.pdf 07.53.29 # 24 contacts? 07.54.00 # Then, say you need a 6" flex jumper. In stock too. 050-24-152B http://dkc3.digikey.com/PDF/T043/0049.pdf 07.54.10 # Was I wrong about the number of contacts? 07.55.08 # should be 20 07.55.25 # how about this one: HFJ20TR-ND 07.55.45 # Ah. I hadn't tried to count them since before the nudes.. 07.57.22 # Hey, you're getting the hang of it! 07.58.16 # Actually, Digikey's site puts a reasonable amount of pleasure into the act of finding the right part. I get the catalog in the mail but I hardly ever use it. 07.58.57 # as opposed to Farnell, where the web search is a real pain 08.01.06 # The Omron XF2J-2024-11 connector is $1.03, compared to the Hirose $2.55. How could you justify the extra cost, especially in single unit quantities? :-) 08.01.38 # Actually, I think Digikey has a $20 minimum for web orders. 08.01.50 # typical 08.02.18 # the shipping to sweden will probably cost the double :-) 08.02.55 # Well, so far you don't have a lot of shipping weight, which works to your advantage. 08.03.21 # btw, i'm a little curious about the communication with the tuner 08.03.52 # Yeah? Anything I can help with? I haven't stared at that code too much, but now is a good time to ask me to do that. 08.03.59 # your table seems to imply that the GPIO3 and GPIO55 pins are configured as GPIO 08.04.39 # but they are definitely more likely to be configured as I2C pins 08.05.21 # or could it be that they wanted to use the internal i2c, but found it easier/better to bit-bang instead? 08.05.34 # Actually, I've got them listed as "F", function pins. 08.05.50 # not before my latest change in wiki 08.06.01 # i changed them to "F" 08.06.02 # Oh, actually, you did that. B) 08.07.07 # Umm... Let me see what the register accesses look like. Definitely GPIO3 confused me as to how they were using it, hence the question mark. 08.10.19 Join DomasoFan [0] (~d433e0ae@labb.contactor.se) 08.10.46 # Also, the pin is a function pin until programmed otherwise. Since the code is structured so that they perform incremental ors and ands to the function bits, sometimes it's hard to say how the pin is at "steady state". It's concievable, for example, that when I2C isn't active they switch to GPIO mode so they can force their own values. 08.13.07 # GPIO3 is never touched, so I concur that it is a function pin. 08.13.17 # (Rather FUNCTION_GPIO3) 08.13.53 # gpio3 is the i2c clock 08.14.15 *** Saving seen data "./dancer.seen" 08.16.53 # <[IDC]Dragon> amiconn: I got the same file system corruption with the new code 08.22.08 # As for GPIO55, it _looks_ pretty cut and dry that it's set to be GPIO. The entry point calls this init routine that calls this function that says GPIO_FUNCTION |= 0x800000. 08.24.47 # Oo. This function also sets GPIO_FUNCTION0 |= 0x8. Missed that one. I bet they wanted to leave the option open to use the builtin I2C but they couldn't get it to work right so the punted. 08.25.19 Quit DomasoFan ("CGI:IRC (Ping timeout)") 08.26.54 # so my guess was right 08.27.03 # they bitbang the i2c 08.27.24 # Right. 08.28.34 # interesting, that has happened to a few other projects i've been working in 08.28.51 # they wanted to use the internal controller, but ended up bitbanging instead 08.31.20 # Once you write the code, life turns out kinda okay, if you've got CPU left over. The one that i think hurt them the most is how they bitbang the SPI for the remote. That must have hurt. 08.31.33 # indeed 08.31.59 # leaving for ~5 days tomorrow, so if i don't catch you, see you later :) 08.34.23 # cu midk, have fun 08.34.43 # later LinusN, thanks :) 08.35.00 # Later midk. 08.35.25 # see you PaulS.. now, bed :) 08.52.00 # [IDC]Dragon: The funny thing with the file system corruption is: I got it with the internal flash first, the Ondio couldn't read it any more. Windows was able to access it, and repairing with Windows yielded a number of lost clusters. 08.52.18 # The Ondio still couldn't access it, so I reformatted. 08.52.48 # After this first reformat, I couldn't make the corruption happen again for the internal flash! 08.53.22 # This morning I tried the same with my external card, with the same results 08.54.26 # Writing seems to work okay when it has to write single blocks (config block and .playlist_control work fine), but chokes on larger block counts (i.e. ROM dump) 08.57.23 # so it might be a timing error between writes? 09.00.30 # <[IDC]Dragon> amiconn: I'm working on the port inits (made a debug output), but not yet done 09.00.49 # <[IDC]Dragon> when cold-started, we have many wrong pin functions 09.05.01 Join amiconn_ [0] (~jens@pD9E7F060.dip.t-dialin.net) 09.10.31 # <[IDC]Dragon> bbl 09.10.33 Quit [IDC]Dragon () 09.15.55 Quit amiconn (Nick collision from services.) 09.15.55 Nick amiconn_ is now known as amiconn (~jens@pD9E7F060.dip.t-dialin.net) 09.16.45 Join Zagor [242] (~bjst@labb.contactor.se) 09.28.57 # first alpha iriver schematics are in the wiki 09.29.38 # excellent 09.29.46 Join ashridah [0] (ashridah@220-253-121-68.VIC.netspace.net.au) 09.32.12 # OMG LinusN. That's the hotness! 09.33.10 # i'm a bit unsure about the disk led though 09.38.30 # radio chip is marked U$1 09.39.41 Join pyros [0] (~hof@ppp158-32.lns2.mel2.internode.on.net) 09.39.43 # LinusN: Donna Sunner doesn't even have this hot stuff. Great work! 09.41.58 # can anybody see which U-number the fm chip is? 09.42.30 # it's really crowded around that little sucker 09.44.46 # Unless it's U8, I don't see it. 09.46.33 # I don't think it's U8 09.47.49 # The "U8" is parked out by a capacitor. There's nothing in that area that looks like it should belong to U8. It's possible that the guy doing the layout lost track of where the label was. 09.49.36 # U8 is the mic, isn't it? 09.52.14 # Hmm.. It's possible. Personally I wouldn't give a microphone a U-number, but that could be argued as a personal taste thing. 09.53.26 # i agree, but I saw the line in/our and power connectors have U-numbers too 09.54.04 Join Chronic007 [0] (~Miranda@24.30.163.142) 09.54.10 # Well, some of those have bunches of pins, and in the line-in/line-out cases they're arguably not-completely-passive. 09.55.30 # headphone connector is U5 :) 09.56.19 # anyway, I can't find a designation for the radio chip either 09.59.57 # i have set it to "U???" for now :-) 10.07.36 # It's bedtime for me. Good work all. Wish me an uneventful JTAGging tomorrow if I get the time. 10.08.25 # PaulS: good luck 10.10.05 # once my CD drive fails to rip a CD and I get kernel error messages about ATAPI 10.10.13 # ... it then stops being able to read from it 10.10.19 # I have to... REBOOT 10.10.33 # * Bagder shrugs 10.11.40 # Bagder: kernel version? 10.11.57 # 2.6.5 10.12.18 # Bagder: ide cdrom? tried using hdparm to reset it completely? 10.12.21 # I suggest an upgrade before you reboot 10.12.24 # I've had that happen in some of the 2.4 kernels with a specific NEC CD-RW drive. Very annoying. 10.12.28 # i've foudn that works for all sorts of fun ide cdrom issues 10.12.32 # I think the drive itself goes nuts.\ 10.13.11 # i don't think I've ever encountered a failed rip, come to think of it. 10.13.19 # yes, it might be the drive itself 10.13.32 # what drive is it? 10.13.34 # PaulS: tried looking for a firmware update? 10.13.35 # Zagor: you should try some of my really old and crappy ones 10.13.39 # CDs that is ;-) 10.13.48 # PLEXTOR DVDR PX-708A 10.13.55 # I think just maybe I've got around the problem in the past with the right set of eject/inserts and hdparm ata resets, but I might me mistaken. I might have just switch to using the other recorder. (I got these errors with cdrecord). 10.14.17 *** Saving seen data "./dancer.seen" 10.14.17 # dmesg reports numerous ATAPI resets 10.14.28 # and they don't seem to make it better 10.14.37 # ashridah: I haven't looked for a firmware update. That's a good idea. I mostly just stay away from that drive. 10.15.20 # Anyway, the pillow bellows. 10.15.39 Part PaulS 10.18.59 # I better reboot then 10.19.02 Quit Bagder ("Off to search for that connect-resetting peer guy!") 10.29.42 Quit kaouete (burroughs.freenode.net irc.freenode.net) 10.29.42 NSplit burroughs.freenode.net irc.freenode.net 10.29.47 Join kaouete [0] (~menfou@dyn-83-155-184-141.ppp.tiscali.fr) 10.51.13 Part Chronic007 10.57.13 Join Chronic007 [0] (~Miranda@24.30.163.142) 11.03.20 NHeal (timeout) burroughs.freenode.net irc.freenode.net 11.44.31 # Zagor: r u there? 11.44.37 # yes 11.45.20 # More button woes, even with the classic jukeboxes :( 11.45.53 # ok? 11.46.44 # If you go into the browser functions available from the menu (plugins/ fonts/ langs/ .wps) and then leave with "left", this is also catched by the menu code afterwards, bringing you one level back (unwanted) 11.47.46 # Then there are the button handling issues on the Ondio. Currently, neither the main menu is callable, nor the onplay menu works. 11.49.03 # right, I'm planning to redo some code to avoid the trailing release events. 11.50.02 # and for the ondio I will simply remove the shift code and call menu and on-play separately (on-play with right+repeat) 11.54.47 # It's probably a good idea for all architectures to use some delay (i.e. button repeat) for more xotic functions instead of button combos. It makes one-hand operation a lot easier 11.54.47 # Real Soon Now ;) 11.54.58 # *exotic 11.56.10 # And on the Ondio it is possible to use the OnOff button for short keypresses (not triggering poweroff). 11.57.00 # The browser<->wps switching and resume comes to mind 11.57.43 # yes but the onoff button is not in a very nice position. i think using the option button is better. 12.02.39 Join [IDC]Dragon [0] (~d90a3255@labb.contactor.se) 12.04.08 Quit Chronic007 (Read error: 110 (Connection timed out)) 12.08.12 # <[IDC]Dragon> amiconn: do you read? 12.14.20 *** Saving seen data "./dancer.seen" 12.14.52 Quit gromit` ("Client exiting") 12.18.00 # [IDC]Dragon: yes 12.19.05 Quit pyros (Read error: 54 (Connection reset by peer)) 12.19.28 Join pyros [0] (~hof@ppp158-32.lns2.mel2.internode.on.net) 12.19.41 # <[IDC]Dragon> one more addition to the f/s corruption: 12.20.11 # <[IDC]Dragon> I got the very same thing, looked well under Windows, but refused to boot from there 12.20.35 # <[IDC]Dragon> then I did a quickformat, which fixed it 12.21.38 # <[IDC]Dragon> I still have a dump of the partition before all these experiments 12.21.57 # <[IDC]Dragon> so I could restore that and try if it happens again 12.22.21 # Did you check _what_ got corrupted? I didn't have an idea how to do this 12.22.45 # <[IDC]Dragon> if it's reproduceable, I could diff the dump 12.23.02 Join gromit` [0] (~gromit@ALagny-151-1-40-71.w83-114.abo.wanadoo.fr) 12.26.59 # [IDC]Dragon: The config sector (both calculation and usage) works well. It is sector 30 (on the internal flash at least). All settingspersist 12.28.25 # <[IDC]Dragon> I noticed that in case of error your calculation function returns 0. 12.28.45 # <[IDC]Dragon> do you catch that from the caller? 12.28.59 # <[IDC]Dragon> we don't want the config in sector 0... 12.29.06 # Yes, that's intended. I changed the the settings_load() / settings_save accordingly 12.29.35 # <[IDC]Dragon> ok 12.29.55 # <[IDC]Dragon> else it would be catastrophic 12.30.23 # ..replacing the old check, which checked whether the partition started at sector 0 (floopy-like disk layout without partition table) 12.30.49 # <[IDC]Dragon> ohh, I liked that 12.31.16 # <[IDC]Dragon> so I could test the fat code with a partition dump 12.32.18 # <[IDC]Dragon> sorry, ignore me, that's in the test code only 13.06.54 Join MooMaunder [0] (~me@194.152.87.150) 13.16.13 # has anyone ever seen/written a nice little hack that turns a numberic range into a regex? i.e. 5-12 => ([5-9]|1[0-2]) 13.19.20 # b 13.20.36 # Zagor: why? 13.20.43 # (curious) 13.21.50 # street numbers... 13.23.13 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 13.28.09 Join R3nTiL [0] (~zorroz@129-250-30-217.kgts.ru) 13.31.00 # Zagor: aha 13.31.36 # Bagder: http://www.rockbox.org/twiki/bin/view/Main/IriverSchematics 13.31.46 # seen it, loved it! 13.32.05 # zoom zoom zoom 13.32.11 # :-) 13.33.01 # Zagor: /(37.3,200)/; # matches any number x, 37.3 < x < 200 13.34.09 # is that what you want ? 13.36.01 # yes it is. now can you make it match only odd or even numbers? 13.36.28 # hmm 13.39.03 Quit [IDC]Dragon ("CGI:IRC (EOF)") 13.54.09 # rumours have it RMS was in a car crash today 14.00.07 Quit R3nTiL () 14.01.30 # injuries? 14.01.45 # apparently RMS survived, but at least one died 14.01.50 # oh 14.01.59 # ouch 14.02.28 # but this is "a user on another channel confirmed this" and I read this in another channel ;-) 14.02.30 # RMS? 14.02.41 # Richard Stallman 14.10.52 Quit Bagder ("Off to search for that connect-resetting peer guy!") 14.14.23 *** Saving seen data "./dancer.seen" 14.29.05 # Ah 15.01.54 Join [IDC]Dragon [0] (~d90a3255@labb.contactor.se) 15.04.34 Part LinusN 15.41.08 Join edx [0] (edx@pD9EAB452.dip.t-dialin.net) 15.42.01 Join methangas [0] (methangas@0x50c61ce6.virnxx10.adsl-dhcp.tele.dk) 15.50.12 Quit ashridah ("sleep.") 15.55.04 Join mecraw [0] (~lmarlow@69.2.235.2) 16.01.23 Join Sporta [0] (~4givn@dpc691997050.direcpc.com) 16.01.28 # hi guys 16.01.30 # yay, microsofts vfat patent has been rejected 16.01.35 # hi 16.02.47 # hey, I'm having a weird problem. All of a sudden, when I boot up my FM Recorder, there's no directory list or files or anything -- it just shows the arrow cursor and the header with the battery, time, etc. then later on, it'll say "Dir buffer full" on the screen... anybody run into this? 16.05.34 # Sporta: how many files do u have in your root dir? 16.05.50 # not many. I have maybe 15 files and another 20 or 30 folders 16.06.12 # unless thos files/dirs have extremely long names i have no idea, sorry 16.06.45 # all right. I did try to put on one of the daily builds the other day, though 16.08.50 # for some reason, though, it didn't overwrite the version 2.2 of Rockbox. The only way I could boot the daily build was by selecting ajbrec.ajz and hitting play. is that not right? 16.14.25 *** Saving seen data "./dancer.seen" 16.19.32 Quit [IDC]Dragon ("CGI:IRC (Ping timeout)") 16.26.19 Quit Sporta () 16.59.45 Quit elinenbe (" HydraIRC -> http://www.hydrairc.com <- Get hot chicks here!") 17.02.27 Part Zagor 17.28.54 Join Tim[RIP] [0] (Tim_RIP_@83.73.82.114.ip.tele2adsl.dk) 17.29.09 Part Tim[RIP] 17.48.50 Quit kaouete ("Changing server") 17.48.54 Join kaouete [0] (~menfou@amande.ipv6.crazydwarves.org) 17.55.32 Nick gromit` is now known as gromit\party (~gromit@ALagny-151-1-40-71.w83-114.abo.wanadoo.fr) 17.59.43 Join _aLF [0] (Alexandre@mutualite-3-82-67-66-128.fbx.proxad.net) 17.59.45 # <_aLF> hi 18.01.16 Join Zagor [0] (foobar@h254n2fls31o265.telia.com) 18.11.05 Join dwihno_ [0] (~dw@81.8.224.89) 18.12.48 Quit MooMaunder (burroughs.freenode.net irc.freenode.net) 18.12.48 NSplit burroughs.freenode.net irc.freenode.net 18.12.48 Quit dwihno (burroughs.freenode.net irc.freenode.net) 18.13.20 Quit AciD (Read error: 104 (Connection reset by peer)) 18.14.29 *** Saving seen data "./dancer.seen" 18.30.28 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 18.36.44 Quit pike (Read error: 104 (Connection reset by peer)) 18.37.31 Join pike [0] (amiga@h234n1fls22o1064.bredband.comhem.se) 18.49.49 NHeal (timeout) burroughs.freenode.net irc.freenode.net 19.36.12 Join webguest64 [0] (~d89b5e36@labb.contactor.se) 19.36.24 Part webguest64 20.14.32 *** Saving seen data "./dancer.seen" 20.46.30 Join adi|blah [0] (~adiamas@pool-138-89-6-14.mad.east.verizon.net) 20.47.03 Quit adi|blah (Client Quit) 20.53.33 Join scott666_ [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 21.14.45 Join zeekoe [0] (me@zeekoe.kabel.utwente.nl) 21.27.18 Quit methangas (Read error: 232 (Connection reset by peer)) 21.29.50 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 21.51.04 Quit Zagor ("Client exiting") 21.52.47 # There seems to be at least one bug in the FAT16 support :( 22.10.04 Join Toni [0] (~3e8650bb@labb.contactor.se) 22.10.32 # Hi guys 22.10.47 # You do a great job! 22.11.16 # hi 22.11.16 # thanks 22.11.19 # Does anybody know a freeware mp3-transcoder? 22.11.41 # transcode between what? 22.11.53 # Mp3 to Mp3 22.12.24 # lame can do it 22.12.38 # I mean, lame dos this job, but no UI. 22.13.35 # transcoding like that is a terrible idea anyway ;-) 22.14.36 *** Saving seen data "./dancer.seen" 22.15.22 # But I have a big list of mp3 with high bitrate, which I like to shrink to get it fit into my MMC card 22.16.07 # How about the idea, I make a Windows-UI and put it to the rockbox page as a goody? 22.16.26 # Toni: You are the Ondio user with FMR and 1 GB CF, right? 22.16.35 # Right 22.16.44 # :) 22.16.59 # http://www.rockbox.org/twiki/bin/view/Main/UsefulTools <= it would fit there 22.17.20 # OK, thanks. 22.17.30 # Toni: Got my reply mail? 22.17.51 # Not yet, I look. 22.21.12 # MAS shows also only zeros 22.22.05 # Hmm. So it is really strange that you are able to play music. I'm not :( 22.23.07 # Okay, maybe I should try it with low bitrate files. Usually my files are vbr around 200 kbps 22.24.40 # I can hear a small click when firmware is loaded, but I donīt know, wether it comes from original or new. 22.25.37 # You can set "Show files" to "supported" or "all" and then try to RoLo. If you hear the click again, it is produced by rockbox 22.27.13 # I don't hear a click :( 22.27.34 # Sorry, I am a newcomer, what is RoLo? 22.27.45 Join [IDC]Dragon [0] (~idc-drago@pD9FF8A31.dip.t-dialin.net) 22.28.20 # Toni: Oh ok, RoLo means "rockbox loader". You can load a (perhaps different) firmware without switching off & on again 22.28.57 # If you see a firmware file in the file browser (extension .ajz), simply "play" it. 22.29.15 # [IDC]Dragon: Bad news: FAT16 seems to have at least one bug :( 22.29.28 # <[IDC]Dragon> booo 22.30.18 # Itīs definitely Rockbox. 22.30.18 # <[IDC]Dragon> it went through Zagors' tests all fine 22.30.19 # I checked my writing, and found that it always returns success. Then I did the following, which should definitely work if FAT16 wouldn't have a bug: 22.31.09 # (1) I made a player build with 2 modifications: (a) compiled with HAVE_FAT16_SUPPORT, (b) modified init() in main.c to only mount partitions with type == 6 22.32.07 # (2) The I repartitioned my player: 1st partition ~3 GB, FAT32, containing archos.mod only. 2nd partition ~260 MB FAT16, with archos.mod and .rockbox dir 22.33.11 # Then I booted with the modified build. The FAT16 partition gets mounted. If you then try to dump the ROMs -> *PANIC* Writing before... 22.34.32 # Btw: it's nice to have a spare box as a developer... 22.36.11 # <[IDC]Dragon> hmm, interesting 22.36.29 # <[IDC]Dragon> (I don't have a spare box) 22.37.09 # Then just tell me what additional tests I could perform 22.37.51 # (You mean: you don't have a _working_ spare box ;) ) 22.37.56 # <[IDC]Dragon> I have a look at the code first 22.38.04 # <[IDC]Dragon> :-( 22.38.25 # Bye 22.38.28 Part Toni 22.38.52 # <[IDC]Dragon> I could need a disk image which is before the problem 22.40.11 # Do you mean from the Ondio or my player test? On the player, it didn't corrupt the fs, it just refused to wite (with that panic) 22.42.09 # Some interesting info about the MMC driver: I measured the raw read speed, got ~135 KByte/s with the internal flash and ~155 KByte/s with my 256 MB card 22.47.30 # <[IDC]Dragon> different response time, right? 22.48.35 # yup 22.49.25 # The theoretical maximum we could achieve if there would be zero response time is ~350 KByte/s. With response times I expect a maximum of ~250 KByte/s 22.49.50 # So there is room for optimization :) 22.51.53 # <[IDC]Dragon> max is theoretical, or with your code? 22.52.10 # Theoretical 22.55.02 # The ~250 KByte/s is derived from the assumption that the read speed scales somewhat linear with the card clock, which is backed by the fact that reading the Ondio (both int & ext card) from the PC (bridge clock 12 MHz) delivers ~1 MByte/s, while reading an MMC with my card reader (most likely using the max possible clock, 20 MHz) delivers ~1.6 MByte/s 23.00.43 # Another interesting fact: Early return from writing the last block is possible, if we don't want to check card status. My first interpretation of the datasheet was incorrect (That's why my first version of write_sectors did only work for single sectors) 23.01.57 # <[IDC]Dragon> saving the last sector, hmm 23.02.07 # <[IDC]Dragon> I'm very sleepy today 23.02.07 # ? 23.02.50 # <[IDC]Dragon> port inits didn't like me 23.03.00 # <[IDC]Dragon> I call it a day, cu 23.03.08 # nite. 23.03.11 Quit [IDC]Dragon () 23.16.38 Join gromit`` [0] (~gromit@ALagny-151-1-21-134.w83-114.abo.wanadoo.fr) 23.30.35 # [IDC]Dragon: (for the log). It's definitely the file system and not the MMC driver. I reformatted my ext MMC with FAT32, and ROM dump did work onto that card! 23.37.31 Quit gromit\party (Read error: 110 (Connection timed out)) 23.46.03 Quit edx (Read error: 60 (Operation timed out)) 23.53.45 # Someone here with a player? 23.55.17 Join webguest61 [0] (~958ef955@labb.contactor.se) 23.56.14 Quit webguest61 (Client Quit)