--- Log for 23.06.103 Server: calvino.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 1 month and 10 days ago 00.00.06 # dos prompt 00.00.13 # I thought you "knew computers" ?? 00.00.45 # i do it brings up a prompt 00.00.48 # and than closes it 00.02.26 # nvm 00.02.31 # im just dling the installer 00.02.49 # 8 meg but im dlin at 150 00.03.20 # nobody talks much here 00.03.23 *** Saving seen data "./dancer.seen" 00.03.46 # Many of the ppl live in Europe, and are asleep now. =) 00.04.03 # well wake them up 00.04.09 # i dont live in europ 00.04.50 # i live in europe! 00.04.53 # in London!!! 00.05.03 # i live in usa 00.05.27 # tracktheripper: what a coincidence! 00.05.34 # that's exactly where I don't live 00.05.36 # heegee 00.05.41 # :(( 00.07.49 # ahh ahh 00.08.28 # grr 00.10.06 Quit Zane ("Leaving") 00.13.45 Quit Jet8810 (Connection reset by peer) 00.21.00 Join Jet8810 [0] (~Jet8810@adsl-34-188-107.bct.bellsouth.net) 00.24.58 Quit Jet8810 (Read error: 54 (Connection reset by peer)) 00.24.58 Quit elinenbe (Read error: 54 (Connection reset by peer)) 00.24.58 Join Josh_ [0] (~Jet8810@adsl-34-188-107.bct.bellsouth.net) 00.25.01 Join elinenbe [0] (trilluser@user-0cev103.cable.mindspring.com) 00.26.47 Quit tracktheripper ("Leaving") 00.27.39 # join gentoo 00.27.49 Nick Josh_ is now known as Jet8810 (~Jet8810@adsl-34-188-107.bct.bellsouth.net) 00.29.10 # you join jentoo 00.29.11 # gentoo 00.34.20 Join OliverKlozoff [0] (whatsit2u@user-2inim1g.dialup.mindspring.com) 00.34.21 Quit Stevie-O (Read error: 104 (Connection reset by peer)) 00.37.49 # join genthree 00.38.54 # * Now talking in #genthree 00.38.54 # * asimov.freenode.net sets mode: +n 00.54.18 Join Bluechip [0] (~bluechip@pc1-colc1-3-cust223.colc.cable.ntl.com) 00.54.51 # any programmers in? 01.00.04 # according to certain theories 01.00.18 # tell me -- did you try menutest yet? 01.07.20 # no, still working on my own code - which bit of the menu system does it test 01.08.41 # anyway in button_get_w_tmo ...how long is a "tick" 01.08.53 # i presume it is some factor of "HZ"?? 01.11.23 # kernel.h: #define HZ 100 /* number of ticks per second */ 01.12.19 Join Yeft [0] (Yeft@AC8466D2.ipt.aol.com) 01.12.23 Quit _aLF ("bye") 01.12.36 # so ...how long is a "tick" then? 01.12.49 # oh shit - sorry, two conversation 01.12.53 # s 01.13.03 # note to self: STOP SCAN READING 01.13.12 # ...can you guys help with the original firmware at all..(fm recorder) 01.13.12 # if HZ is 100 ticks/sec, tick is 1/100 sec 01.13.26 # yeah, sorry, just me being dumb! 01.13.53 # what's your Q, Yeft? (I don't have an FM) 01.14.55 # when i turn it oh, everything loads fine, but its all jibberis (i.e. $#^DSF is a folder) and if i try to enter an of the folders it says hard drive error, and if i try to turn on the radio it crashes... 01.15.19 # Hmmm. Have you tried to scandisk the drive? 01.15.36 # nope 01.15.42 # run chkdsk before scandisk 01.15.48 # that'd be the first thing I tried. 01.15.51 # ok 01.15.54 # chkdsk chkdsk /f scandisk 01.16.51 # ok, I just opened my fm and removed the hdd 01.17.00 # woohoo! 01.17.32 # I put it back in, re-assembled, and it is till functioning 01.18.01 # i think it worked 01.18.07 # lol it said i bunch of stuff 01.18.13 # the case, however, is bent in acurve at the back top and bottom 01.18.17 # convert lost chains to files????? 01.18.25 # yeft: no 01.18.25 # yes please 01.18.35 # Convert = YES *always* 01.18.36 # ty 01.18.47 # brrr 01.18.53 # i typed n 01.18.56 # this is your lost data - the alternative is lose it forever 01.18.58 # brfore you chimed in... 01.19.07 # but it will not convert unless you use /f - stage 2 01.19.09 # bahhhhhh 01.19.12 # what,s he going to do with partial mp3 filesa/ 01.19.22 # most ppl have their JB synced w/ PC anyway. Easy to recover. =) 01.19.47 # <-- not most people 01.19.55 # oh, dear 01.20.29 # it works! 01.20.35 # thank you 01.20.36 # good! 01.24.19 # i love all my new ultimixes (ac/dc you shook me all night) 01.24.27 # i love that one the most 01.25.37 # thank you all! 01.25.44 # seeya later 01.25.56 Quit Yeft ("i'd rather be rich than stupid - jack handy") 01.28.55 Part Bluechip 01.34.26 # jzoss? 01.35.19 # yes 01.36.19 # the bent case means that the battery contact isn't secured as tightly 01.36.34 # any ideas on straightening that bend? 01.36.56 # Is the piece flat, or does it have the sides on too? 01.37.30 # sides, which are soldered to the mainboard 01.37.45 # that's why i bwnt, to avoid soldering 01.37.54 # So you can't exactly press it with anything, since it's got circuit stuff mounted to it 01.38.34 # I was able to hold the pieces together 01.38.56 # If you can't pull the circuit stuff away from the case (to bend it back into shape), I'd probably just try and shim the battery contact to fit better 01.39.14 # once it was all reassembled 01.39.18 # shim? 01.39.44 # shim == stick small pieces of metal inbetween two parts to do fine-adjustment on spacing/offset/angle/whatever 01.39.59 # ah 01.40.13 # As in: can you just wad up some aluminum foil to fill whatever gap you're seeing? 01.40.30 # that's essentially what the archos battery cover does 01.41.10 # no: the battery cover is the contact ( is attached to, anyway) 01.41.31 # and the cover is flexed like a spring 01.42.06 # it's held down becuase it's wwdged between the front cover and the back ( now bent) case 01.42.13 # you'd prolly be better off asking Linus, or someone who's actually disassebled the battery cover. =) 01.42.14 Join Bluechip [0] (~bluechip@pc1-colc1-3-cust223.colc.cable.ntl.com) 01.42.29 # with the bend, it's not wedged as much. 01.42.34 # good suggestion 01.42.35 # can i retrive the current tick? 01.42.37 # so shim under battery 01.43.16 # Bluechip: lots o references in mpeg.c for "current_tick". You could check there... 01.43.43 # thanks :)) 01.45.40 # firmware 1.17i, must be old.. 01.52.29 # interface pcb also differs (v1.2) 02.03.25 *** Saving seen data "./dancer.seen" 02.07.46 Join Asmotaku-Neko [0] (WinNT@ACB8B65F.ipt.aol.com) 02.07.51 # Hi there ! 02.07.53 # ^w^ 02.08.16 # !rules 02.08.23 # no ones. 02.08.30 # >.> 02.08.33 # <.< 02.08.43 # Anybody there ? 02.09.05 Quit Asmotaku-Neko (Client Quit) 02.14.29 Join LinusN [200] (~linus@labb.contactor.se) 02.14.56 # hiya, LinusN =) 02.15.00 # hi 02.17.45 # ahh, is that a man who can tell me how to access a timer with units smaller than a second? ;) 02.21.02 # probably, yes 02.21.17 # one tick is 10ms 02.21.36 # just can't work out how to read the current value into a variable! 02.22.24 # also - does it wrap at say, 2^65 02.22.25 # it *is* in a variable 02.22.29 # current_tick 02.22.44 # it is an unsigned 32-bit 02.23.22 # and is it free running or reset every X seconds? 02.23.31 # if you use the TIME_AFTER() and TIME_BEFORE() macros, you won't have to think about the wrap issues 02.23.42 # it is free running 02.24.06 # brilliant - thank you - i will grep for these macros :) <- happy again 02.24.20 # see the implementation of sleep() in kernel.c 02.24.32 # the macros are defined in kernel.h 02.24.59 # brilliant - I will try to work out how to create a patch for my new game tonight :) 02.25.05 # this was my last problem 02.25.08 # a game! nice! 02.25.14 # Othello 02.25.28 # with subsecond timing? 02.25.32 # simple, but i just wanted to get used to accessing the display/keys/timers/etc 02.25.50 # i want to slow the oponent down - he moves too quickly 02.25.55 # ah 02.26.34 # wouldn't sleep() do fine then? 02.27.12 # i also tried button_get_w_tmo(), but they did not give me the flexibility i required over the keyboard 02.27.40 # i see 02.30.39 # it will make sense when you see the code 02.30.49 # looking forward to it 03.00.46 Part LinusN 03.33.39 # damn 03.33.44 # I missed Linus 03.34.32 # 0009 nop 4041 9481550 2346.3 03.35.11 # nop takes an an average of 2346 instructions to execute 03.35.36 # that's actually MORE than many instructions 03.36.25 # hmm 03.37.13 # :-o 03.37.17 # Stevie: Scan the IRC logs for today. Someone pointed out a link to a company that's offering a disassembly package of the Archos for like $2k a pop. =) I wonder if they got any of their info from rockbox? 03.37.34 # disassembly package? 03.37.38 # what do they mean? 03.37.51 # I think it's hardware: component lists, circuit diagrams, etc. 03.37.57 # heh 03.38.02 # fuck that, we already have all those 03.38.04 # Not sure if there's any software disassembly/analysis 03.38.06 # however incomplete 03.38.08 # could write a simple disassembler in an hour or so :( ...$2000 - LOL 03.38.15 # write? 03.38.17 # we HAVE one 03.38.20 # I know. That was my thought 03.38.26 # comes with the source 03.38.29 # sh2d.c 03.38.37 # lol 03.38.42 # ;) 03.38.48 # still working my way though it all :) 03.38.49 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 03.38.49 # * OliverKlozoff has used it extensively 03.40.47 # anyone know if the preprocessor will handle this okay: 03.40.49 # (HZ*((REPEAT_START+1)/10)) 03.41.31 # i'm expecting 70 03.42.16 # ...given HZ = 100 and REP_ST = 6 03.42.30 # integer division? 03.42.42 # there is a 0.7 in the middle of it all 03.42.56 # (6+1)/10 = 0.7 03.43.27 # or (6+1)/10 = 7/10 = 1 (or whatever int division gives you...I forget) 03.43.35 # zero 03.43.46 # round down 03.44.25 # fractional portion is dropped 03.44.37 # is that a no then? 03.44.40 # right. I usually avoid at all costs. =) 03.44.52 # I think it'll always give you zero. Not 70 03.45.02 # what i feared 03.45.12 # Just multiply first, then divide 03.45.26 # D'OH! 03.46.31 # * Bluechip cowers in a pool of missing the obvious 03.46.54 # =) it's 'cause your mind is involved in "higher things" ;) 03.46.59 # Einstein couldn't do math, either 03.47.12 # ty ;) 03.50.11 # lol 03.55.01 Quit BoD[] ("hhh") 03.57.54 Join nu [0] (neuro@got.lost.in.the.witches-world.com) 03.58.03 # good evening 03.58.11 # evenin 03.58.21 # hi Bluechip 03.58.33 # is LinusN ever around ? 03.58.52 # he popped on earlier, solved my problem and went away again 03.58.57 # ...such a nice man :) 03.59.21 # eheh 04.03.27 *** Saving seen data "./dancer.seen" 04.04.36 # i was browsing the internet looking for VBRI header data when i came across a log of this channel where LinusN stated he had figured it out 04.05.17 # since its 4am where i live and i need this done by yesterday, it would've been so very nice of him to share his findings with a perfect stranger ;) 04.05.33 # sorry, all alien to me - i have a friend who may know - but he is not onlne atm :( 04.05.45 # if he had been online - he surely would have helped 04.05.59 # thanks anyway...i'm probably too tired to even understand anything 04.06.13 # i'll pop in tomorrow if i cant figure out this stuff by myself 04.06.14 # thanks again! 04.06.15 # later 04.06.18 # l8rz 04.06.24 Quit nu ("smash is the way you deal with your life, like an outcast you're smashing your strife") 04.09.44 Join Stevie-O [0] (whatsit2u@user-2inimh5.dialup.mindspring.com) 04.15.05 Quit adi|home (Read error: 54 (Connection reset by peer)) 04.16.34 # 26940 04.16.35 # ok 04.16.42 # so i need a 27 GHz CPU 04.16.59 # to emulate the archos at full speed 04.17.04 # lol. You can have mine. I just upgraded 04.17.05 # ;) 04.19.03 # what 04.19.09 # you have a 28GHz now? 04.21.17 # 24948 04.21.17 # woo 04.21.23 # now I only need a 25GHz CPU 04.22.27 # damn, I need a beowulf cluster of ..... nm 04.22.59 # you've been reading too much slashdot 04.23.20 # nope. I was channeling. ;) 04.23.46 # either of ya'll know anything about the sim? 04.24.24 # I know it doesn't work well for me, so i stopped trying to use it. 04.25.28 # It's working okay for me, but it looks like it's showing the mp3buf size as: 135M (in the code). The Info display shows 6.6M (maybe a var limit). 04.25.43 # Maybe it's not limiting ram size to 2M? hmmm 04.25.47 # wow 04.26.15 # when I run the optimized Release build 04.26.35 # Yah, I think I must be trashing the memory somewhere. 04.26.40 # Only a 9GHz CPU is required to execute full-speed 04.26.52 # 'Cause when I run a fresh build, it shows 0.928M ram 04.28.25 Quit OliverKlozoff (Read error: 110 (Connection timed out)) 04.29.47 # * Stevie-O notes that the clock almost runs full speed in Release mode 04.29.52 # you,re trashing mem 04.30.05 # good work stevie 04.30.27 # don't I get a "good work" (for trashin memory)?? ;) j/k 04.31.07 # naw. 04.31.14 # sign 04.31.25 # *sigh 04.31.33 # trashing memory's easi in C 04.31.43 # true dat 04.31.51 # tomorrow I get my new 60gb hdd 04.33.12 # so, stevie, when do the rest of us get to play with the emulator? 04.43.24 # jzoss, are you running the win or x sim? 04.43.29 # x sim 04.43.36 # I've narrowed it down to: 04.43.45 # memset(mp3buf, 0, mp3end-mp3buf) 04.44.37 # assuming end-buf is <= ptrdiff 04.44.50 # Before that line, mp3end-mp3buf = 973380. Afterwords, =135770052 04.45.33 # shouldn't 04.45.46 # I know. It's not rocket science. Hmmm. 04.46.01 # I'm sure it's something trivial. :S 04.47.09 # unless you are overwriting the stack space 04.47.27 # yah, but I tried shortening the size by a byte and it didn't help 04.48.10 # divide it by 2 04.48.47 Part Bluechip 04.48.57 # Yah, I was goin there next. /2 works okay 04.50.14 # apparently you are overwrting mp3end 04.50.28 # yup 04.52.48 # don't do that! ;) 04.53.06 # oh! thx 04.54.49 Join adi|home [0] (~adi|home@as5300-11.216-194-24-173.nyc.ny.metconnect.net) 04.55.41 # okay, so here's the scoop: memset(mp3buf, 0, mp3end-mp3buf-4) works, but memset(mp3buf, 0, mp3end-mp3buf-3) does not 04.55.57 # I'm thinking that maybe memset is writing in units of (int) or something instead of units of (char) 04.56.40 # shouldn't be 04.56.54 # memset works on bytes 04.57.49 # the prototype (in firmware/common) shows memset(void*, int, size_t) 04.58.15 # is mp3end < mp3buf? 04.58.44 # size_t, sure. but it's a byte count. 04.59.04 # but fine, test it. 05.01.00 # Hmmmm... it's actually mp3buf (the ptr value) that's getting overwritten. 05.01.59 # w/ memset(mp3buf, 0, mp3end-mp3buf-3), before call mp3buf is 0x808d5a0 and after is 0x808d500 05.02.30 # that doesn't make any sense. It must be late or something. :S 05.03.12 # is it taking the address of the first arg? 05.04.21 # or is another thread doing it? 05.05.29 # ah. 05.05.49 # you're hitting mpebuf. 05.08.05 # I don't see an mpebuf anywhere... 05.08.53 # I wonder if I need to be doing a make clean everytime.... 05.09.38 # 3=e 05.09.56 # make clean's probably a good idea 05.10.34 # bbl 05.13.34 Part jzoss ("Client exiting") 06.03.30 *** Saving seen data "./dancer.seen" 06.36.28 Join Bluechip [0] (~bluechip@pc1-colc1-3-cust223.colc.cable.ntl.com) 07.01.47 # the doc on creating patches is a little contradictory - is there a simple answer? 07.02.17 # please bear in mind that THIS is all completely new to me 07.03.26 # maybe there is a preferred doc? 07.03.55 # i think everybody had gone to bed :( 07.07.41 Join Josh_ [0] (~Jet8810@adsl-211-194-198.mia.bellsouth.net) 07.20.07 Join thu [0] (~thu@h24-87-64-169.vc.shawcable.net) 07.24.55 Quit Jet8810 (Read error: 110 (Connection timed out)) 07.52.30 Quit earHurts (Remote closed the connection) 07.56.53 Nick dw|gone is now known as dwihno (dwihno@h193180246067.kommunicera.umea.se) 08.03.33 *** Saving seen data "./dancer.seen" 08.12.02 Quit thu ("Client exiting") 08.44.02 Join matsl [0] (~matsl@dhcp101.contactor.se) 09.03.35 Part Bluechip 09.31.05 # exit 09.31.07 Quit hardeep ("BitchX: faster than a speeding bullet, more powerful than a locomotive") 10.03.34 *** Saving seen data "./dancer.seen" 11.05.21 Join Kuji [0] (~kuji@cuji.gotadsl.co.uk) 11.05.37 Part Kuji 11.33.47 Join Kuji [0] (~kuji@cuji.gotadsl.co.uk) 11.33.57 # logbot seen linusn 11.34.14 >>> "help" by Kuji (~kuji@cuji.gotadsl.co.uk) 11.34.26 >>> "cmd" by Kuji (~kuji@cuji.gotadsl.co.uk) 11.34.33 >>> "seen" used by Kuji (~kuji@cuji.gotadsl.co.uk) [snoop prevented] 11.34.44 >>> "SEEN" used by Kuji (~kuji@cuji.gotadsl.co.uk) [snoop prevented] 11.49.42 Part Kuji 11.55.01 Join LinusN [200] (~linus@labb.contactor.se) 12.02.15 Part LinusN 12.03.35 *** Saving seen data "./dancer.seen" 12.06.27 Join Kuji [0] (~kuji@cuji.gotadsl.co.uk) 12.10.37 Join olivier [0] (~olivier@www.linux-nerd.com) 13.35.39 Quit Josh_ ("Client exiting") 13.59.57 Part Kuji 14.03.37 *** Saving seen data "./dancer.seen" 14.12.35 Quit olivier ("Aller, tous au ciné !") 14.31.05 Join Bagder [241] (~daniel@as3-3-2.ras.s.bonet.se) 14.53.53 Join LinusN [200] (~linus@labb.contactor.se) 14.54.01 # hey Linus 14.54.07 # yo 15.00.45 # mu! 15.00.49 # mamma mu! 15.00.53 # <-- = kråkan 15.01.19 # med flax! 15.01.30 # :O 15.02.28 # so, do you guys hear any difference between the soundcheck firmware and the standard? :-) 15.02.47 # soundcheck firmware? 15.02.48 # I never tried it 15.03.04 # dwihno: read the mailing list 15.05.25 # * dwihno has 2300 mails in the inbox 15.05.30 # It's summer for crying out loud! :) 15.05.45 # naaah 15.05.48 # :-) 15.06.59 # Yes 15.07.04 # It's neato! :) 15.07.23 # Bagder: Will you and Björn go to Skellefteå this weekend? 15.07.35 # no 15.07.46 # why would we? 15.07.47 # I guess it's not worth it if not E-type is not around ;) 15.07.53 # hahaha 15.07.54 # Björn went there last year 15.10.02 # you mean there's some kind of festival or something? 15.10.58 # Yes. 15.11.04 # Skellefteåfestivalen. 15.11.10 # Björn was there last summer. He watched E-type. 15.21.40 # if i add clip-protection code in rockbox, how would we want it to behave? 15.21.51 # clip protection? 15.21.52 # what's that? 15.22.28 # volume + loudness + max(bass, treble) must be <= 0dB 15.23.04 # it means that if we want lots of loudness, we must lower the volume to avoid clipping 15.23.48 # hm 15.23.59 # Make it behave ... well :) 15.24.42 Quit Stevie-O (Read error: 110 (Connection timed out)) 15.25.07 # so, do we lower the volume automatically when raising the loudness, or do we prevent the setting of high loudness values? 15.25.38 # probably. 15.28.21 # helpful comment... 15.28.34 # I really don't know 15.28.43 # I wouldn't care much for any version myself 15.29.10 # I think 15.29.16 # I vote for lowering the volume 15.29.35 # that's what we do on the player 15.29.49 # I always fine tune my settings 15.29.57 # So limitations are not really an issue. 15.31.14 # i will of course make it optional 15.31.52 # "We, Mitsubishi Electric Corporation, are planning to use cURL to our software products." 15.31.57 # <= from a mail I got 15.31.59 # cool 15.32.15 # yeah! 15.32.24 # 24-tmmarsmyndigheten uses curl 15.32.45 # they do? neato 15.33.15 # they called me a few months ago asking for help 15.33.40 # aha ;-) 15.34.05 # Whoa 15.34.12 # Coolness. 15.37.13 # gotta go, cu 15.37.15 Part LinusN 15.55.23 Join Stevie[FP] [0] (~whatsit2u@65.114.136.196) 16.03.41 *** Saving seen data "./dancer.seen" 16.17.46 Nick dwihno is now known as dw|gone (dwihno@h193180246067.kommunicera.umea.se) 16.51.20 Join hardeep [0] (1098@208.247.65.237) 17.15.43 Join mecraw [0] (~mecraw@69.2.235.2) 17.16.51 Quit Bagder ("http://daniel.haxx.se") 18.03.43 *** Saving seen data "./dancer.seen" 18.15.49 Join Zagor [242] (bjst@as9-5-6.k.s.bonet.se) 18.16.14 # hi guys 18.23.12 # hi 18.23.56 # hey Z 18.27.52 # * Stevie[FP] pokes Z 18.28.07 # hi stevie :) 18.28.10 # http://www.qrpff.net/~stevie/jbremu/revelation.jpg 18.28.16 # cheq eet 18.28.39 # yay! 18.28.50 # gets better 18.29.04 # it wasn't *supposed* to be in USB mode :D 18.29.12 # but I had a glitch in the ADC emulation 18.29.13 # http://www.qrpff.net/~stevie/jbremu/fixedadc.jpg 18.29.45 # wow, i've never seen that message :) 18.29.59 # One of the things I find interesting about that message 18.30.06 # is that it implies Archos has support for FAT16 18.30.25 # that was exactly my though 18.30.26 # t 18.30.28 # ... except FAT16 filesystems can only go up to 2GB 18.30.37 # and the smallest JB I know if is 6GB 18.30.37 # exactly. so rather pointless. 18.30.40 # s/if/of/ 18.30.54 # http://www.qrpff.net/~stevie/jbremu/power.jpg 18.31.39 # and http://www.qrpff.net/~stevie/jbremu/power2.jpg 18.32.08 # It took me a fscking WEEK to get this far 18.32.10 # i'm impressed 18.32.19 # err 18.32.25 # to get around the problem I was having 18.32.31 # it's a bit more than an 1815 lcd emulator now :-) 18.32.37 # lol 18.32.40 # just a bit :D 18.32.42 # you know why it wasn't working? 18.32.49 # why? 18.32.58 # cuz the damn thing was trying to record 18.33.04 # !? 18.33.10 # as part of the startup, the recorder (or at least the FM) puts the MAS in record mode 18.33.19 # and waits for like 8KB or so of data 18.33.44 # stramge 18.33.47 # very. 18.34.01 # so I had to emulate recording 18.34.15 # which meant emulating PA11, PB15, PB14, IRQ3, IRQ6 18.34.20 # ouch 18.34.23 # and address 0x04000000 18.34.32 # I cheated on one thing 18.34.46 # I just hold the 'data ready' pin low 18.35.22 # oh! 18.35.25 # maybe you can help me 18.35.36 # I can't get the device to restart properly after exiting USB mode 18.36.18 # it apparently sets up a watchdog timer 18.37.11 # according to the schematics, the watchdog output pin is connected to the watchdog input pin on the RTC 18.37.23 # and that the IRQ output on the RTC is connected to PA12 18.37.29 # but I don't understand what that does overall 18.38.15 # i don't know if anyone's every messed with rebooting. 18.38.43 # are the schematics even correct about those pins? 18.39.42 # oh, I also need some empirical information on the Recorder 18.40.02 # runtime values of the AN0-AN7 18.41.20 # (when not plugged in and no buttons pressed) 18.43.07 Quit matsl ("Client Exiting") 18.43.10 Join Norrin [0] (~JSmith123@ip68-110-25-172.om.om.cox.net) 18.43.28 # ahh 18.43.30 # I see 18.43.35 # it causes a manual reset 18.44.32 # it's a pretty safe bet to not trust the schematics :) 18.44.33 # Hello all. Question: The daily builds change in size even though the changelog reflects no changes. Also, the notes on the homepage reflect changes being made when don't appear in the CVS. Comments? 18.44.56 # cvs is kaput 18.45.11 # Norrin: a) the date changes, and compresses differently == different size b) sourceforge CVS is having baaaaad problems, causing erratic daily status display 18.45.53 # Thanks for the update. Excellent product by the way. Look forward to see what Rockbox comes up with next. 18.46.34 # http://www.qrpff.net/~stevie/jbremu/shutdown.jpg 18.46.46 # see, now I need some damn buttons! 18.47.29 # hehe 18.51.44 Quit Norrin () 18.58.09 # ;) 19.42.48 Quit hardeep ("BitchX: better than a penis enlargement!") 19.45.04 # Stevie[FP] an0 om the rec? 19.45.08 # 3ff 19.46.14 # that one I could have guessed ;) 19.46.31 # okay 19.46.48 # who wants to know the trigger thresholds for charging/not charging an FM 19.47.06 # got an old one with 1.17i frimware/// 19.48.46 # http://www.qrpff.net/~stevie/jbremu/charged.jpg 19.48.49 # http://www.qrpff.net/~stevie/jbremu/charging.jpg 19.51.39 Join Tiberious [0] (~none@12-216-244-18.client.mchsi.com) 19.52.24 # Question, I can no longer turn on my recorder 15 gig, as with the power and usb on it freezes and turns off, without the usb is loads a little bit,then the screen flickers and a strange sound comes from the unit. ANy idea? 19.52.50 # drive dead? 19.53.04 # No idea,this just happened. 19.53.35 # jesus im a moron... 19.53.45 # Plugging the power in the wrong hole doesn't help. :P 19.54.44 # you will also have to charge it then for a while.. 19.54.58 # okay,thanks 19.58.55 # lol 19.59.21 # Stevie[FP] also need other an values ? 20.03.14 # an2,an4,an5 typically float around 000-002 20.03.44 *** Saving seen data "./dancer.seen" 20.03.56 Join matsl [0] (~matsl@as13-4-5.mal.s.bonet.se) 20.04.06 # pressing play raises an5 to ~2dc 20.06.53 Join _aLF [0] (alexandre@AGrenoble-203-1-12-172.w81-51.abo.wanadoo.fr) 20.24.33 Join hardeep [0] (1098@208.247.65.237) 20.24.35 # the v1.2 interface uses a different power regulater. 20.29.23 Join Jet8810 [0] (~Jet8810@adsl-34-221-14.bct.bellsouth.net) 20.44.52 Join Guest [0] (jirc@ti231210a080-0080.bb.online.no) 20.46.22 # help! I have just dissected my jbr20 to connect it directly to my computer, but the IDE-cable does'nt fit the hard-drive!! 20.48.42 # Guest: you need an adapter 20.48.53 # Guest: you can find them at most every electronics store 20.50.03 # OK, thanx.... 20.50.07 Quit Guest ("Leaving") 20.59.57 # sigh unless 'my computer' is a laptop that isn't verry surprising... 21.02.58 Join mecraw_ [0] (~mecraw@69.2.235.2) 21.06.46 Quit hardeep (calvino.freenode.net irc.freenode.net) 21.06.46 NSplit calvino.freenode.net irc.freenode.net 21.06.46 Quit Tiberious (calvino.freenode.net irc.freenode.net) 21.06.46 Quit mecraw (calvino.freenode.net irc.freenode.net) 21.06.46 Quit MT (calvino.freenode.net irc.freenode.net) 21.08.59 NHeal calvino.freenode.net irc.freenode.net 21.08.59 NJoin MT [0] (mt@fido.impulsed.net) 21.17.05 # wtf is Z doing 21.17.58 # got questions? 21.25.26 # ah 21.25.31 # no, I got answers 21.26.06 # as in, when the Archos firmware considers the FM charged 21.26.14 # http://www.qrpff.net/~stevie/jbremu/charged.jpg 21.26.18 # note the value of AN7 21.27.36 # interesting 21.27.46 # now 21.27.51 # that's at 100 (decimal) 21.28.11 # so 0x64 21.28.42 # also note that those values are shifted left 6 bits before being fed to the program being run 21.29.04 # (which will then shift RIGHT 6 bits..) 21.29.45 # at 101, it still says charging 21.29.59 # once it's <= 100, however, it latches on 'charged' 21.30.19 # http://www.qrpff.net/~stevie/jbremu/charging.jpg 21.30.43 # until it hits the threshold value of 150 21.32.22 # interesting, but not really useful. it is generally acknowledged that delta-V is the right way to determine charging completed 21.32.29 # delta-V? 21.33.27 # a dip in voltage can be seen just as the battery becomes full 21.33.54 # it has to do with increased resistance, leading to higher temperature 21.34.48 # hm 21.34.57 # that might work for NiCd or NiMH 21.35.03 # but does it work for Li ion? 21.35.05 # right, that's what it's for 21.35.22 # i don't know much at all about the liion charging cycle 21.35.23 # do keep in mind that the FM uses a lithium ion battery 21.35.38 # yes, but it also handles the charging completely in hardware 21.35.38 # li ion batteries don't have much of a 'cycle' 21.35.50 # all you do is keep feeding it current 21.36.24 # the LTC1734 just lowers the output current as the battery becomes more full 21.36.41 # * Stevie[FP] read the spec sheet a couple of weeks ago 21.36.58 # right, but there's no way we can affect any of this from software is it? 21.37.06 # not that i'd like to... :-) 21.37.31 # no 21.37.47 # when the battery hits the 'full mark' 21.38.05 # which is decided by the voltage being >= 4.1V or 4.2V (depending on which LTC1734 version used) 21.38.54 # the value read by AN7 will drop to nearly zero 21.39.12 # ah, right. we currently don't ever show the fm recorder as finished charging 21.39.51 # actually we do (prematurely) 21.40.13 # the battery looks to be at 100% long before it's really completely charging 21.40.14 # ok. i'm a bit behind on the fm details... 21.40.35 # unless the Recorder has another way of indicating charging vs not charging 21.43.04 # no, it has the same problem on the regular recorder. we show the voltage as if supplied by the batteries, which means it indicates full long before actually completed 21.43.48 # okay 21.44.08 # does the recorder have some sort of 'we are currently charging' indicator? 21.44.11 # mike holden is looking into various ways to fix/clarify that 21.44.24 # Stevie[FP]: yes, it animates the graphic battery symbol 21.44.33 # like the original archos fw? 21.44.42 # yes, something like it 21.44.50 # is there a generic 'are we charging' function? 21.45.43 # there's a global 'charge_state' variable 21.46.10 # 0 = not charging, 1 = charging, 2 = trickle 21.46.33 # actually, 2 = top-off, 3 = trickle 21.47.15 # that one should really be an enum... 21.47.50 # i'm off a bit, bbl 21.54.17 # ok 22.03.48 *** Saving seen data "./dancer.seen" 22.08.30 # * Stevie[FP] wonders wtf these transistor-type things are 22.22.40 # I regret that I don't understand at all how this damn thing powers on/off 22.33.26 Join LinusN [200] (~linus@labb.contactor.se) 22.33.36 # sup Linus 22.33.40 # hi 22.33.51 # Stevie[FP]: can you do me a favour? 22.34.01 # depends on the favour 22.34.11 # * Stevie[FP] wonders if it'll be 'stop bugging you' :P 22.34.19 # :-) 22.34.37 # btw 22.34.45 # did you know the original archos fw supports fat16? 22.34.51 # no, can you see what the orig firmware writes to the direct config registers of the MAS? 22.35.03 # oh 22.35.09 # yeah I have that info 22.35.24 # Stevie[FP]: yeah, i saw that message when i shrunk my jb partition to debug my "disk full" code 22.35.33 # http://www.qrpff.net/~stevie/jbremu/fixedadc.jpg 22.35.35 # oooh 22.35.39 # so its' the paritition size? 22.35.50 # that is one factor i think 22.35.53 # what's the minimum partition, you know? 22.36.05 # didn't care that much to find out, actually 22.36.09 # mkay 22.36.17 # how bout this 22.36.18 # did you know 22.36.27 # the original FW records from the built-in mic on startup? 22.36.44 # no i didn't, was surprised when you told us 22.36.48 # that's the problem I've been trying to figure out for a week 22.36.56 # It waits for like 8kb of data 22.37.08 # self test, perhaps? 22.37.08 # why would it do that... 22.37.17 # that's the only thing I can think of 22.37.20 # but it doesn't actaully validate the data 22.37.27 # how could it? 22.37.32 # mp3 frames? 22.37.42 # that, maybe, yes 22.37.43 # I just have it "read" garbage data 22.37.59 # look at this: 22.38.01 # http://www.qrpff.net/~stevie/jbremu/charged.jpg 22.38.12 # well, if the handshake signals behave ok, there is little chance of garbage data 22.38.39 # charged, yes 22.38.42 # when the value read by AN7 falls to <= 100, it considers charging complete 22.38.48 # http://www.qrpff.net/~stevie/jbremu/charging.jpg 22.39.02 # i guess it only uses a batt level threshold...? 22.39.06 # no 22.39.11 # it's not the battery level 22.39.15 # oh, its the fm 22.39.16 # it's the 'external power' level 22.39.26 # ya 22.39.34 # it's a way to determine if we're still charging on the FM 22.39.37 # (^: 22.40.06 # looks like they have added the extpower with the charging current 22.40.19 # also 22.40.24 # oh, nm 22.40.36 # you knew that already, it just isn't mentioned in adc.h 22.40.43 # * LinusN thinks the emulator is a kickass reverse engineering tool 22.40.53 # hehe 22.41.00 # it'd be more kickass if it was a little faster :( 22.41.02 # okay 22.41.04 # MAS stuff 22.41.08 # coming right up... 22.41.26 # nice, i'll go clean up the kitchen while you dig 22.42.38 # actually it's already logged (had to get the damn record mode emulationg working) 22.42.45 # I just need to filter out the writes to PBDR/PBIOR) 22.45.20 Quit Zagor ("Client exiting") 22.45.47 # Stevie[FP]: if you don't mind, i'd like the complete log (if it isn't toooooo big) 22.45.55 # well 22.45.58 # I can log a LOT of things 22.46.29 # I can even log individual instructions (which I will quickly rack up a few hundred megabytes if I do that) 22.47.22 # ok, i'd settle with MAS accesses then 22.47.42 # mkay 22.47.52 # I'll give you all the I2C stuff 22.47.56 # which includes the RTC 22.47.57 # nice 22.56.48 # okay 22.56.49 # http://www.qrpff.net/~stevie/jbremu/jbremu.log.bz2 22.56.54 # that's the raw log output 22.56.59 # nice 22.56.59 # not very pretty 22.57.14 # but it's fairly explicit 22.58.24 # just like i want it 22.58.29 # lol 22.58.31 # ok (^: 22.59.31 # how come you write "MAS I2C ..." and then (write RTC 0x13 <- 0x10)? 22.59.46 # because I didn't realize at first that it was a shared bus 23.00.03 # and the LCD is an i2c bus too 23.00.09 Join Tiberious [0] (~none@12-216-244-18.client.mchsi.com) 23.00.11 # so it was LCD I2C and MAS I2C 23.00.12 # no, i believe it is SPI 23.00.33 # that's for the MP3 data transfer 23.00.42 # no, no, the LCD is not I2C 23.00.47 # oh 23.00.52 # well it's close enough to I2C 23.01.02 # it's like I2C that's output only 23.01.04 # I2C has start/stop conditions and the LCD hasn't 23.01.10 # hm 23.01.13 # true 23.01.18 # well anyway 23.01.19 # nm 23.01.31 # I didn't realize initially that the MAS shared the line with the RTC 23.01.51 # (which is why I was *VERY* confused at first when I saw address D0 -- I was like 'wtf? that's not in the MAS docs...') 23.02.12 # :-) 23.05.46 # what we *really* need is the schematics for that M3Po device >:D 23.06.08 # i guess they look pretty much like the archos 23.06.16 # the archos is not a unique design 23.06.20 # perhaps 23.06.58 # but the M3Po supposedly has speed change without pitch change (or something like it that implies that it programs the MAS it has) 23.07.26 # would be nice to steal that MAS code 23.07.34 # * Stevie[FP] grins 23.07.35 # indeed 23.07.50 # and if we were to emulate the HW well enough to be able to acquire that code 23.08.03 Join hardeep [0] (1098@208.247.65.237) 23.09.08 # hi hardeep 23.09.17 # hello everyone 23.09.22 # Now, that would be stealing, right? 8-) 23.09.29 # hi 23.09.32 # anyone here live in or been to Croatia? 23.09.32 # Hes: naaaaaaah 23.09.42 # nope 23.11.59 Quit Jet8810 ("Client exiting") 23.13.07 # Stevie[FP]: thanks, the log has the info i was looking for 23.13.32 # what info was that? 23.13.52 # i wanted to know what was written to I2C address 6A 23.14.00 # the Control Register 23.14.12 # Stevie[FP]: how is the emulator coming? 23.14.26 # elinenbe: it's great at emulating an unformatted hard drive 23.14.32 # ;) 23.15.07 # I can't wait to try it :) 23.15.19 # you can watch it in action here: 23.15.23 # http://www.qrpff.net/~stevie/jbremu/fixedadc.jpg 23.16.12 # it's a very enlightening tool.. 23.16.32 # and it's friggin' cool as well 23.16.49 # it's only enlightening if you want to know what it does if it doesn't like the filesystem on the HD :P 23.17.15 # or if you want to trace the MAS communication... 23.17.24 # true 23.18.06 # which could give us some goodies... 23.18.53 # nothing useful 23.19.48 # I just read a rumor about getting some stuff from the M3Po 23.21.26 # hi hardeep, anything new on the dynamic-patch ? 23.22.20 Quit mecraw_ ("Trillian (http://www.ceruleanstudios.com)") 23.22.25 # ricII: nope, just waiting for it to be approved/rejected now 23.24.05 # I will keep my fingers crossed than :) 23.24.37 Join [IDC]Dragon [0] (jirc@pD9512FAF.dip.t-dialin.net) 23.24.52 # <[IDC]Dragon> Hi! 23.24.55 # hi 23.25.07 Part Tiberious 23.25.23 # <[IDC]Dragon> Remember the UART boot? It's working now. 23.25.53 # you downloaded and executed some code? 23.26.00 # <[IDC]Dragon> Yes. 23.26.03 # wow 23.26.29 # <[IDC]Dragon> I made a liitle monitor to download, it can read+write memory. 23.26.49 # c00l 23.27.18 # <[IDC]Dragon> The PC controls the momory of the box, in a way. 23.27.28 # <[IDC]Dragon> memory, i mean. 23.28.31 # <[IDC]Dragon> Using mem read, I was able to download the flash content (once again). 23.28.45 # <[IDC]Dragon> No upload yet ;-) 23.29.29 # <[IDC]Dragon> I have the "bad" flash, not in circuit programmable. 23.29.54 # <[IDC]Dragon> A chip is on order, I'm desperately waiting for it. 23.30.53 # <[IDC]Dragon> There's one more experiment i'd like to try: downloading the rockbox image using my monitor, then executing it. 23.31.14 # <[IDC]Dragon> I'm curious what that'll do. 23.31.36 # <[IDC]Dragon> First I need to init the DRAM controller, though. 23.31.48 # <[IDC]Dragon> Still with me? 23.32.23 Join diddystar5 [0] (Lee@AC8DBDDC.ipt.aol.com) 23.32.33 # hey linus 23.33.58 # i've been trying to get cvs to work for about 30 min and it won't 23.34.03 # :( 23.35.37 # cool things are happening, it seems. 23.36.31 # sourceforge sayed they should have had it fixed on the 19th 23.37.39 # the sf cvs sux atm 23.37.54 # <[IDC]Dragon> atm? 23.37.56 # * LinusN is in abbreviation hell 23.37.58 # hehe 23.38.00 # at the moment 23.38.09 # <[IDC]Dragon> aha! 23.38.40 # i wish i was a better programmer and i could have ssh access 23.38.53 # me too 23.39.04 # (wish i was a better programmer) :-) 23.40.06 # <[IDC]Dragon> I made a new hardware mod: the UART boot mod. Requires pulling LCD lines low instead of high. I used a tiny switch. 23.40.08 # the daily builds haven't had a successful cvs checkout for ages 23.40.26 # [IDC]Dragon: so you need a hw mpd to download code 23.40.39 # <[IDC]Dragon> mpd? 23.40.40 # LinusN: I think the hard disk read error handling code is quite ok at the moment, I did some extensive motorcycle driving suit testing during the last couple weeks 23.40.41 # mod 23.40.53 # Hes: nice to hear 23.41.10 # <[IDC]Dragon> Yes, unfortunately. That's just the way the ROM code does it. 23.41.15 Quit matsl ("Client Exiting") 23.41.25 # i also wish i was old enough to drive :) i have 3 more years 23.42.12 # Went to barcelona and back in a couple weeks, I think I had two playback stops while driving 23.42.18 # which were not due to dead batteries. 23.42.40 # <[IDC]Dragon> Linus, I'm thinking of a way to "authorize" flash images, avoiding anybody to flash the bleeding edge build. Do you have any ideas? 23.42.55 # One recovered after some 10-20 seconds, the other was probably because of no keylock and the pause button got pressed, and before I stopped the idle timer shut it off. 23.44.06 # [IDC]Dragon: why? 23.44.23 # Hes: that sounds good 23.44.37 # <[IDC]Dragon> Because you can lock dead your box. 23.44.55 # you can do that with released builds too, no? 23.45.14 # just interrupt the flashing and boom 23.45.17 # <[IDC]Dragon> The only way out is a UART boot, requiring that mod and serial mod. 23.45.52 # my point is, there is a serious risk regardless of which version you flash 23.45.58 # <[IDC]Dragon> Released like somebody checking it, then publishing it? 23.46.16 # Thought it might be my new driving suit has a better pocket 8-) 23.46.25 # Hes: must be that 23.47.10 # <[IDC]Dragon> If the image is OK, I don't see a significant risk. 23.47.32 # <[IDC]Dragon> Some sanity checks are in order, though. 23.47.57 # <[IDC]Dragon> What's the meaning of the mask value? 23.48.01 Join Jet8810 [0] (~Jet8810@adsl-34-221-14.bct.bellsouth.net) 23.48.18 # you mean the HW mask? 23.48.25 # <[IDC]Dragon> Yes. 23.48.55 # i'm not even sure it is a bit mask, but it tells you which version of the hw you are running on 23.48.59 # people modding there box, sould be aware of the riks when flashing.. 23.49.00 # so you can adapt 23.49.13 # ricII: we can flash it without modding 23.49.32 # <[IDC]Dragon> I'd like to tell Plaer, Recorder, FM apart to avoid the worst. 23.49.39 # O I didn't know that.. 23.50.11 # [IDC]Dragon: you can probably use the hw mask to do that, but there are other ways too 23.50.27 Join tracktheripper [0] (jirc@ACA320AA.ipt.aol.com) 23.50.34 # Evening 23.50.35 # <[IDC]Dragon> Like what? 23.51.03 # lots of things changed while I was away.. 23.51.46 # have you built a flashed rockbox yet? 23.52.00 # <[IDC]Dragon> Is it safe to fail if the mask value is different? 23.52.25 # [IDC]Dragon: different from what? 23.53.04 # <[IDC]Dragon> Differing between the current flash content and the image about to be flashed. 23.53.24 # the image shouldn't have mask should it? 23.53.38 # <[IDC]Dragon> diddystar5: not yet, but very close. 23.53.43 # it should copy the mask from the current flash 23.53.55 # cool 23.54.05 # why not just flash rolo ? 23.54.51 # <[IDC]Dragon> No. I see 2 phases: composing an image from the own box content (to preserve the mask value), and second flashing it. 23.55.06 # ah, then a mask check is in order 23.55.20 # <[IDC]Dragon> Yes, but is it enough? 23.55.24 Join BoD[] [0] (~BoD@m198.net195-132-85.noos.fr) 23.55.37 # hello ! 23.55.53 # so what's new in rockbox world 23.56.00 # <[IDC]Dragon> Which/how many mask values are out there? 23.56.05 # hewwo Bod[] 23.57.49 # hello BoD 23.57.56 Part diddystar5 23.57.58 # <[IDC]Dragon> For the flash administration: We would need one responsible person per mask value/hardware with the UART boot mod, who can validate images. 23.58.04 # im the only Rockboxer in the whole wide world who can't play Sokoban :-( 23.58.40 # [IDC]Dragon: have you been able to successfully flash anything at all?