--- Log for 01.01.117  Server: asimov.freenode.net  Channel: #rockbox
--- Nick: logbot  Version: Dancer V4.16  Started: 5 days and 16 hours ago

00.28.35 Quit    paulk-collins (Quit: Leaving)
00.36.35 Quit    pamaury (Ping timeout: 248 seconds)
00.53.45 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
00.58.24 Quit    PurlingNayuki (Ping timeout: 260 seconds)
01.17.32 Quit    Rower (Ping timeout: 245 seconds)
01.22.34 Join    Rower [0] (husvagn@d83-183-134-99.cust.tele2.se)
01.31.04 Quit    ender` (Ping timeout: 260 seconds)
01.36.07 #       <scorche> Oh - I hadn't noticed that the forums actually had a proper database error now - lovely
01.37.09 Quit    edhelas (Quit: Leaving.)
01.38.11 #       <scorche> Sorry folks, but I just cant fix it at the moment - and probably wont for a bit longer...  Family is over and we are prepping for the birth of the kid, so yay...
01.38.41 Quit    alexweissman (Remote host closed the connection)
01.39.08 #       <scorche> I won't be working for the next couple of months, so I will have time to completely re-do the server, but when I actually start that depends on how the kid sleeps and such, I guess.
01.54.31 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
01.57.01 ***     Saving seen data "./dancer.seen"
01.59.04 Quit    PurlingNayuki (Ping timeout: 260 seconds)
02.12.06 Join    aptzero [0] (~Adium@c-69-140-168-118.hsd1.md.comcast.net)
02.28.59 Quit    smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/)
02.29.22 Join    edhelas [0] (~edhelas@145.133.43.230)
02.32.10 Quit    edhelas (Client Quit)
02.49.11 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
02.53.43 Quit    alexweissman (Ping timeout: 258 seconds)
02.55.15 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
02.59.43 Quit    PurlingNayuki (Ping timeout: 260 seconds)
03.03.50 Quit    Strife89 (Quit: No Ping reply in 180 seconds.)
03.05.28 Join    Strife89 [0] (~quassel@adsl-98-80-185-155.mcn.bellsouth.net)
03.11.01 #       <dongs> haah
03.20.50 #       <fIorz> what happened? :-)
03.29.31 Quit    ZincAlloy (Quit: Leaving.)
03.34.48 Quit    idonob (Ping timeout: 264 seconds)
03.56.01 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
03.57.02 ***     Saving seen data "./dancer.seen"
04.00.04 Quit    PurlingNayuki (Ping timeout: 246 seconds)
04.14.01 Quit    aptzero (Quit: Leaving.)
05.10.50 Quit    Strife89 (Read error: Connection reset by peer)
05.11.47 #       <dongs> no just replying about the forum finally haveing a database error
05.12.36 #       <fIorz> IC :-)
05.14.36 Join    Strife89 [0] (~quassel@adsl-98-80-185-155.mcn.bellsouth.net)
05.18.51 Join    treaki_ [0] (~treaki@p5B11C0F8.dip0.t-ipconnect.de)
05.22.31 Quit    treaki__ (Ping timeout: 260 seconds)
05.40.07 #       <scorche> well, I fixed the database error at leastr
05.40.33 #       <scorche> the messages I mentioned earlier still stand for the "big fix" that needs to happen
05.51.03 Quit    __builtin (Read error: Connection reset by peer)
05.52.16 Join    __builtin [0] (~xray@rockbox/developer/builtin)
05.57.04 ***     Saving seen data "./dancer.seen"
05.58.05 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
06.02.22 Quit    PurlingNayuki (Ping timeout: 252 seconds)
06.52.35 Quit    TheSeven (Ping timeout: 240 seconds)
06.53.00 Join    TheSeven [0] (~quassel@rockbox/developer/TheSeven)
07.57.06 ***     Saving seen data "./dancer.seen"
08.01.09 Quit    naleo (Read error: Connection reset by peer)
08.01.45 Join    naleo [0] (~naleo@unaffiliated/naleo)
08.02.18 Quit    fs-bluebot (Ping timeout: 258 seconds)
08.03.49 Quit    bluebrother (Ping timeout: 258 seconds)
08.05.34 Join    bluebrother [0] (~dom@rockbox/developer/bluebrother)
08.05.49 Quit    naleo (Client Quit)
08.16.18 Join    fs-bluebot [0] (~fs-bluebo@xd9baf47d.dyn.telefonica.de)
09.00.02 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
09.04.24 Quit    PurlingNayuki (Ping timeout: 258 seconds)
09.07.47 Quit    Jinx (Ping timeout: 256 seconds)
09.38.19 Join    Mihail [0] (252d5c46@gateway/web/cgi-irc/kiwiirc.com/ip.37.45.92.70)
09.44.51 #       <Mihail> scorche: forum down again :(
09.57.07 ***     Saving seen data "./dancer.seen"
10.01.01 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
10.05.20 Quit    PurlingNayuki (Ping timeout: 258 seconds)
10.19.45 Quit    krnlyng (Ping timeout: 256 seconds)
10.21.48 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
10.23.26 Quit    alexweissman (Client Quit)
10.32.46 Join    krnlyng [0] (~liar@178.114.11.184.wireless.dyn.drei.com)
10.41.05 Join    RetroFan90 [0] (63eac4c5@gateway/web/freenode/ip.99.234.196.197)
10.49.02 Join    ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:ed36:1732:6f5d:bd90)
10.52.24 #       <RetroFan90> hello, what's up?
10.53.12 #       <RetroFan90> i am having some issues with my iPod Nano 1st Gen 2 GB White.
10.54.50 #       <RetroFan90> http://pastebin.ca/3751195
10.55.20 #       <RetroFan90> the error is kind hard to read because the screen is slightly damaged
10.55.26 #       <RetroFan90> kind of *
10.58.50 Join    pamaury [0] (~pamaury@rockbox/developer/pamaury)
11.01.56 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
11.02.16 #       <RetroFan90> hold on...
11.02.28 #       <RetroFan90> i think i figured it out :(
11.03.28 #       <RetroFan90> sorry for the trouble :)
11.03.44 #       <RetroFan90> Happy New Year.
11.03.50 Quit    RetroFan90 (Quit: Page closed)
11.06.27 Quit    PurlingNayuki (Ping timeout: 248 seconds)
11.29.57 Quit    dfkt (Ping timeout: 268 seconds)
11.38.46 Join    rela [0] (~x@pdpc/supporter/active/rela)
11.42.47 Join    edhelas [0] (~edhelas@145.133.43.230)
11.50.47 Quit    edhelas (Ping timeout: 260 seconds)
11.55.43 Join    paulk-collins [0] (~paulk@gagarine.paulk.fr)
11.57.08 ***     Saving seen data "./dancer.seen"
12.13.16 Join    fs-bluebot_ [0] (~fs-bluebo@xd9bef3d2.dyn.telefonica.de)
12.14.46 Quit    fs-bluebot (Ping timeout: 256 seconds)
12.16.54 Quit    bluebrother (Ping timeout: 265 seconds)
12.18.16 Join    bluebrother [0] (~dom@rockbox/developer/bluebrother)
12.30.22 Join    ender` [0] (krneki@foo.eternallybored.org)
12.42.52 #       <Mihail> pamaury: I have strange problem with internal flash in clip zip: if I set low voltage (CVDD2) and than revert this voltage back to normal - internal flash stop working. If I try reinit it - it stop on ACMD41. External sd card work without problems. I change voltages when flash at idle state (all related clocks off). Have idea what can be wrong or w
12.42.52 #       <Mihail> hat should I try?
12.52.00 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
13.00.49 Quit    idonob__ (Read error: Connection reset by peer)
13.03.04 #       <pamaury> Mihail: hard to say, first one would need to know what CVDD2 controls and what voltage you set it to
13.05.37 #       <pamaury> also I don't remember wat spec says about voltage changes. You can change the data lines voltage if you issue the problem voltage change command but for the main voltage of the chip, I think you can only do that when the reset pin is active
13.06.23 Join    idonob [0] (~Owner@S010610c37b922980.vs.shawcable.net)
13.06.27 #       <pamaury> did you try to reset te chip ? cause if the voltage of the chip drops, it may crash it until you reset it
13.08.57 #       <Mihail> CVDD2 control all memory (RAM, SD, internal flash) and probably something else
13.09.19 #       <Mihail> internal memory freeze with voltages < 2V
13.10.26 #       <Mihail> are you know how can I activate reset pin on AMS v2?
13.11.24 #       <pamaury> I'm reading the spec right now for mmc (should mostly apply to sd). It says you can cange the voltage if you put the chip in sleep mode (there is a command for that I think, and then you need to wake it up)
13.11.48 #       <pamaury> why do you need to turn CVDD2 low and high ?
13.12.17 #       <Mihail> I think it in sleep mode as all related clocks is down
13.12.31 #       <pamaury> you need a special command to sleep
13.12.34 #       <pamaury> (CMD5)
13.13.07 #       <pamaury> otherwise a chip is supposed to monitorr vcc and if voltage goes to low, it goes back to pre-init state and you need to redo a full init *in theory*
13.13.52 #       <Mihail> I want implement dynamically voltage scaling for CVDD2 and get less power consumption (more info on forum, but it down)
13.14.07 #       <pamaury> try puttting flash to sleep before changing the voltage I would say
13.16.10 #       * pamaury checks the SD spec
13.16.46 #       <pamaury> ok my mistake, sleep might only exists in MMC and not SD
13.17.06 #       <pamaury> also thinking about it now, I have now idea how the sd -> nand layer handles that
13.19.00 #       <Mihail> we do CMD7 (SD_DESELECT_CARD) before down clocks
13.20.01 #       <pamaury> that might not be enough, it puts the card in inactive mode only
13.21.13 #       <Mihail> I try power off it, but both flash and sd still work :(
13.21.50 #       <pamaury> power off what ?
13.22.27 Quit    idonob (Ping timeout: 248 seconds)
13.22.33 #       * pamaury thinks putting RAM, SD and internal flash on the same power rail is stupid
13.23.03 #       <dongs> heh
13.23.43 #       <Mihail> MCI_PWREN &= ~pwr_mask;             /*  power off all cards  */
13.24.12 #       <pamaury> hum, do you know what that does exactly ?
13.24.34 #       <pamaury> the internal storage seems like a hack with the sd to nand translation, that might explain the problem
13.24.44 Join    idonob [0] (~Owner@S010610c37b922980.vs.shawcable.net)
13.24.54 #       <Mihail> maybe I should try CMD0 before voltage changes?
13.25.07 #       <dongs> two things either 1) there's a enable/disable pin that turns off vcc to sd card(s) via fet/regulator or 2) puts card in poweroff mode
13.25.28 #       <pamaury>  the SD specs is a bit vague, the way I understand it, you need a true power down and then power up as soon as the voltage falls below 2.7V (or whatever the minimum operating voltage is). And true power down is <0.5V
13.26.00 #       <pamaury> and after true power down you need to send a CMD0 to reset and then reinit 
13.26.06 #       <dongs> I heard sandisk approached rockbox about opensores and that ended super well
13.26.59 #       <pamaury> but the code already sends CMD0 on reinit, not sure if CMD0 before power down helps
13.27.56 #       <pamaury> dongs: did they ? I think  Austria Microsystems approached us back in 2007
13.28.24 #       <dongs> and how well did that end?
13.29.16 #       <pamaury> they gave us the datasheets https://www.rockbox.org/wiki/AustriaMicrosystems
13.29.56 #       <dongs> err isnt the 3534 the one thats in clip+?
13.33.30 #       <pamaury> I think AS3534 is an audio codec
13.34.43 #       <pamaury> the clip+ uses that, it's integrated into the amsv2 soc
13.34.46 #       <pamaury> iirc
13.36.37 Join    edhelas [0] (~edhelas@145.133.43.230)
13.39.42 #       <Mihail> pamaury: no success with CMD0. External sd work good even at 1.5V
13.39.57 #       <dongs> huh is that evne in spec for SD
13.40.06 #       <dongs> i'd expect them to work at like 1.8 or something but not less than that
13.40.32 Quit    edhelas (Client Quit)
13.40.34 #       <Mihail> and sd was in 3.3V mode :)
13.42.11 #       <Mihail> pamaury: can you send to me AS3531 and AS3534 datasheets?
13.45.05 #       <dongs> ugh
13.45.17 #       <dongs> so I cant just install gcc-arm-embedded + make to build rockbox on windows?
13.45.31 #       <dongs> what other stuff does it need that requires cygwin+shit?
13.48.43 #       <dongs> oh, perl heh
13.49.36 #       <dongs> pamaury: https://daniel.haxx.se/rockbox-sandisk-connection.html this 
13.50.25 #       <__builtin> pamaury: are the datasheets from AMS public now?
13.57.09 ***     Saving seen data "./dancer.seen"
13.58.12 #       <dongs> oh look i found a clipzip i have
13.58.15 #       <dongs> is that > or < than clip+
13.59.18 #       <pamaury> Mihail: I don't have them
14.00.01 #       <Mihail> pamaury: maybe saratoga have?
14.00.10 #       <pamaury> no idea, or funman
14.00.39 #       <pamaury> but I don't know if that's going to help, we miss a lot of information about amsv2
14.01.07 #       <dongs> has anyone just tried emailing or calling them
14.01.12 #       <dongs> and referencing old events
14.01.33 #       <dongs> bla bla lunux bla bla opensores bla bla 2009 giev dox plz thx
14.02.58 #       <pamaury> now that you mentioned it, I think sandisk contacted us but then suddenly stopped responding
14.03.43 #       <Mihail> pamaury: yes but datasheets for AS3525 and AS3543 already help a lot
14.05.01 #       <pamaury> well AS3531 is an audio codec
14.06.08 #       <pamaury> ah maybe not, in any case I don't have the datasheet I think
14.09.40 #       <pamaury> Mihail: funman is the one who editted the wiki to put this datasheet list
14.11.38 #       <pamaury> Mihail: I can send you the linux as352x and as353x patches that funman sent me
14.13.42 #       <pamaury> Mihail: I sent an email to funman
14.18.20 #       <Mihail> thanks, it can be useful
14.18.44 Join    rockbox_fan [0] (c14d4632@gateway/web/freenode/ip.193.77.70.50)
14.18.50 #       <rockbox_fan> hey guys
14.20.12 Quit    rockbox_fan (Client Quit)
14.23.01 #       <funman> answered
14.24.32 #       <dongs> heh
14.24.35 #       <dongs> that was fast.
14.26.33 #       <Mihail> pamaury: Did you have idea how can I reset internal flash? I look at linux/drivers/mmc/host/dw_mmc.c and try use RST_N but no success.
14.27.10 #       <dongs> if its really nand>sd translation in hardware, you probably cant
14.29.05 #       <funman> google as3543 gives a pdf as 1st link
14.30.00 #       <Mihail> dongs: sd2nand controller should have way to reset?
14.30.22 #       <dongs> Mihail: well, nand has no r eset pin iirc.
14.30.27 #       <dongs> it could have some sequence to internally reset I guess
14.30.47 #       <funman> google gives as3531 pdf as 2nd link
14.31.30 #       <Mihail> I think I should find way to reset sd2nand controller, not nand
14.31.50 #       <dongs> Mihail: that would probably be peripheral power registers that enable/disable clocks/reset them
14.31.56 Join    johnb3 [0] (~johnb3@p57B45981.dip0.t-ipconnect.de)
14.32.17 Join    aptzero [0] (~Adium@c-69-140-168-118.hsd1.md.comcast.net)
14.32.17 #       <dongs> (that would probably reset both extenral sd and nand together tho)
14.32.18 #       <Mihail> funman: it just product brief
14.32.19 #       <johnb3> Mihail: have you seen https://www.rockbox.org/wiki/Main/SansaAMS#Hardware_Info it has links to various docs
14.32.52 #       <dongs> hweh the arm9* ds's are particularly worthless
14.32.55 #       <dongs> since its just the core
14.33.47 #       <johnb3> but not for AS3531 and AS3534, sorry, wrote this too quick
14.36.30 #       <Mihail> dongs: we disable all clocks already, power off just don't work (probably memory powered directly) and I don't know how reset cards
14.40.42 #       <Mihail> dongs
14.40.42 #       <Mihail> dongs: BTW are you measure voltages on nand before desoldering it?
14.40.59 #       <dongs> nope, but i have other clip+s i can try with
14.41.02 #       <dongs> i got a drawer full of dead ones.
14.41.07 #       <dongs> :D
14.41.18 #       <dongs> which is why I'm super interested in making the shit work wiht nand flash I can acutally buy and resolder.
14.42.08 #       <dongs> its at 2.8V
14.42.11 #       <dongs> just like the rest of the system
14.42.34 #       <Mihail> ok, thanks!
14.43.06 #       <dongs> jtag I/Ovoltage was also 2.8
14.43.20 #       <dongs> makes sense, since they don't have to care about buck/boost battery and can just step it down always
14.51.59 Nick    soap_ is now known as soap (~soap@rockbox/staff/soap)
15.04.19 Quit    ZincAlloy (Quit: Leaving.)
15.05.41 Join    ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:6451:efa5:b96e:2814)
15.20.38 Quit    johnb3 (Ping timeout: 256 seconds)
15.41.19 Join    skapazzo [0] (~skapazzo@151.9.205.1)
15.46.24 #       <Mihail> possible I found which type of nand (or similar) we have in sansa players: http://www.longsys.com/en/products/detail.asp?id=243
15.49.03 #       <dongs> ill call them next week. but I very much doubt it.
15.49.49 #       <dongs> Mihail: if it was really SD interface WHY have ~40 pins connected on clip+, and in same way you'd hookup regular nand.
15.52.15 #       <Mihail> maybe their etSD partially compatible with nand?
15.52.39 #       <dongs> it doesnt really make sense. also did you see the die pic? all pins are actualyl connected
15.52.50 #       <dongs> http://i.imgur.com/eCKebg9.jpg
15.52.59 #       <dongs> you dont need 40 signals for SD in any way
15.53.03 #       <dongs> even for 8bit sdio
15.53.44 #       <dongs> eMMC has like 150balls in bga but only ~12 are used for signal and a bunch more for power/gnd but thats it
15.55.10 Join    edhelas [0] (~edhelas@145.133.43.230)
15.55.35 #       <dongs> anyway, from manufacturing/part sourcing point of view it doenst make sense
15.55.58 #       <dongs> "lets put some strange flash in these so we always have to keep manufacturing it, and nobody else will want to buy from us cuz its non-standard"
15.56.36 #       <dongs> i suppose i could tap a couple pins on a working sansa, that match into nand control pins like CE/WE/whatever and see if those are accessed during boot/operation
15.56.42 #       <dongs> with timing that looks like something that would be nand-related.
15.57.02 #       <dongs> also tap those "NC" pins and see wtf is passing over those :)
15.57.10 ***     Saving seen data "./dancer.seen"
15.58.26 #       <Mihail> did you try connect nand from sansa as regular nand to some controller?
15.58.43 #       <dongs> no, i have it in a socket but I need to find the matching board where i can plug it into. its omsewhere in my pile of shit
15.58.49 #       <dongs> that was my todo list for next week
15.58.55 #       <dongs> to try and read out nand flash ID or something 
16.02.39 #       <dongs> cool, found it
16.03.30 #       <dongs> will write some quick test code when its not midnight. probly tomrorow.
16.03.52 #       <dongs> looks like i have the code too
16.03.52 #       <dongs> hmm
16.15.22 Join    n3m9 [0] (~n3m9@ANantes-652-1-57-61.w90-59.abo.wanadoo.fr)
16.19.02 #       <aptzero> hello all, longtime rockbox user (iriver h320 and h120)…thanks for all devs efforts…wanted to post thanks and successful ssd install results on the forums but alas they are down again. will hit the donate button - happy new year!
16.19.49 #       <__builtin> :D
16.20.12 Join    Senji [0] (~Senji@85.187.103.250)
16.20.58 Quit    Senji (Read error: Connection reset by peer)
16.21.43 Join    Senji [0] (~Senji@85.187.103.250)
16.25.08 Join    Senji_ [0] (~Senji@85.187.103.250)
16.26.03 Quit    Senji (Ping timeout: 252 seconds)
16.28.44 Join    b-f-1 [0] (~user@s5596c859.adsl.online.nl)
16.40.53 #       <dongs> hm so.
16.41.06 #       <dongs> my socket works, and reads flash ID from 512meg piece that I have
16.41.20 #       <dongs> buut, its not reading shit from sandisk one, but im not sure what timings it should be using etc.
16.43.07 Join    lebellium [0] (~chatzilla@ren77-h01-176-151-188-9.dsl.sta.abo.bbox.fr)
16.48.54 #       <dongs> my socket only does x8 nand tho, so if that snadisk thing only works in x16 the nit wont work either
16.52.39 #       <funman> http://ams.com/eng/content/download/125308/723179/file/AS3543_Datasheet_EN_v2.pdf
16.54.08 Quit    sparetire (Ping timeout: 256 seconds)
16.54.49 #       <funman> Mihail: you wanted the 3531 too?
16.56.10 Quit    edhelas (Ping timeout: 268 seconds)
16.56.46 #       <Mihail> yes
16.57.21 Join    edhelas [0] (~edhelas@145.133.43.230)
16.57.24 #       <Mihail> and 3534 if you have
16.57.58 #       <dongs> hm yeah so.. Mihail i can read "normal" nand ID, can't read sandisk, but donno about corect timings. if I cahnge timings, i get shit like FF/70/F0/20/ etc as IDs at random, so maybe something is happening but not sure. meh.
16.58.08 #       <dongs> 1am, not gonna spend more time on it tho. will do next week sometime
16.59.16 #       <funman> ah 34 not 43
16.59.26 #       <funman> Mihail: mihail.z.....@gmail.com ?
17.01.00 #       <Mihail> yes
17.01.38 Quit    edhelas (Ping timeout: 248 seconds)
17.02.17 #       <funman> Mihail: pamaury: sending 3531
17.02.47 #       <dongs> what is it, SoC?
17.03.33 #       <dongs> oo
17.03.37 #       <dongs> thats more relevant to clip+/v2
17.06.12 #       <pamaury> funman: thanks
17.06.23 Quit    skapazzo (Quit: Lost terminal)
17.06.37 #       <dongs> pamaury: now read SD controller part and see what it says about nand :)
17.06.50 #       <funman> can't find 3534 in my mailbox, i might have downloaded it from ams.com a while ago, need to look in old laptops
17.06.58 #       <dongs> well, unless that bit was custom-added by sandisk
17.07.20 #       <funman> dongs: what are you looking at?
17.07.23 Join    johnb3 [0] (~johnb3@p57B45981.dip0.t-ipconnect.de)
17.07.33 #       <funman> clips don't have a nand controller
17.07.46 #       <dongs> well, they sure don't, but why is the flash IC hooked up like its nand
17.07.51 #       <funman> iiuc sandisk replaces them with SD since they don't have to pay SD patents
17.08.04 #       <dongs> http://i.imgur.com/wh8KbTN.jpg how does this work then
17.08.29 #       <dongs> if it was SD interface I dont see why they'd need all those pins, in same places wehre you'd find them on regular nand.
17.09.01 #       <funman> isn't there a SD controller between the nand and the cpu ?
17.09.05 #       <dongs> no
17.09.11 #       <pamaury> funman: is the AS3531 the closest to amsv2 ?
17.09.22 #       <funman> hmm
17.09.35 #       <funman> iirc it's still very like as3525
17.09.39 #       <funman> so like amsv1
17.10.37 #       * funman git clones
17.11.00 #       <pamaury> dongs thinks there could be a sd to nand converter in amsv2 since the flash part seems to be a raw nand
17.11.07 #       <dongs> yeha
17.11.20 #       <funman> yes that's what i would think
17.11.30 #       <dongs> it doenst make sense to route all that shit if it doesnt actually use all the signals
17.11.50 #       <funman> dongs: you could try removing solder points and see if it still works?
17.11.57 #       <dongs> like?
17.12.35 #       <funman> if you think some unneeded things are connected try unsoldering them and see if internal flash still works? sorry i am not sure what you want to do exactly
17.12.50 #       <dongs> well, i have (many) dead clip+'s with dead flash on them
17.13.00 #       <dongs> i'd like to replace with standard 4/8gib nand if that makes it work.
17.13.07 #       <funman> oh
17.13.12 #       <funman> good idea
17.13.21 #       <dongs> i got one replaced with a 512meg part (thats all I could find on short notice), and it doenst work (obivosuly). i got it booting over jtag into bootloader + usb mode, it comes up as 1.3tb usb device
17.13.25 #       <dongs> so clearly not working
17.13.35 #       <dongs> i will get some 4/8gb parts sometime in coming weeks and try that as well
17.13.46 Quit    sLite (Remote host closed the connection)
17.13.47 #       <pamaury> one thing which we don't know for sure though is that the sd to nand controller may need some bootstrapping to work with some nand, either by preformating the raw nand or using a magic command
17.14.03 #       <funman> rockbox usb mode right?
17.14.04 #       <dongs> while waiting i will probably hookup a almost/nearly dying one and check the nand-specific signals to see if theyt're toggling while the flash is being accesses
17.14.12 #       <dongs> funman: well, bootloader USB mode
17.14.27 #       <funman> there is some custom SD commands to get the flash size
17.14.33 #       <funman> bank switching
17.14.49 #       <funman> maybe those could cause some weird size to be reported
17.15.47 Join    sLite [0] (~quassel@mail.slite.org)
17.16.00 #       <pamaury> did you find it by reverse engineering the OF ?
17.16.22 #       <dongs> i would imagine this kinda stuff is either in ROM or in bootloader
17.16.28 #       <dongs> early on, shouldn't have any business in firmwarwe
17.16.33 #       <funman> pamaury: bank switching yes, it's proprietary commands
17.16.42 #       <funman> https://github.com/Rockbox/rockbox/blob/master/firmware/export/as3525v2.h seems to agree that amsv2 is still the old as3525
17.16.45 #       <johnb3> I have a dead/bricked clip+. sudo fdisk -l   reports it as for 4MB when connected to USB. Does it even make any sense to try the unbrick approach by shorting those two pins and dd'ing the firmware or is the flash completely broken? I had bought it as defective from *bay...
17.16.54 #       <funman> plus some custom devices and upgraded audio / pmu
17.17.11 #       <funman> johnb3: nothing to lose i guess
17.17.50 #       <funman> hm maybe amsv2 doesn't do bank switching stuff though
17.18.06 #       <pamaury> amsv2 has a different sd controller from amsv1 I think
17.18.10 #       <dongs> johnb3: mine c omes up as 32meg usb whether those pins are shorted or not
17.18.29 #       <pamaury> and the sd-as3525v2.c driver doesn't do bank switching
17.19.57 Join    edhelas [0] (~edhelas@145.133.43.230)
17.20.02 #       <funman> ah yep
17.20.35 #       <funman> capacity is given by csd
17.20.38 #       <pamaury> I could try to have a look at clip+ ROM, see if it does anything fancy with SD, but it seems a bit unlikely that it would have a magic SD command to somehow reformat
17.20.43 #       <johnb3> dongs: I have a second one that comes up as 32MB too. The reason why I ask is that https://www.rockbox.org/wiki/SansaAMSUnbrick says if AFTER shorting the pins it has 4MB, the nand is dead.
17.21.08 #       <dongs> johnb3: hm. its still 32 with new "512M" nand that I soldered on there
17.22.44 #       <dongs> anywa,y writes to it fail/readback is zero
17.22.47 #       <dongs> so thats obivously not working
17.23.17 #       <dongs> oh right rom jumped straight to 0x800000D1C and i gave up trying to analyze it
17.23.24 #       <dongs> pamaury: where did y ou load the rom at, 0x80000000?
17.24.00 Join    skapazzo [0] (~skapazzo@151.9.205.1)
17.24.40 #       <pamaury> dongs: yes
17.25.02 #       <pamaury> but if you are going to REing it, I can send you my IDA file, which is based on funman's work
17.25.04 #       <johnb3> As a side note, out of 10 I bought 4 have a dead screen, but could be recovered (installing a RB bootloader) otherwise.
17.25.29 #       <johnb3> SO now I make use of the voice / talk feature ;-)
17.25.34 #       <pamaury> at some point I tried to understand the usb protocol of the ROM but gave up
17.26.41 #       <johnb3> so it's not always the nand that kills it for people.
17.27.07 #       <pamaury> dongs: one interesting thing though, is that iirc the ROM implements the SCSI FORMAT_UNIT command, so if you can reach the ROM usb protocol, you could try that see if that helps, on my side I can look at how it's implemented
17.27.59 #       <dongs> pamaury: remember ROM doens't do much here. when I try to run rockbox bootloader, i connect under reset, set that memory controller to remap ram @ 0 and then jump directly to it
17.28.03 #       <dongs> it never loads any rom code.
17.28.57 #       <dongs> 0xC80C03FC etc are peripehrals?
17.29.26 #       <pamaury> dongs: I know but nothing prevents you from running the ROM code
17.29.37 #       <dongs> right.
17.29.41 #       <dongs> it just dies shortly after boot.
17.29.43 #       <pamaury> dongs: there are plenty of peripherals
17.30.14 #       <pamaury> the SD spec has an ERASE command
17.30.21 #       <pamaury> maybe it's worth a try on the 512MB flash ?
17.34.11 Join    fujisan [0] (~fujisan@unaffiliated/fujisan)
17.34.20 #       <dongs> hm.i think ill try tapping signals on a non-dead sansa first and see if its talking like a nand or not
17.39.34 Join    parchd__ [0] (~martin@cpc19-wals10-2-0-cust100.wolv.cable.virginm.net)
17.40.53 #       <parchd__> as hoped, I got an xDuoo X3 for christmas, so whenever things get so far I'm more than happy to help with testing of an official rockbox build
17.42.08 #       <parchd__> pamaury: I believe you're doing the work on that chipset - I'll probably be hanging about here after the holidays, but if you send a call for testers out to the list I'll see it when you get to that point
17.43.00 #       <parchd__> in the mean time, does anyone know of a reason why I shouldn't use the unofficial rockbox build that already exists?
17.43.49 #       <pamaury> parchd__: ok thanks, right now I am working on some sony players but that chip is on my soon-todo-list. You can use the unofficial one, I think some people have stability issues but I aven't followed closely
17.43.52 Quit    johnb3 (Quit: Nettalk6 - www.ntalk.de)
17.44.38 #       <parchd__> pamaury: thanks. Thats cool - I knew from hanging around here in the last couple of weeks that you were focussing on the sony players at the moment
17.46.53 #       <funman> dongs: 3FC sounds like gpio
17.47.24 #       <funman> #define GPIOB_BASE           0xC80C0000
17.49.14 #       <dongs> pamaury: how useful is the ida one, does it have peripherals segments and stuff mapped as structs etc
17.49.28 Join    sparetire [0] (~sparetire@unaffiliated/sparetire)
17.49.33 #       <pamaury> dongs: yes, I mean some of it at least
17.54.07 Join    Senji [0] (~Senji@85.187.103.250)
17.54.14 #       <dongs> will take a look later. too many things to do at once :)
17.55.59 Quit    Senji_ (Ping timeout: 268 seconds)
17.57.11 ***     Saving seen data "./dancer.seen"
18.34.58 Quit    parchd__ (Quit: Lost terminal)
19.40.12 Quit    edhelas (Ping timeout: 268 seconds)
19.42.56 Join    diox [0] (~u@c80-216-201-69.bredband.comhem.se)
19.45.42 Join    larsd [0] (5491a09e@gateway/web/freenode/ip.84.145.160.158)
19.47.44 #       <larsd> Good evening, can someone tell me how I can change the button-combination used for the dual-boot in the source? I got a XDuoo X3 but the people that ported the device apparently set the dual-boot on power + lock, which is very bad, as it completely makes the lock button useles... :P
19.48.34 Quit    diox (Read error: Connection reset by peer)
19.49.10 #       <pamaury> larsd: the current Xduoo X3 port is unofficial so I can't tell you
19.52.18 #       <larsd> pamaury, hm... it's not about Xduoo in particular I'd say... but I suppose that it should be possible to set the button-combination somewhere in the source code no? Before, I used a Sansa Fuze and it worked fine, when something broke I had to remap some buttons... That's why I am supposing I should be able to change it somehow...
19.53.12 #       <larsd> Though I'm not sure how the booting of rockbox works... so yeah, I have no idea myself :P
19.53.12 #       <pamaury> larsd: dualboot is very device specific
19.53.21 #       <larsd> Ah, I see
19.53.34 #       <pamaury> I can try to have a quick look at how the port is done, wait a minute
19.53.36 #       <__builtin> look for the bootloader source somewhere
19.53.56 Join    diox [0] (~u@c80-216-201-69.bredband.comhem.se)
19.53.57 #       <larsd> it's on github...
19.54.20 #       <larsd> https://github.com/xvortex/rockbox
19.55.56 #       <larsd> I was randomly looking at the firmware files of mips/jz47xx but seems like I haven't found what actually plays a role in booting...
19.57.08 #       * __builtin can't finds bootloader/xduoox3.c
19.57.13 ***     Saving seen data "./dancer.seen"
19.57.37 #       <pamaury> dualboot does not seem to be done in bootloaders/xduoox3c.c
19.57.55 #       <__builtin> that's the problem though
19.58.37 #       <__builtin> out of curiosity, has anyone contacted this "Vortex" about merging their work into master?
19.59.29 #       <pamaury> yes
19.59.51 #       <__builtin> what was the result?
20.01.32 #       <pamaury> basically he doesn't want to maintain the code and I won't merge it as is because there is a bunch of copy paste from random ingenic code that is both super ugly and of dubious licence
20.04.30 #       <pamaury> I think dualboot patching is done in the update-to-rockbox.zip but I can't download it
20.05.25 #       <__builtin> odd
20.05.55 #       <larsd> ah hm... indeed, for now, I used their "easy" install method... didn't try to compile the stuff myself, nor bootloader
20.06.33 #       <__builtin> larsd: do you have that file?
20.06.50 #       <larsd> though there is a rockbox.bin generated in my built of their git...
20.06.56 #       <larsd> yes, I have...
20.07.44 #       <__builtin> wait a second
20.09.05 #       <pamaury> I didn't study how the xduoo x3 boot process works but the obvious solution is to dualboot in uboot
20.09.17 #       <pamaury> (since the OF is linux based)
20.10.14 #       * __builtin is downloading the other file from mega now
20.10.37 #       <__builtin> but it seems to have negative progress: 6% to 5% ?!
20.11.40 #       <larsd> I can also upload it somehwere...
20.12.35 #       <__builtin> let me see if this works first
20.13.13 #       <larsd> ok
20.14.41 #       <larsd> well, in case it doesn't work https://wolke.sumpi.org/s/QeOZFqM1ZVQYfAl
20.17.48 #       <__builtin> darn, all binaries and no source
20.18.53 #       <pamaury> one of the other reason I don't like it, there is doc about how he did things
20.18.59 #       <pamaury> *no doc
20.19.02 #       <larsd> Maybe I should ask for their kernel source and config?
20.19.36 #       <__builtin> and winblows binaries, too :(
20.19.55 #       <pamaury> well I sent them an email without luck. Vortex (who did the port) said he managed to contact xduoo engineers
20.20.52 #       <__builtin> so yeah, larsd, it seems unlikely that you'll be able to modify that behavior at the moment
20.21.06 #       <pamaury> try to contact him directly
20.21.16 #       <larsd> I see, well, seems a bit intransparent then... as Rockbox works to me, I can live with it, just thought it would be sufficiently quick and easy...
20.21.47 #       <larsd> Thank you for your help though :) and for developing and maintaining Rockbox :)
20.28.10 #       <fs-bluebot_> Build Server message: 3New build round started. Revision 985f6e6, 255 builds, 13 clients.
20.33.42 Quit    diox (Read error: Connection reset by peer)
20.39.04 Join    diox [0] (~u@c80-216-201-69.bredband.comhem.se)
20.40.37 #       <fs-bluebot_> Build Server message: 3Build round completed after 748 seconds.
20.40.38 #       <fs-bluebot_> Build Server message: 3Revision 985f6e6 result: All green
21.00.26 #       <fs-bluebot_> Build Server message: 3New build round started. Revision 6e5f287, 255 builds, 12 clients.
21.00.41 #       <__builtin> this should fix a little bug with puzzles rendering
21.00.51 #       <__builtin> if it doesn't break anything...
21.01.23 Quit    fujisan (Quit: Textual IRC Client: www.textualapp.com)
21.03.43 #       * __builtin isn't sure if he should keep all of the files that aren't specific to rockbox around in the source directory
21.07.47 Join    idonob_ [0] (~Owner@static-173-212-139-201.ptr.terago.net)
21.10.48 #       <__builtin> I mean, they don't do anything...
21.14.29 #       <fs-bluebot_> Build Server message: 3Build round completed after 844 seconds.
21.14.30 #       <fs-bluebot_> Build Server message: 3Revision 6e5f287 result: All green
21.14.48 #       <__builtin> wow the build cluster has been slow lately
21.23.38 #       <pamaury> well apparently I lost a build client
21.25.07 #       <pamaury> also petur's client disappeared
21.32.18 #       <pamaury> is it me or gerrit is super slow
21.32.47 #       <__builtin> not just you
21.32.54 #       <__builtin> (though everything's slow for me)
21.34.01 #       <__builtin> but yeah, it seems to be slower than normal
21.43.23 Join    [Saint] [0] (~sinner@rockbox/staff/saint)
21.57.17 ***     Saving seen data "./dancer.seen"
21.58.07 Join    edhelas [0] (~edhelas@145.133.43.230)
22.03.39 Quit    michaelni (Ping timeout: 246 seconds)
22.07.34 Quit    edhelas (Ping timeout: 268 seconds)
22.16.21 Join    michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at)
22.29.09 Join    tracktheripper [0] (4d61f5e5@gateway/web/freenode/ip.77.97.245.229)
22.31.53 #       <lebellium> pamaury: still busy?
22.33.27 Join    edhelas [0] (~edhelas@145.133.43.230)
22.37.45 #       <pamaury> lebellium: yes and no, depends for what ;) also soon to bed
22.40.20 #       <lebellium> if you have some things to try out on NWZ-A15 (like changing the region code/sound pressure or such)
22.40.36 #       <lebellium> I'm still on holidays tomorrow and the day after so I'll have some time
22.45.15 #       <pamaury> someone successfully changed the sound pressure of a NW-A25
22.46.45 #       <lebellium> was on the IRC? Didn't read that
22.55.03 Quit    idonob_ (Ping timeout: 268 seconds)
22.55.04 #       <pamaury> no he sent me an email
22.55.30 Quit    n3m9 (Read error: Connection reset by peer)
23.05.32 #       <lebellium> well it seems that there is no volume cap anymore on "recent" walkman
23.05.34 #       <lebellium> http://www.sony-europe.com/support/emanual/NWZ-E583/HG/EN/contents/TP0000067716.html
23.05.44 #       <lebellium> it's just a warning
23.06.36 Part    TorC
23.07.05 #       <pamaury> I don't know, to be honest I don't really care
23.07.36 #       <pamaury> My tool allows one to change the setting associated with it, what people do with that is not my problem ;)
23.11.52 Join    idonob_ [0] (~Owner@static-173-212-139-201.ptr.terago.net)
23.30.33 Quit    larsd (Ping timeout: 260 seconds)
23.36.22 Join    TorC [0] (~TorC@fsf/member/TorC)
23.41.56 Join    Jinx [0] (Dojo@unaffiliated/jinx)
23.57.18 ***     Saving seen data "./dancer.seen"