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

00.17.41 Nick    Bray90820_ is now known as bray90820 (~bray90820@173-25-204-30.client.mchsi.com)
00.25.05 Quit    lebellium (Quit: ChatZilla 0.9.93 [Firefox 50.1.0/20161208153507])
00.43.11 Quit    paulk-collins (Quit: Leaving)
00.55.27 Quit    edhelas (Ping timeout: 245 seconds)
01.00.49 Quit    skapazzo (Quit: Lost terminal)
01.17.03 Quit    alexweissman (Remote host closed the connection)
01.56.27 ***     Saving seen data "./dancer.seen"
02.07.07 Quit    atsampson (Ping timeout: 245 seconds)
02.15.15 Quit    smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/)
02.19.18 Join    atsampson [0] (~ats@cartman.offog.org)
02.25.38 Quit    ender (Quit: BOFH excuse #53: Little hamster in running wheel had coronary; waiting for replacement to be Fedexed from Wyoming)
02.29.24 #       <dongs> hm he left already.
02.36.25 #       <dongs> but if "nand" on sansas was some custom thing converting to SD why the shit would they have just as many connections as a normal nand flash 
02.36.51 #       <dongs> hm i think ill xray the 4gb deadnand i took out to see if its just the flash die or if there's a controller stacked / near it
02.37.19 #       <dongs> .. if i find where i tossed it
02.37.56 Quit    ZincAlloy (Quit: Leaving.)
03.09.00 Join    Saratoga [0] (47e27552@gateway/web/freenode/ip.71.226.117.82)
03.09.33 #       <Saratoga> dongs: I am mostly guessing, it's possible it is normal nand and the SD logic is on die with the as3525
03.09.55 #       <Saratoga> If so that would make fixing players much easier 
03.11.44 Quit    kleinerbasti (Ping timeout: 260 seconds)
03.15.25 #       <dongs> Saratoga: thats what I THOUGHT it was
03.15.32 #       <dongs> until someone said it was on-flash chip
03.15.35 #       <dongs> anyway, took xrays uh...
03.16.39 #       <dongs> http://i.imgur.com/eCKebg9.jpg thats not what last  flash I looked at looked like
03.24.08 #       <dongs> didnt expect so much metal that it covers everything
03.24.53 #       <dongs> and honestly i expected teh shit to be wirebonded not wahtever the hell this is
03.26.23 Join    rela_ [0] (~x@p200300764D68AA00A0B011247A05BFD0.dip0.t-ipconnect.de)
03.29.56 Quit    rela (Ping timeout: 260 seconds)
03.56.31 ***     Saving seen data "./dancer.seen"
04.30.20 #       <Saratoga> Wiki says the pin out is onfi although I don't know how that was determined
04.38.53 #       <dongs> < dongs> http://i.imgur.com/wh8KbTN.jpg i mapped out the flash chip, it does sorta look like x16 nand with a couple exceptions...
04.45.16 #       <Saratoga> Sorry, missed that, should put it on the wiki
04.46.00 #       <Saratoga> How did you map that?
04.46.46 #       <dongs> looked at onfi pinout, saw that most of those pins are connected same way, vcc/gnd parts are obvious etc
04.47.01 #       <dongs> what i'm saying is that pinout *does* look like standard nand, with a couple exceptions i marked on there
04.47.39 #       <dongs> like it has CE2 conencted (pin8) but that one is not used in X16 mode
04.47.43 #       <dongs> the only thing I can think of is that
04.47.51 #       <dongs> liek 1gb (do those exist?) clips used x8 nand mode
04.48.01 #       <dongs> and then something larger like 8gb would use x16
04.48.02 #       <dongs> or something
04.48.12 #       <dongs> or maybe they just made it compatible with either one
04.48.37 #       <dongs> but 34/35 which are NC officially connecting is weird...
04.49.18 #       <dongs> and now looking at that die xray, that pin36 actualyl is connected to gnd which spreads across the entire chip, which would be gnd on x8 but NC on x16.
04.49.29 #       <dongs> but the die pic shows it wired up as x16, at least all the pins are there
04.50.46 #       <Saratoga> Not sure if this matters but I believe the nand is accessed as N banks of 2GB each 
04.51.11 #       <Saratoga> Or maybe 1 GB, been forever
04.51.30 #       <dongs> Saratoga: do you know as32wahtever boot sequence? if I wanted to boot it over jtag, by loading some code, is there steps to go through first? the jtagunbrick shit says loading into 0x0, but thats mapped to ROM when I power my stuff up
04.52.00 #       <dongs> if I jump to 0x0 and start executing from tehre, it runs, then gets stuck in a endless loop somewehre in 0x80004xxx or someshit
04.55.04 #       <dongs> donno if internal memory needs to be setup first and bla bla
05.05.25 #       <Saratoga> Iirc it starts executing ROM, sets up the nand and dram, and then loads the nand start into ram 
05.06.02 #       <Saratoga> The data sheet describes how to boot from various things, but evidently the Sandisk ROM is different then built in 
05.06.34 Quit    atsampson (Ping timeout: 258 seconds)
05.06.47 #       <Saratoga> Funman might remember more I never played with it much 
05.08.27 #       <Saratoga> A few people have looked at the ROM but I'm not sure it's ever been fully worked out 
05.09.18 #       <Saratoga> Possibly if it's already booted the memory map is setup wrong 
05.09.26 #       <Saratoga> I forget if we remap it
05.09.27 #       <dongs> right, i think what i need to do is skip the nand stuff, just do initial boot to bring up PLL/etc, setup ram/whatnot if needed, load what would have been loaded from nand into ram and jump there
05.10.01 #       <dongs> is v2 (clip+) AMS chip much different from the one that the datasheet exists for?
05.10.08 #       <dongs> i.e. completely different memory map etc
05.10.19 #       <Saratoga> Can you put a breakpoint in the mkamsboot preboot loader?
05.10.28 #       <dongs> v1 datshet talks about  extenral sdram and shit (I guess it could be stacked die)
05.10.37 #       <dongs> my jtagged clip has dead nandflash
05.10.51 #       <dongs> so I can only boot to rom or to code I put into ram, wherever that is
05.10.57 #       <Saratoga> It does have a different memory map ( more iram and different hardware)
05.11.12 #       <dongs> and datasheet to that isnt linked? i only found v1 thats hosted by keil or wahtever
05.11.25 #       <dongs> http://www.keil.com/dd/docs/datashts/ams/as3525_ds.pdf < this
05.11.27 #       <Saratoga> They all have dram, either external or stacked die 
05.12.14 #       <Saratoga> There's no data sheet for v2, it's a mix of the as3525 and as3531 and some random Sandisk stuff
05.12.26 #       <dongs> fuckin great
05.12.58 #       <dongs> ah, 3531 looks more like the v2 chip
05.13.03 #       <Saratoga> People have unbricked a v1 device over JTAG many years ago
05.13.12 Join    atsampson [0] (~ats@cartman.offog.org)
05.13.28 #       <Saratoga> But it was after a bad flash, and on the m200v4 I think
05.16.25 #       <dongs> yeah , my flash is deader than BSD, so just reflashing it isnt gonna help. i scrapped around a random 4gbit nand i had laying around and soldered it on, in 'recovery' usb mode it does show up as 32meg disk but writing to it and reading back brings back zeros so its clearly not w orking
05.17.08 #       <dongs> i guess its quite likely rom only supports setting up just a dozen chips that sandisk would use or something
05.17.11 #       <dongs> assuming it even gets tehre
05.17.37 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
05.19.47 #       <Saratoga> Mkamsboot source says that on v1 iram is mapped at 0x0 while v2 maps dram there 
05.19.59 Join    treaki__ [0] (~treaki@p3E991662.dip0.t-ipconnect.de)
05.20.16 #       <dongs> well theres definitely something there when i attach
05.20.19 #       <dongs> even right after reest
05.20.26 #       <dongs> it just looks like standard arm vector table
05.20.36 #       <dongs> cant be ram right awayt
05.20.50 #       <dongs> maybe ROM that executes some junk and later becomes RAM after initialization/remapping
05.20.52 #       <Saratoga> ROM ?
05.20.54 #       <dongs> yerah
05.21.03 #       <dongs> if i try changing 1st vector it doesnt take
05.21.09 #       <dongs> so, i mean, cant write to it
05.22.09 Quit    alexweissman (Ping timeout: 252 seconds)
05.23.01 #       <Saratoga> Iiuc the default ROM (which is not quite what Sandisk is using ) should poll various hardware devices to figure out what to do
05.23.22 #       <dongs> does 512k iram always exist at same addres ssomewehre?
05.23.23 Quit    treaki_ (Ping timeout: 245 seconds)
05.23.24 #       <dongs> before sdram is brought up
05.23.29 #       <Saratoga> So maybe if the nand doesn't respond it never sets up the ram
05.23.33 #       <dongs> right
05.23.53 #       <Saratoga> 320 KB on v1, 1MB on v2
05.24.08 #       <dongs> at which address tho?
05.24.09 #       <dongs> remappable?
05.24.21 #       <Saratoga> It's embedded DRAm of some kind, ams licensed it from tsmc 
05.24.37 #       <dongs> right, sram or whatever
05.24.51 #       <Saratoga> It's slower, but yeah 
05.25.03 #       <Saratoga> Everything is remappable 
05.25.17 #       <dongs> how much of sdram tho?
05.25.20 #       <Saratoga> We don't use virtual memory, but there is an MMU
05.25.43 #       <dongs> 3531 datasheet says 512k sram
05.25.56 #       <Saratoga> 2 or 8 MB depending on device, but sdram controller must be configured first 
05.26.14 #       <Saratoga> It's double that on the Sandisk hardware
05.26.30 #       <dongs> i guess i can just keep writing rnadom values at every few megs into addres sspace until i hit where the ram is
05.26.33 #       <Saratoga> It's not quite the same as either data sheet
05.27.06 #       <dongs> does rockbox bootloader expect hardware to be already setup by OF boot?
05.27.08 #       <Saratoga> Doesnt the data sheet specify the initial memory map? Probably that didn't change much
05.27.11 #       <dongs> or can it do all the bringup itself
05.27.25 #       <dongs> the v1 datasheet has, but its fucked up, ram wasnt working at that address either
05.27.52 #       <Saratoga> Some stuff is setup already, but most things are reset by rockbox anyways
05.29.13 #       <Saratoga> I'm not sure anyone has figured out what exactly the ROM does
05.30.36 #       <dongs> well i could dump/step/disassemble/decompile it but without memory map or at least most periphral addreses map it would be annoying as shit
05.31.03 #       <dongs> could probly look through what rockbox has figured out for peripherals like gpio/whatever else it touches
05.33.22 #       <Saratoga> I think what you could do is setup the dram, load rockbox into ram, and then boot into it, but even then you'd be reset when you powered off 
05.34.07 #       <Saratoga> Unless you replaced the nand 
05.34.35 #       <dongs> right, but if that does work, and rockbox can format the internal nand (the 4gbit replacement), then things could go from there
05.35.17 #       <dongs> but anyway if ROM is only looking for a handful flash device IDs and doens't setup anythign that's not in that list then its fucked anyway as it will never boot from anything else
05.35.55 #       <Saratoga> I think if you got a new nand working, you could do the ams unbrick trick to rewrite it
05.36.25 #       <dongs> which was what? booting in recovery mode and copying some .bin file over?
05.36.37 #       <Saratoga> Yeah that could be a problem if it only works with a few chips
05.36.39 #       <dongs> i did that, but readback was zeros
05.36.47 #       <dongs> so clearly nothign was going into it
05.37.03 #       <Saratoga> If it's working you get a whole bank of memory, 1 GB I think
05.37.10 #       <dongs> oh, really?
05.37.24 #       <dongs> well, 4gib would be 512megs but yeah
05.37.25 #       <Saratoga> If nothing is working you get 32 or 4 MB on AMSv2 
05.37.26 #       <dongs> i dont have anything bigger
05.37.33 #       <dongs> yes, i get 32.
05.37.59 #       <Saratoga> On v1 I think 32 (or 16?) Means it worked 
05.38.13 #       <dongs> i guess I could grab 32gbit nand somewehre and resolder it again
05.39.18 #       <dongs> would probly fuckup my carefully planted jtag connection
05.39.30 #       <dongs> http://i.imgur.com/51tHgIW.jpg < this
05.40.57 #       <Saratoga> Nice 
05.46.28 #       <dongs> i really dont know. the flash pinout confuses me greatly
05.46.49 #       <dongs> if it was some custom thing with SDIO controller on it, it wouldn't need all those pins.
05.47.06 #       <dongs> technically in 1 bit sdio you only need 3 wires
05.47.14 #       <dongs> clk, cmd, and d0
05.48.02 #       <dongs> i suppose they could have trolled everyone and put that interface into pins 34/35/38/39 or something
05.48.07 #       <dongs> on those NC pins on the nand pinout
05.48.23 #       <dongs> but i think thats pretty farfetched
05.48.38 #       <dongs> but then why bother routing/connecting the rest of nand pinout
05.50.42 #       <fIorz> sourcing flexibility somehow?
05.50.48 #       <fIorz> but does sound wild indeed :-)
05.50.59 #       <Saratoga> It's used in a lot of different devices (see Google), maybe it has multiple modes?
05.51.17 #       <dongs> what is, the AMS chip? or that shitdisk weirdnand
05.51.39 #       <Saratoga> Alternatively it could be normal nand, but why put an SD controller in hardware if the CPU has a nand controller anyway
05.52.03 #       <Saratoga> The nand chips is 
05.52.04 #       <dongs> maybe they had some IP left over from making sdcards
05.52.23 #       <Saratoga> They use it in USB sticks 
05.52.38 #       <dongs> then its gotta be just normal nand, eh?
05.52.55 #       <dongs> maybe i should find my socket and try actualyl reading the sandisk part
05.53.07 #       <dongs> at least to get chip ID or something, then it would be obvious its not some SD-controller based weird thing
05.55.30 #       <dongs> but if that part is in usb sticks as you say... even less reasons for it to be internally SD-based..
05.56.33 ***     Saving seen data "./dancer.seen"
05.58.01 #       <Saratoga> Maybe they put the flash translation layer on the package and expose it to the USB bridge?
06.05.55 #       <dongs> typical garbagecheap USB sticks are either nand or emmc, with single chip controller
06.06.34 #       <dongs> dont see why they would complicate it any more by adding extra shit
06.22.49 #       <dongs> Flash ID code:      45C79432 - SanDisk SDTNNMAHSM-004G - 4CE/Single Channel [MLC-8K] -
06.22.52 #       <dongs> accroding to google
06.22.56 #       <dongs> its standard nand.. hmm
06.23.24 #       <dongs> i guess i gotta figure out how to get dram setup and load rockbox there.
06.33.26 #       <Saratoga> So the SD logic is entirely on the ams chip?
06.36.38 #       <dongs> yes
06.37.08 #       <dongs> i dont know why EXTRA lines are connected on the nand side, but if you ignore those the chip IS accessible as standard x16 nand, at least electrically
06.49.09 Join    hcs [0] (~agashlin@rockbox/contributor/hcs)
06.53.48 Quit    TheSeven (Ping timeout: 245 seconds)
06.54.21 Join    TheSeven [0] (~quassel@rockbox/developer/TheSeven)
07.04.46 Quit    rela_ (Quit: Leaving)
07.05.52 #       <freesoftware> how's it goin?
07.06.18 #       <freesoftware> i guess sandisk made that nand so it could be used in literally whatever
07.16.29 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
07.47.33 Quit    alexweissman (Remote host closed the connection)
07.56.37 ***     Saving seen data "./dancer.seen"
08.00.52 Quit    naleo (Read error: Connection reset by peer)
08.46.37 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
08.51.00 Quit    PurlingNayuki (Ping timeout: 260 seconds)
08.58.07 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
09.02.31 Quit    alexweissman (Ping timeout: 252 seconds)
09.22.37 Join    rela [0] (~x@pdpc/supporter/active/rela)
09.56.41 ***     Saving seen data "./dancer.seen"
09.58.33 Join    JanC_ [0] (~janc@lugwv/member/JanC)
09.59.48 Quit    JanC (Killed (rajaniemi.freenode.net (Nickname regained by services)))
09.59.49 Nick    JanC_ is now known as JanC (~janc@lugwv/member/JanC)
10.01.06 Join    rela_ [0] (~x@p200300764D68AA00A0B011247A05BFD0.dip0.t-ipconnect.de)
10.04.16 Quit    rela (Ping timeout: 260 seconds)
10.06.08 Quit    hcs (Quit: Yaaic - yikez!)
10.09.51 #       <dongs> cool
10.10.00 #       <dongs> i can get soem 8gb nand for around $6 or so next year
10.10.20 #       <dongs> but i gotta get this shit booting first
10.10.37 #       <dongs> is github rockbox mirror current?
10.11.05 #       <dongs> hm last commit 2014..
10.11.05 #       <dongs> nope
10.14.25 Join    lebellium [0] (~chatzilla@ren77-h01-176-151-188-9.dsl.sta.abo.bbox.fr)
10.19.45 Quit    krnlyng (Ping timeout: 258 seconds)
10.33.02 Join    krnlyng [0] (~liar@77.116.98.38.wireless.dyn.drei.com)
10.36.13 Join    pamaury [0] (~pamaury@rockbox/developer/pamaury)
10.49.24 Join    ender` [0] (krneki@foo.eternallybored.org)
10.55.27 #       <dongs> where are IDE files for rokcbox firmware?
10.55.36 #       <dongs> so i can crossreferenc code/variables/etc
10.58.07 #       <pamaury> we don't use any IDE
10.59.21 #       <dongs> so how do you uh.. navigate the souirce/
10.59.51 #       <dongs> pamaury: did you see my current blogging about deadsansa and figuring out if I can swap a generic nand flash into its place
11.00.05 #       <pamaury> you use headers
11.00.50 #       <pamaury> dongs: I read the logs quickly but I don't know much about sansas
11.00.57 #       <dongs> ah okay.
11.01.07 #       <pamaury> afaik, sansas use an sd+nand chip
11.01.22 #       <dongs> well, i spent last 24 hours checking that its most likely not the case.
11.01.47 #       <dongs> if there's a nand->sd translation layer, its in the SoC and not on the flash chip.
11.02.10 #       <pamaury> really? odd
11.02.27 #       <dongs> same chips are also in USB flash drives
11.02.33 Join    Strife89 [0] (~quassel@adsl-98-80-190-150.mcn.bellsouth.net)
11.02.48 #       <dongs> and people have loaded htem into standard nand flash dumping devices and they have chip ID and everything liek stanard nand.
11.03.05 #       <dongs> and the fact that pinout for it mostly matches (minus extra signasl on pins that should be NC), etc.
11.03.34 #       <dongs> now its MAYBE possible that they put a 1bit SDIO interface on those NC pins, but that would be pretty unlikley as well as pointless, since they already routed and hooked up all of nand x16 connections as wel.
11.04.11 #       <pamaury> then I guess you can try to swap it with a generic nand and see what happens, the small problem is that you have to make sure the sd->nand layer will recognize it
11.04.29 #       <pamaury> it may be using nand ids, or some semi-standard commands to get flash info
11.04.38 #       <dongs> right. thats where i'm at now. its swapped with a 512meg part, its not doing (much), so I need to load some stuff up that maybe at least pokes SD and try to see if it works or not
11.04.49 Quit    Strife1989 (Ping timeout: 264 seconds)
11.04.59 #       <dongs> and I'll get a 4gb and 8gb chip sometime next month to try with as well
11.05.23 #       <dongs> got jtag connected and I can reset/halt/step the core, but nto finding much info on the memory map and stuff on the clip+
11.05.31 #       <pamaury> Isn't there a jtag and/or a special usb mode where you upload a file and it runs?
11.05.39 #       <dongs> jtag works fine
11.05.54 #       <dongs> USB shows up as 31meg thing but reading back doesnt work = zeros, so its probly not getting written.
11.06.19 #       <dongs> if I knew memory map i could at least load hello world into it that does some stuff and poke sd controlelr registers etc
11.06.26 #       <dongs> to see if I can get some info of the new "512meg" flash.
11.06.48 #       <pamaury> the memory layout should be partly documented in target/arm/as3525/app.lds and also in the as3525 datasheet (which partly applies to amsv2)
11.07.04 #       <dongs> ok, lds thats better. lemme look for that
11.07.07 #       <pamaury> you can google "as3525 datasheet"
11.08.33 #       <dongs> yeah when i looked at t hat, IRAM wasn't where it said it was (i have clip+).
11.08.35 #       <dongs> gonna look again
11.09.42 #       <dongs> ah i havent tried at c100000. time to hook it up again and check
11.09.45 #       <pamaury> also look at as3525.h and as3525v2.h
11.10.33 #       <pamaury> in rockbox we use the mmu to remap the iram iirc
11.10.51 #       <pamaury> there might also be some magic bits that move/remap the iram
11.11.55 #       <dongs> yeah on reset 0x0 is ROM, since i cant modify it.
11.13.20 #       <pamaury> you might want to look at as3525/memory-init.S also and I think I have a ROM dump with some analysis. It's fairly common to have a ROM disable/remap bit
11.14.49 #       <dongs> hey cool
11.14.52 #       <pamaury> if you look in system-as3525.c, there is a bit called CGU_ROM_ENABLE
11.14.55 #       <dongs> ram at c10000000 does work
11.16.04 #       <pamaury> also if you look at page 190 of the as3525 datasheet
11.16.23 #       <pamaury> you'll see that address 0 has three overlapping regions: ROM, ExtMemIF and RAM
11.16.24 #       <dongs> yea im there right now
11.16.34 #       <pamaury> depending on the Remap and IntBoolSel
11.16.43 #       <dongs> k, i can put code into c1000000, so i could probly go from there
11.17.14 #       <pamaury> ExtMemIF you be there if you boot from NAND I guess. And Remap is in CCU_MEMMAP
11.17.34 #       <pamaury> (assuming it applies to amsv2)
11.17.52 #       <pamaury> (page 116)
11.18.32 #       <pamaury> so something like
11.18.32 #       <pamaury> *(unsigned long *)0x0xC8100008 |= 2
11.19.02 #       <dongs> its 2 now
11.19.12 #       <dongs> ccu_memmap is the register that controls remap?
11.19.31 #       <pamaury> apparently
11.21.08 #       <pamaury> you mean it was already 2 or you changed it to  2 ?
11.21.21 #       <dongs> was at 2
11.23.08 Quit    rela_ (Quit: Leaving)
11.23.24 Join    rela [0] (~x@pdpc/supporter/active/rela)
11.25.01 #       <pamaury> give me a sec, I'll just have a quick look at the rom dump I have, it must remap the iram I think
11.25.38 #       <dongs> after reset, PC is at 0 and it starts tehre.
11.27.08 #       <pamaury> the very first thing the ROM does is to setup the mmu and it uses nonstandard bits
11.27.24 #       <pamaury> sorry, it disables the mmu my bad
11.28.30 #       <pamaury> actually the first thing it does is to jump at 0x80000000
11.28.50 #       <dongs> that seems to match with what im seeing
11.29.01 #       <dongs> if i let it boot, it gets stuck in endless loop around 80004xxx or so
11.29.08 #       <dongs> shortly after
11.29.22 #       <dongs> o yeah
11.29.33 #       <dongs> jumps to 80000D1C
11.29.44 #       <pamaury> try to write 1 to CCU_REMAP
11.29.51 #       <pamaury> that's what the ROM does for some reason
11.30.01 #       <dongs> to C8100008  ?
11.30.23 #       <pamaury> yeah
11.30.29 #       <dongs> its '3' now.
11.30.37 #       <dongs> and
11.30.39 #       <dongs> ram is at 0 now
11.30.51 #       <dongs> with my 0xDEADF00D still present
11.30.51 #       <pamaury> so ram is working now ?
11.30.56 #       <dongs> at 0, yes
11.31.09 #       <dongs> before it was at c1000000
11.31.20 #       <pamaury> out of curiousity, can you try to see what is at 0x81000000 ?
11.31.34 #       <dongs> alias of ram :)
11.31.52 #       <pamaury> ah yeah the datasheet it's also an alias
11.31.53 #       <dongs> same deadf00d stuff.
11.32.03 #       <pamaury> good, so you found the ram remap bit
11.32.35 #       <dongs> now can i load some bit of rockbox into that 0-ram and make it do something? :)
11.32.42 #       <dongs> some bootloader part maybe?
11.32.50 #       <pamaury> you want to load the bootloader
11.33.33 #       <pamaury> although I have to say I don't know if you can plain load the .bin file produced by the compilation or if you need to patch the OF and load the patched thing
11.33.55 #       <dongs> OF is liek 15megs tho
11.33.58 #       <dongs> which part is bootloader
11.34.12 #       <dongs> i probably have both patched and normal version
11.34.53 #       <fIorz> pamaury: thx for the hint about the FM clock, BTW, it's indeed clocked by the 32 KiHz RTC crystal, and that one was ~ 0.4 % lower than what it should be, swapped it for a non-defective part, and stations are where they belong now, and stereo sounds acceptable as well :-)
11.37.14 #       <pamaury> dongs: I don't know much about boot process, my guess is that the entire OF is flash to nand but the first N kB are the the bootloader and are loaded to RAM, and then it loads everything else. There must be some info on the wiki or in the code
11.37.27 #       <dongs> right.
11.37.32 #       <dongs> gonna poke around that for a bit
11.37.33 #       <pamaury> in rbutil/mkamsboot for example?
11.37.53 #       <pamaury> I know we use a decompressor
11.37.58 #       <pamaury> because of the size
11.38.03 #       <dongs> oh hm
11.38.19 #       <pamaury> I think we take OF bootloader + rockbox bootloader, and compress them to squeeze them in the required space
11.38.40 #       <dongs> ah theres some comments inside mkamsboot
11.39.26 #       <pamaury> if you look at mkamsboot/dualboot/dualboot.S
11.39.57 #       <pamaury> you'll see that it enables peripherals to read a key, then select either ucl compressord rb or of
11.40.03 #       <freesoftware> do you think a 128GB chip will work?
11.40.06 #       <pamaury> then decompress and run
11.40.34 #       <pamaury> so my guess is that if you compile a rockbox bootloader for your device (clip+ ?), take the resulting bootloader.bin file and upload it at 0, it should work
11.41.02 #       <pamaury> freesoftware: I'm missing some context here
11.41.14 #       <dongs> freesoftware: havent seen any that ican actualyl buy in tsop48
11.42.14 #       <freesoftware> dongs build a BGA->TSOP board
11.42.19 #       <dongs> plz.
11.43.48 #       <dongs> pamaury: doesnt rokcboxutility  pull bootloader.bin from somewehre?
11.47.32 #       <pamaury> dongs: it pulls a scrambled version yes, give me a minute
11.47.50 #       <pamaury> which device do you have ?
11.47.55 #       <dongs> clip+
11.48.03 #       <pamaury> http://download.rockbox.org/bootloader/sandisk-sansa/clipplus/bootloader-clipplus.sansa
11.48.30 #       <pamaury> this is NOT the raw binary, it has a small header (8 bytes). You need to remove the header because uploading that to the device
11.49.10 #       <dongs> hm that looks like it might actually work
11.49.17 #       <dongs> i see short jump offset to 0
11.49.19 #       <dongs> ok lets see
11.51.01 #       <dongs> hmm no, that doenst look right
11.51.09 #       <freesoftware> i hope things will be easier for me when my flash dies
11.51.13 #       <dongs> ks like it might actually work
11.51.15 #       <dongs> err
11.51.17 #       <dongs> 00000000:  00 00 EA 20        RSCCS   R10, R0
11.51.25 #       <dongs> first instruciton is this? thats wrong
11.51.31 #       <dongs> should be some kinda vector table or something at start i guess
11.51.44 #       <freesoftware> probably in like 2 years because chinese and database refreshes
11.52.34 #       <pamaury> dongs: give me a minute, I might have been wrong about the header then
11.52.58 #       <dongs> lemme load this up in real debugger and see if tehres better asm nearby
11.54.02 #       <dongs> hm nope it all looks pretty shit, wonder if header was less than 8 bytes
11.54.34 Join    paulk-collins [0] (~paulk@gagarine.paulk.fr)
11.54.49 #       <pamaury> no, the first 4 bytes are a checksum
11.55.03 #       <pamaury> the next 4 bytes are a string "cli+"
11.55.14 #       <dongs> yes
11.55.17 #       <dongs> and next 3 bytes are useless too
11.55.18 #       <pamaury> for me it looks ok
11.55.23 #       <dongs> EA 20 00 00 looks like maybe valid arm
11.55.39 #       <dongs> oh oops
11.55.39 #       <pamaury> it's a valid jump
11.56.24 #       <dongs> nice, jtag died
11.56.28 #       <dongs> so at least getting somewhere :)
11.56.28 #       <dongs> oh.
11.56.31 #       <dongs> it powered off
11.56.42 ***     Saving seen data "./dancer.seen"
11.57.16 #       <dongs> hmm
11.58.11 #       <pamaury> it is possible that the code expects some init done by the rom
11.58.34 #       <dongs> time to try gain
11.58.35 #       <dongs> right
12.01.06 #       <dongs> hmm no
12.01.07 #       <dongs> damn
12.01.12 #       <dongs> 1st jump goes to crap code
12.02.45 #       <dongs> pamaury: 1st code jumps to 0x4001c, yeah
12.02.47 #       <dongs> ?
12.03.02 #       <dongs> but there is just trash, ANSDEQ/0 filled shit
12.03.07 #       <pamaury> dongs: it jumps to 0X20
12.03.16 #       <pamaury> at least that what I see when I disassemble the file
12.03.47 #       <dongs> from waht offset?
12.03.50 #       <pamaury> 0
12.03.57 #       <dongs> you mean minus the header?
12.04.00 #       <pamaury> yes
12.06.53 #       <dongs> ok, yeah.
12.06.59 #       <dongs> as soon as i jump and run that, it powers off.
12.07.03 #       <dongs> hmm.
12.07.20 #       <pamaury> can you step through the code ?
12.07.25 #       <dongs> yeah
12.07.49 #       <dongs> not until power off part tho.. only tried few instructions. trying to figure out how to make it properly load in debugger and not just cli stepping
12.08.46 #       <pamaury> the first executed instructions should be:
12.08.46 #       <pamaury> b 0x20
12.08.46 #       <pamaury> msr     CPSR_c, #211    ; 0xd3
12.08.46 DBUG    Enqueued KICK pamaury
12.08.46 #       <pamaury> bl      0x7378
12.08.51 #       <dongs> yes
12.09.11 Ctcp    Ignored 2 channel CTCP requests in 23 hours and 30 minutes at the last flood
12.09.11 #       * pamaury disappears for an hour
12.09.26 #       <dongs> ill step it until it powers off :)
12.31.41 #       <dongs> hmm power consumption reduced by 10mA
12.31.44 #       <dongs> whilestepping
12.50.03 Quit    igitoor (Ping timeout: 245 seconds)
12.52.14 #       <pamaury> dongs: did you find out when it powers of f?
12.53.34 Join    igitoor [0] (igitur@2a00:d880:3:1::c1ca:a648)
13.00.06 Quit    igitoor (Changing host)
13.00.07 Join    igitoor [0] (igitur@unaffiliated/contempt)
13.04.58 #       <dongs> no im still steeping to there
13.04.59 #       <dongs> lol
13.08.30 Join    __builtin [0] (3f5874b2@gateway/web/freenode/ip.63.88.116.178)
13.09.03 Join    shmap [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
13.09.12 #       <shmap> ppl what happen to the forums?
13.09.35 #       <shmap> I tried to load forums.rockbox.org/index.php?topic=51277.0
13.09.42 #       <shmap> doesnt work...
13.09.49 #       <dongs> probly dead, it was dead around same time yesterday too
13.10.07 #       <__builtin> they've been intermittent lately
13.10.47 Nick    __builtin is now known as __builtin[WEB] (3f5874b2@gateway/web/freenode/ip.63.88.116.178)
13.11.23 #       <shmap> I really need an entry a friend of mine put there.... there were some good answers that he needs now...
13.11.52 #       <__builtin[WEB]> try archive.org
13.11.59 #       <shmap> doesnt work
13.12.24 #       <__builtin[WEB]> google cache？
13.13.33 #       <shmap> loads for hours
13.13.40 #       <dongs> click "text only link"
13.13.45 #       <dongs> on google cache page.
13.14.28 #       <dongs> hm
13.14.40 #       <shmap> please send me the link to google cahce
13.14.50 #       <dongs>  < shmap> loads for hours
13.14.55 #       <shmap> and btw how to change nickname w/o relogging
13.14.56 #       <dongs> i presumed you had that link
13.15.14 #       <__builtin[WEB]> use /nick
13.15.29 #       <dongs> cache looks perfectly fine for me
13.15.31 Nick    shmap is now known as shmap_the_map (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
13.15.45 #       <dongs> loads instantly
13.16.05 #       <dongs> my Clip Zip freezes at "boot 4.0" in rockbox, and shows green screen when trying to load OF. I cant connect to pc, cause neither of the firmwares (not the sansa, nor the rockbox) boot up. what can I do? 
13.16.10 #       <dongs> Clip zip, 4GB internal, tried anything with and without mSD card. 
13.16.32 #       <dongs> pamaury: weird. now if i step it doesnt power off immediately
13.16.51 #       <shmap_the_map> can u give me a link?
13.16.51 #       <dongs> but doenst do much either
13.17.00 #       <dongs> http://webcache.googleusercontent.com/search?q=cache:qYLGc_KFd74J:forums.rockbox.org/index.php%3Ftopic%3D51277.0+&cd=3&hl=en&ct=clnk&gl=us
13.17.44 #       * __builtin[WEB] has an idea
13.18.23 #       <__builtin[WEB]> how does active noise cancellation sound to you guys?
13.18.24 #       <dongs> pamaury: now its endless cycling in 0x34 or so
13.18.24 #       <dongs> hmm
13.18.48 #       <dongs> i suopose i should try building this, then try to match stepping elf w/source vs the stuff thats loaded
13.18.54 #       <dongs> so I can at least follow to what is being done
13.19.11 #       <shmap_the_map> dongs how to make it load text only?
13.19.26 #       <dongs> top left corner, say s"text only version'
13.19.32 #       <dongs> http://webcache.googleusercontent.com/search?q=cache:qYLGc_KFd74J:forums.rockbox.org/index.php%3Ftopic%3D51277.0&num=1&hl=en&gl=us&strip=1&vwsrc=0
13.19.34 #       <shmap_the_map> nvm
13.19.47 #       <dongs> it looks like ass, but readable even if original site is down.
13.19.49 #       <pamaury> dongs: 0x34 is the copy loop I think
13.19.54 #       <dongs> oh?
13.19.59 #       <dongs> well, its spending way too long in there anyway
13.20.11 #       <dongs> ill let it run then :p
13.20.11 #       <pamaury> err sorry
13.20.17 #       <pamaury> I was looking at the wrong file :-p
13.20.30 #       <dongs> ya 34 looks useless
13.20.41 Join    mutnai [0] (6db91733@gateway/web/freenode/ip.109.185.23.51)
13.20.48 #       <pamaury> I think it's the IBSS clearing loop
13.21.06 #       <pamaury> I would need to rebuild it to get a map of symbols to be sure
13.21.24 Quit    mutnai (Client Quit)
13.21.32 #       <dongs> at any rate its been there way longer than it should have been
13.21.39 #       <dongs> and power consumptiuon up 20mA while its looping there
13.21.40 #       <dongs> heh
13.22.06 #       <dongs> i think im gonna hve to get build stuff running and get matching .elf for the bootloader
13.22.12 #       <dongs> to have some hope of debugging it properly
13.22.18 #       <pamaury> you can look in target/arm/crt0.S
13.22.31 #       <pamaury> I think that's what it's stuck in, since that's the very early init
13.22.47 #       <pamaury> do you have a cross compiler?
13.27.02 #       <shmap_the_map> what device are u guys talking about
13.27.07 #       <shmap_the_map> ?
13.30.47 #       <dongs> pamaury: no, i mean, it went through lots of other stuff
13.30.54 #       <dongs> then goes to get stuck in there
13.31.14 #       <dongs> HEY HEY HEY
13.31.18 #       <dongs> i have plug usb cable
13.31.22 #       <dongs> in rockbox font :D:D:D
13.31.36 #       <dongs> HMMMM
13.31.50 #       <dongs> what should I do~
13.32.25 #       <dongs> does that mean rockbox USB stack is gonna work?
13.32.26 #       <dongs> hmmm
13.33.59 #       <dongs> pamaury: tell me what to do. I have "Plug USB cable" in center of screen. 
13.34.25 #       <dongs> i think my previous poweroff might have been due to current limiting on the psu
13.34.28 #       <dongs> i set it to only 100mA
13.34.38 #       <dongs> i didnt consider it might jump above during boot
13.35.06 #       <dongs> now its drawing 77mA at that usb screen
13.36.03 #       <dongs> bootloader USB mode!
13.36.58 #       <dongs> .. bootloader USB drive came up as 1335.84 gigabytes
13.37.43 #       <freesoftware> beautiful
13.38.09 #       <dongs> yes
13.38.20 #       <freesoftware> now shove all your data on it, no one will ever find it
13.38.27 #       <freesoftware> perfect security
13.38.54 #       <dongs> thats further than I got on this before so it is progress
13.39.25 Quit    __builtin[WEB] (Ping timeout: 260 seconds)
13.39.51 #       <freesoftware> maybe it's controller limit?
13.39.59 #       <dongs> thats good news
13.40.10 #       <dongs> i just need to attach a couple ssd960pros to it
13.40.37 #       <freesoftware> that's pcie
13.41.10 Quit    shmap_the_map (Ping timeout: 260 seconds)
13.41.17 #       <dongs> no, thats nvme
13.41.24 #       <dongs> (there's actually a difference, too)
13.41.29 #       <freesoftware> yeah but interface is pcie
13.42.40 #       <freesoftware> also the 950pro goes up to 100C during operation so watch out
13.43.39 Join    shmap_the_map [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
13.48.52 Join    nothing [0] (2e13555c@gateway/web/freenode/ip.46.19.85.92)
13.49.28 Nick    nothing is now known as shnatot (2e13555c@gateway/web/freenode/ip.46.19.85.92)
13.51.27 #       <shnatot> Champange shower
13.56.20 Quit    shnatot (Ping timeout: 260 seconds)
13.56.33 Join    fujisan [0] (~fujisan@unaffiliated/fujisan)
13.56.45 ***     Saving seen data "./dancer.seen"
13.59.50 Quit    shmap_the_map (Ping timeout: 260 seconds)
14.04.11 Join    natanelho [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
14.04.27 #       <natanelho> people can you help me?
14.04.42 #       <natanelho> my clip zip wont boot up...
14.05.04 #       <dongs> sounds like youve got the same problem I'm solving now :p
14.05.16 #       <natanelho> wut :-<
14.05.23 #       <natanelho> ok...
14.05.31 #       <natanelho> loops in "boot 4.0"
14.05.49 #       <natanelho> green screen when trying to boot of
14.05.54 #       <natanelho> OF*
14.06.18 #       <natanelho> and makes headaches to my pc
14.06.28 #       <natanelho> pcaches*
14.08.37 #       <natanelho> tried to connect to  usb  while holding left, still green screen. connect usb while center is pressed, in my linux pc and it shows up on the left, "3.9 gb media device" and doesnt responds when clicking on it.
14.09.04 #       <natanelho> also it that state it doesnt show anything on the clips' screen
14.09.18 #       <natanelho> #dongs what should I do?
14.09.43 #       <dongs> i dont know, im waiting for  instructions too
14.09.47 #       <dongs> mine shows up as 1.3tb media device
14.10.00 #       <natanelho> WUT?
14.10.13 #       <natanelho> FREE STORAGE? LOL
14.10.35 #       <dongs> http://i.imgur.com/3kCGEob.png i hope so
14.11.01 #       <natanelho> also clip zip?
14.11.10 #       <dongs> clip+
14.11.19 #       <dongs> + for the "free storage"
14.11.27 #       <natanelho> LOLOLOL
14.11.39 #       <natanelho> I wouldnt complain in your place
14.11.51 #       <natanelho> sell it on ebey for tons of cash lol
14.12.23 #       <dongs> as soon as I get it working without a ratsnest of wires attached to make it boot, yes
14.13.40 #       <natanelho> I havent hardmodded mine yet
14.18.01 #       <natanelho> can I somehow format my 4gb rockbox player?
14.18.09 #       <pamaury> dongs: so I take it that you managed to get the full usb drive ?
14.18.46 #       <pamaury> however I *think* that rockbox usb only exposes the user part of the disk, you can't use it to reflash the OF (which you need to to reflash the bootloader)
14.18.47 #       <dongs> well
14.18.48 #       <dongs> kinda
14.18.55 #       <pamaury> for that you might need a custom build
14.19.03 #       <dongs> pamaury: but its showing up as 1.3tb drive
14.19.12 #       <dongs> i guess because tehre's absolutely no partition/etc info on the flash
14.19.15 #       <pamaury> interesting...
14.19.16 #       <dongs> wondering what i should do with it 
14.19.28 #       <pamaury> can you read/write from/to it ?
14.19.35 #       <pamaury> (using dd)
14.19.42 #       <dongs> yeah i considered trying
14.20.32 #       <pamaury> I think that's the first step
14.20.44 #       <pamaury> making sure the nand works (and persists accross boots)
14.21.00 #       <dongs> tryin to find dd.exe that does raw drives
14.21.10 #       <pamaury> if it works, we should do a special build to give full access to the storage and reflash the bootloader
14.21.18 #       <dongs> yes
14.21.20 #       <pamaury> are you using windows ?
14.21.46 #       <dongs> got it, i had one that does raw devices
14.22.26 #       <dongs> ok, reading = all zers, lemme write some random trash to it
14.22.29 #       <dongs> and see if i get anything else back
14.23.18 #       <dongs> damnit
14.23.18 #       <dongs> nope
14.23.28 #       <dongs> pamaury: read back is zeros
14.23.31 #       <natanelho> pamaury can u help me? 
14.23.57 #       <natanelho> my clip zip wont boot up...
14.23.59 #       <dongs> i guess ill try back when I get 4gb flash
14.24.10 #       <dongs> 512m is probly not working for ~reasons
14.24.38 #       <dongs> < dongs> http://i.imgur.com/3kCGEob.png < does that drive serial look like something rockbox would set?
14.24.48 #       <pamaury> natanelho: did you try to hold power for 20sec ?
14.24.49 #       <dongs> what's it based on i wonder
14.25.12 #       <natanelho> yea
14.25.30 #       <natanelho> it forces shut down
14.25.52 #       <pamaury> natanelho: and nothing happens when you press power ? What happens if you plug the usb cable ?
14.26.19 #       <dongs> *PANIC* mount: 0
14.26.22 #       <natanelho> it does *some*thing when I press power button
14.26.22 Quit    dfkt (Disconnected by services)
14.26.33 Join    dfkt_ [0] (~dfkt@unaffiliated/dfkt)
14.26.37 #       <pamaury> dongs: given the wrongly reported size, it is likely the sd to nand layer doesn't like your flash or gets confused
14.26.45 #       <dongs> right
14.26.53 #       <natanelho> I loops in "boot 4.0"
14.27.09 #       <natanelho> it*
14.27.13 Quit    dfkt_ (Client Quit)
14.27.26 #       <pamaury> you mean it prints boot 4.0 and does nothing ? or it reboots in a loop ?
14.28.01 #       <natanelho> pamaury: it prints boot 4.0 and does nothing, for really long time
14.28.11 #       <natanelho> like till the battery drains
14.28.28 #       <natanelho> or for a week if left in charger
14.28.39 #       <dongs> pamaury: ok, cool, so it is booting consistently now with just loading image and adjusting memory remap and jumping to pc=0
14.29.00 #       <dongs> power down was due to current spike and psu limiting it.
14.29.14 #       <dongs> now i just have to get new flash into it .
14.29.26 #       <dongs> and fix bootloader to expose entire flash area (if it works)
14.29.43 #       <pamaury> dongs: good, so yeah you need a new flash I guess. It's hard to help on this part, this is completely undocumented
14.30.18 #       <pamaury> to be honest I am really surprised that the FTL is done in the soc, because that would mean either a third hidden process or a very dumb FTL
14.30.38 #       <pamaury> also it's not described in the AS3525 manual
14.30.45 #       <dongs> yep, hardware part I can handle. ill get soem 32 and 64gbit nand in the next few weeks to try out
14.31.07 #       <pamaury> dongs: what is the part number of the original flash ?
14.31.14 #       <dongs> pamaury: well its just an IP core, i dont know why they would go nand->SD maybe for programming easy purposes? who knows.
14.31.21 #       <dongs> its.. sec
14.31.26 #       <pamaury> natanelho: if you plug usb, do you get a usb driver ?
14.31.31 #       <dongs> i only have 4gig ones
14.31.37 #       <dongs> SDTNNMAHSM-004G
14.31.42 #       <pamaury> dongs: SD is *much* easier
14.31.51 #       <pamaury> dongs: is it from sandisk ?
14.31.55 #       <dongs> im gonna get MT29F32G08CBADAWP and MT29F64G08CBABAWP
14.32.01 #       <dongs> yeah
14.32.04 #       <natanelho> pamaury: no
14.32.08 #       * pamaury pulls his sandisk flash part decoder
14.32.23 #       <dongs> according to internet its 32nm MLC flash.
14.32.36 #       <pamaury> dongs: did you find the specific datasheet ?
14.32.42 #       <dongs> nope not at all
14.32.48 #       <dongs> the fact that sandisk got bought by WD doenst help
14.32.49 #       <pamaury> natanelho: that's a bad sign
14.33.14 #       <dongs> pamaury: he gets USB drive if he holds left or center, down
14.33.26 #       <natanelho> pamaury: it does show something when I hold center button while connecting the usb to linux
14.34.48 #       <pamaury> natanelho: if you hold left on boot (without usb), do you have a working device with the original firmware ?
14.35.04 #       <natanelho> no
14.35.09 #       <natanelho> green screen
14.35.19 #       <pamaury> dongs: is there any other part on the pcb?
14.37.55 #       <dongs> you mean?
14.38.59 #       <pamaury> some device have a discrete IC that does sd <-> nand
14.39.05 #       <dongs> ah, no
14.39.11 #       <dongs> clipplus is just that
14.39.18 #       <dongs> nand, SD socket, and AMS
14.39.45 #       <dongs> i dont find it particularly TOO crazy that nand would be accessible as SD to firmware.
14.40.02 #       <dongs> honestly I'd find it more crazy if sandisk did special SDIO-only "flash" ICs that only worked in their hardware
14.40.07 #       <dongs> that seems liek a waste of resources
14.40.17 #       <natanelho> pamaury: when I hold center and plug in usb it shows up on pc as media device, and shows 3.9 gb but then doesnt open
14.40.21 #       <pamaury> that's very unusual to have it in the soc though
14.40.42 #       <pamaury> natanelho: it seems to suggest a potentially bad flash
14.40.56 #       <natanelho> pamaury: and that means..?
14.41.04 #       <dongs> i have the original flash in a socket, but I gotta find my devboard where I can try bringing it up to the point of at least reading nand flash ID byte
14.41.43 #       <dongs> wont happen today
14.42.24 #       <dongs> anyway, if it returns some ID byte that means its basicalyl standard nand and should be able to be replaced, unless the hardware flash>sd translation layer specifically blacklists devices that arent sandisk
14.42.24 #       <pamaury> dongs: yeah that would be the ultimate test
14.42.41 #       <dongs> but google says it does return an id, etc
14.42.49 #       <pamaury> natanelho: that means you device is close to dead unless you swap the flash, something that dongs is trying to do
14.43.15 #       <natanelho> pamaury: no way to softmod?
14.43.19 #       <pamaury> dongs: the problem is that there is no real standard to get nand info
14.43.25 #       <dongs> eh, sure tehre is
14.43.31 #       <pamaury> the info you get in the last byte is far from being enough
14.43.45 #       <dongs> like 0x90 for read ID or whatever
14.44.01 #       <natanelho> isnt it some problem with installing rockbox wrongly or something?
14.44.30 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
14.44.42 #       <pamaury> that doesn't give you much info, it only works if you are going to have some very slow FTL
14.45.16 Join    ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:d527:80db:ecbd:d219)
14.45.21 #       <pamaury> natanelho: if you had rockbox installed and previously working, that seems unlikely
14.45.21 #       <pamaury> also if you cannot even reach usb mode in the original firmware, you have no way to reflash
14.46.15 #       <natanelho> I thought some linux magic code will save me :-<
14.46.25 #       <dongs> pamaury: i donno, readID looks solid for knowing its nand and not some weird shit. cuz if it actually responds to that then its decided.
14.47.23 #       <dongs> also, the same 004G IC has been used in USB flash drives
14.47.37 #       <pamaury> natanelho: can you pastebin the dmesg output of when you plug it in usb ?
14.48.05 #       <natanelho> what is it? how to get it?
14.48.50 Quit    PurlingNayuki (Ping timeout: 265 seconds)
14.48.59 #       <pamaury> natanelho: you are using linux ?
14.49.06 #       <natanelho> yea
14.49.14 #       <natanelho> I have windows too if needed
14.49.39 #       <pamaury> so plug you device in usb (and holding left), then in a command shell:
14.49.39 #       <pamaury> dmesg > dmesg.txt
14.49.51 #       <pamaury> and copy and paste dmesg.txt here: http://pastebin.com/
14.50.07 #       <pamaury> (and post the url here after that)
14.52.04 #       <natanelho> do u mean center key?
14.52.32 #       <natanelho> cause when holding left it just prints "boot 4.0"
14.52.38 #       <pamaury> center then
14.52.47 #       <pamaury> (the one that boots the original firmware)
14.55.43 Quit    fujisan (Quit: Textual IRC Client: www.textualapp.com)
14.56.41 Join    fujisan [0] (~fujisan@unaffiliated/fujisan)
14.56.42 #       <natanelho> http://pastebin.com/becxZpjJ
14.57.25 #       <natanelho> please wait i'll be back in a few minutes
14.59.12 #       <dongs> hey
14.59.17 #       <dongs> that serial number looks similar to the shit i get
14.59.54 Join    natanelho_ [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
15.00.09 #       <dongs> so yeah
15.00.33 #       <dongs> ill get a build environment going so i can step bootloader if needed and also to make adjustments to open entire flash to access
15.01.43 #       <dongs> gonna try run another set of solder across the flash too just incase i missed a pin
15.01.49 #       <dongs> then give up for the day
15.02.15 Quit    natanelho (Ping timeout: 260 seconds)
15.02.42 Nick    natanelho_ is now known as natanelho (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
15.02.53 #       <natanelho> heres another paste
15.02.54 #       <natanelho> http://pastebin.com/7wHBrnrn
15.03.31 #       <natanelho> that one is while holding center button, the previews one is while holding left
15.04.28 #       <natanelho> pamaury: do I have any hope?
15.04.32 Quit    Strife89 (Ping timeout: 258 seconds)
15.05.42 #       <natanelho> dongs: incase youre successful, please make a documentation of waht u do
15.06.22 #       <dongs> natanelho: it involves things like .. http://i.imgur.com/51tHgIW.jpg
15.06.40 #       <natanelho> because if you are right, we can solder a huge NAND in place of the 4gb right?
15.07.03 #       <dongs> not "huge" . nobody is making tssop nand anymore
15.07.08 #       <dongs> its all bga for high capacity
15.07.34 #       <dongs> 64gbit is max you can get
15.07.46 #       <natanelho> and thats a lot...
15.08.00 #       <natanelho> wait, megabit or megabyte?
15.08.05 #       <dongs> bit
15.08.07 #       <dongs> so 8gb.
15.08.17 #       <dongs> i.e. the max that was in sansa clip+
15.08.27 #       <natanelho> so sandisk offered the largest possible memory:-<
15.08.46 #       <pamaury> natanelho: try running fsck
15.08.52 #       <natanelho> whats that
15.08.56 #       <pamaury> sudo fsck -a /dev/sdc
15.09.03 #       <pamaury> it will try to fix the file system
15.10.06 #       <dongs> k. still comes up as 1.3tb after soldering, im 99.999% sure the connections are solid
15.10.15 #       <dongs> will try again when i get 4/8gib chips.
15.10.21 #       <natanelho> I think sdc is my flash drive, which runs the linux
15.10.51 #       <natanelho> pamaury: will it damage it?
15.11.41 #       <pamaury> natanelho: no
15.11.49 #       <dongs> pamaury: i think most interesting would be stepping through bootloader wehre it initializes the SD layer and stuff and see error/return codes there
15.12.15 #       <pamaury> natanelho: based on your dmesg output, sdc is the rockbox drive
15.13.13 #       <pamaury> dongs: rockbox panics on sd error for the internal storage
15.13.20 #       <dongs> mhm
15.13.28 #       <dongs> you mean *PANIC* mount: 0?
15.13.32 #       <dongs> thats what i get when i remove usb :d
15.13.51 #       <dongs> why doent it panic earlier tho when i plug usb in?
15.13.56 #       <pamaury> that's normal :-p No you would gte *PANIC* sd init -9
15.13.56 #       <pamaury> for example
15.14.04 #       <dongs> ah
15.14.20 #       <natanelho> fsck says "* is missing, cant fix yet" and stil lists a lot of my files, WTF
15.14.20 #       <pamaury> mount panics because it cannot find a valid filesystem on the driver
15.14.44 #       <dongs> hopefully its just because this ancient 512megabyte nand chip is just junk
15.14.49 #       <pamaury> natanelho: did you remove your drive without safely ejecting ?
15.14.51 #       <dongs> and it will just work(tm) with 8gib
15.15.13 #       <natanelho> pamaury: maybe a few years ago, 
15.15.27 #       <natanelho> when it last worked
15.15.51 #       <natanelho> I didnt touch it since, and I dont remember the cause of the problem
15.16.43 #       <natanelho> pamaury: does it mean its possible to fix it?
15.17.39 #       <pamaury> natanelho: if you don't care about the files currently on the device, I would say just reformat
15.17.54 #       <natanelho> the command still runs
15.18.05 #       <natanelho> how much time will it take?
15.18.16 #       <natanelho> I care about them somewhat
15.18.28 #       <pamaury> natanelho: ok, then wait until the command finishes
15.18.45 #       <pamaury> it might take a while, depending on how broken your filesystem is
15.18.50 #       <pamaury> fsck cannot fix all problems
15.19.01 #       <natanelho> estimate? no?
15.19.53 #       <natanelho> if its more then 5 hrs I wont bother...
15.21.19 #       <natanelho> how bad could removing w/o safely ejecting a usb be for the device?
15.21.24 #       <natanelho> like, deadly?
15.21.47 #       <pamaury> not for the device, but your filesystem may end up corrupted and you may need to reformat, in the worst case
15.25.39 #       <natanelho> theres a setting in windows that I might have touched, something along the lines of "make the device able to be removed w/o safely ejecting or use the old method (which is faster?)" AFAIK
15.27.04 Join    skapazzo [0] (~skapazzo@151.9.205.1)
15.27.11 #       <natanelho> I remember I messed with it, and it made some harm to me, I dont remember if that was the clip zip or a usb stick that was broken tho...
15.29.01 #       <natanelho> pamaury: in worst case scenario, how much time will it take to fsck to complete?
15.32.28 #       <pamaury> natanelho: no idea, there is no limit
15.36.23 #       <natanelho> :-<
15.36.39 #       <natanelho> so how to format it in worst case scenario?
15.38.46 #       <freesoftware> trash it and buy new
15.41.34 #       <gevaerts> If fsck takes a long time on a smallish flash device, I'd worry about the flash going bad
15.41.50 #       <gevaerts> Apart from that, mkfs.vfat should do the trick
15.43.01 #       <gevaerts> And then reinstall rockbox of course. The bootloader will still be there
15.44.18 Join    Strife89 [0] (~quassel@adsl-98-80-185-155.mcn.bellsouth.net)
15.45.09 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
15.47.50 Join    b-f-1 [0] (~user@s5596c859.adsl.online.nl)
15.49.02 Quit    pixelma (Disconnected by services)
15.49.02 Join    pixelma_ [0] (~pixelma@rockbox/staff/pixelma)
15.49.04 Join    amiconn_ [0] (~amiconn@rockbox/developer/amiconn)
15.49.05 Nick    amiconn is now known as Guest55409 (~amiconn@rockbox/developer/amiconn)
15.49.06 Quit    Guest55409 (Killed (rajaniemi.freenode.net (Nickname regained by services)))
15.49.06 Nick    amiconn_ is now known as amiconn (~amiconn@rockbox/developer/amiconn)
15.49.44 Quit    PurlingNayuki (Ping timeout: 265 seconds)
15.56.46 ***     Saving seen data "./dancer.seen"
16.01.27 #       <natanelho> gevaerts: how much is "long time"?
16.04.35 #       <natanelho> so what should I type to format the zip? 
16.16.20 #       <freesoftware> mkfs.vfat /dev/sdXY
16.35.00 Quit    natanelho (Ping timeout: 260 seconds)
16.46.21 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
16.51.07 Quit    PurlingNayuki (Ping timeout: 265 seconds)
16.55.17 Nick    __builtin_ is now known as __builtin (~xray@rockbox/developer/builtin)
17.03.58 Join    natanelho [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
17.06.11 #       <natanelho> does the clip zip charge the battery while it is connected to a pc in bootloader mod (connecting usb while holding center button
17.06.17 #       <natanelho> )
17.06.27 #       <natanelho> ?
17.06.45 Quit    freesoftware (Ping timeout: 268 seconds)
17.11.14 #       <pamaury> natanelho: yes
17.11.26 #       <pamaury> (I mean I would expect so)
17.14.13 #       <natanelho> so I gave up, how to format it?
17.15.19 #       <natanelho> the "disks" gui/aplication/whatever doesnt allow me to do it...
17.19.54 Quit    natanelho (Ping timeout: 260 seconds)
17.30.54 Join    natanelho [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
17.30.58 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
17.48.00 Quit    michaelni (Remote host closed the connection)
17.49.24 Quit    Saratoga (Quit: Page closed)
17.51.10 Join    michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at)
17.56.50 ***     Saving seen data "./dancer.seen"
18.00.17 Join    naleo [0] (~naleo@unaffiliated/naleo)
18.01.18 Join    edhelas [0] (~edhelas@145.133.43.230)
18.01.54 Quit    natanelho (Ping timeout: 260 seconds)
18.12.58 Join    dfkt [0] (~dfkt@unaffiliated/dfkt)
18.13.12 Quit    munch` (Quit: Let's blast this shit and get naked)
18.13.49 Join    munch [0] (pls@gateway/shell/elitebnc/x-pxkymapqlvzgyhrg)
18.15.48 Quit    edhelas (Ping timeout: 248 seconds)
18.23.51 Join    natanelho [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
18.30.17 Join    natanelho_ [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
18.30.29 Quit    natanelho (Ping timeout: 260 seconds)
18.33.01 #       <natanelho_> pamaury: I cant format my device... I tried mkfs, mkfs.vfat, the "disks" and each time I try to access it via any command it says some random error and then the device disapears form the list on the left (ubuntu) and form the list in the "disks" gui...
18.33.08 #       <natanelho_> what should I do?
18.36.51 #       <pamaury> natanelho_: that sounds like your flash is failing
18.36.57 #       <pamaury> you can't do much I'm afraid
18.37.41 #       <natanelho_> but, then, why does it show me "3.9 GB" when connected?
18.39.43 Nick    natanelho_ is now known as natanelho (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
18.40.04 #       <pamaury> because it's not completely dead yet, most probably some read/writes are randomly failing, and at some point it will fail completely
18.40.08 #       <pamaury> that's what usually happen
18.47.50 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
18.52.07 Quit    PurlingNayuki (Ping timeout: 245 seconds)
18.52.37 Join    Mihail [0] (252d5ec6@gateway/web/cgi-irc/kiwiirc.com/ip.37.45.94.198)
18.53.05 #       <Mihail> natanelho_: Remove partition (if you have it) on your player and try create new small partition (10MB) and format it. If it OK, write rockbox directory on it.
18.56.09 Quit    natanelho (Ping timeout: 260 seconds)
19.08.37 Join    natanelho [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
19.08.57 #       <natanelho> Mihail: how to do it?
19.10.48 #       <natanelho> and will 10 mb be enough for this?
19.12.04 Join    edhelas [0] (~edhelas@145.133.43.230)
19.12.31 #       <Mihail> yes, I usually use fdisk but it not user friendly. Probably better try some gui program
19.13.07 #       <natanelho> what should I type in for fdisk?
19.13.18 #       <natanelho> the device is /dev/dsc
19.13.26 Quit    edhelas (Client Quit)
19.13.30 #       <natanelho> I mean /dev/sdc
19.13.49 Quit    alexweissman (Remote host closed the connection)
19.16.23 #       <Mihail> fdisk /dev/sdc than press 'p' - it show all partition (if you have)
19.18.28 #       <natanelho> ok...
19.18.43 #       <natanelho> Michail: what now ?
19.18.59 #       <natanelho> Mihail: ?
19.19.12 #       <Mihail> did you see any partition?
19.19.53 #       <natanelho> http://pastebin.com/XN0xKusk
19.21.33 #       <Mihail> create new partition - press 'n'
19.22.09 #       <natanelho> p/e?
19.22.12 #       <Mihail> p
19.22.21 #       <natanelho> 1-4?
19.22.24 #       <Mihail> 1
19.23.15 #       <natanelho> First sector (2048-7683071)?
19.23.27 #       <Mihail> 2048
19.23.37 #       <natanelho> last?
19.24.31 #       <Mihail> 22528
19.25.02 #       <natanelho> Created a new partition 1 of type 'Linux' and of size 10 MiB.
19.25.05 #       <natanelho> now what?
19.25.06 Quit    lebellium (Quit: ChatZilla 0.9.93 [Firefox 50.1.0/20161208153507])
19.25.19 #       <Mihail> press 'w'
19.25.44 #       <natanelho> The partition table has been altered.
19.25.58 #       <natanelho> (and its thinking....)
19.26.06 #       <Mihail> good, reconnect player
19.26.24 #       <natanelho> shouldnt I wait for it to finish?
19.27.10 #       <Mihail> is ask command?
19.27.27 #       <natanelho> I dont think so
19.27.56 #       <Mihail> and it not return to shell?
19.28.06 #       <natanelho> it did
19.28.16 #       <Mihail> ok, reconnect
19.28.17 #       <natanelho> sorry, didnt understand
19.28.25 #       <natanelho> ok
19.29.47 #       <natanelho> reconected, doesnt seem to pop up
19.30.10 #       <Mihail> try format new partition: mkfs.vfat /dev/sdc1 (or what you have)
19.31.54 #       <natanelho> No such file or directory
19.32.13 #       <natanelho> think a restart for the pc would help... brb
19.32.31 #       <Mihail> what you have in dmesg after player reconnection?
19.35.53 Join    natanelho_ [0] (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
19.36.02 #       <natanelho_> so where were we?
19.36.33 #       <Mihail> try connect it and check what you have in dmesg
19.36.59 Quit    natanelho (Ping timeout: 260 seconds)
19.37.40 #       <natanelho_> http://pastebin.com/9FXChFDu
19.37.46 #       <natanelho_> thats what he says
19.38.41 #       <natanelho_> the "disks" gui shows one 3.9gb device, I am afraid to click on it to look at it
19.39.13 #       <Mihail> no partition (sdc1) :( Try again fdisk /dev/sdc
19.42.49 #       <natanelho_> http://pastebin.com/VPKNGisD
19.43.52 #       <Mihail> try remove it all - press 'd'
19.44.34 #       <natanelho_> Disk /dev/sdc: 3.7 GiB, 3933732864 bytes, 7683072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x6f20736b
19.45.46 #       <Mihail> if no more partition in 'p' - try create new one - as we try before
19.47.30 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
19.49.02 #       <natanelho_> created one 3.7gb long
19.49.23 #       <natanelho_> http://pastebin.com/EFtJUkbv
19.50.34 #       <Mihail> delete it - you need small partition without bad sectors
19.51.50 #       <natanelho_> Created a new partition 1 of type 'Linux' and of size 19 MiB.
19.51.57 #       <Mihail> ok
19.52.01 #       <Mihail> try 'w'
19.52.18 #       <natanelho_> The partition table has been altered.
19.52.27 #       <natanelho_> and it takes its time...
19.52.51 #       <Mihail> is it return to shell or freeze?
19.53.19 #       <natanelho_> last time it took a minute or two... ill give it that
19.53.39 #       <natanelho_> freezes
19.53.45 #       <Mihail> bad sign. what you have in dmesg?
19.53.55 #       <natanelho_> nvm returned to shell
19.54.49 #       <natanelho_> http://pastebin.com/WZKjNXBU
19.54.57 #       <natanelho_> ^dmesg^
19.55.42 Quit    b-f-1 (Remote host closed the connection)
19.56.22 #       <Mihail> many usb errors. Try connect with another short usb cable and do all again
19.56.53 ***     Saving seen data "./dancer.seen"
20.01.23 Quit    fujisan (Ping timeout: 248 seconds)
20.05.23 #       <natanelho_> Command (m for help): p  Disk /dev/sdc: 3.7 GiB, 3933732864 bytes, 7683072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x6f20736b  Command (m for help): n Partition type    p   primary (0 primary, 0 extended, 4 free)    e   extended (container for logical partitions) Select (default p): p 
20.05.28 #       <natanelho_> sorry
20.06.09 #       <natanelho_> Mihail: http://pastebin.com/dG1R4Dig
20.06.34 #       <natanelho_> this is the output. this time it didnt freeze at all after "w"
20.08.23 #       <Mihail> good try mkfs.vfat /dev/sdc1
20.09.08 #       <natanelho_> done in no time at all
20.09.10 #       <natanelho_> :-)
20.09.17 #       <Mihail> try mount
20.10.00 #       <natanelho_> mount: can't find /dev/sdc1 in /etc/fstab
20.10.40 #       <Mihail> try full mount command - mount /dev/sdc1 /yourdir
20.11.41 #       <natanelho_> what in yourdir?
20.12.14 #       <Mihail> create any - it just mount point - /mnt/sdc1 for example
20.13.33 #       <Mihail> or you already mount to  yourdir?
20.14.24 #       <natanelho_> done
20.14.37 #       <natanelho_> sudo mount /dev/sdc1 /mnt/rock
20.14.56 #       <natanelho_> thats what I did and it returned to shell imediatly
20.15.06 #       <Mihail> great ;) try extract rockbox to /mnt/rock
20.15.20 #       <natanelho_> what files?
20.15.27 #       <natanelho_> from where?
20.15.33 Quit    alexweissman (Remote host closed the connection)
20.15.44 #       <natanelho_> and will it b enough for plugins and themes?
20.16.02 #       <natanelho_> (I have 20 mb
20.16.12 #       <Mihail> You have zip? https://build.rockbox.org/data/rockbox-sansaclipzip.zip
20.16.24 #       <natanelho_> thx
20.16.38 #       <natanelho_> latest build or 3.1.3
20.16.39 #       <natanelho_> ?
20.16.50 #       <Mihail> my link better
20.18.33 #       <natanelho_> thats what I ask
20.18.41 #       <natanelho_> wut version is it
20.18.47 Nick    natanelho_ is now known as natanelho (4d8a29a2@gateway/web/freenode/ip.77.138.41.162)
20.18.54 #       <Mihail> latest build
20.19.00 #       <natanelho> k
20.20.20 Join    alexweissman [0] (~alexweiss@pool-108-51-84-48.washdc.fios.verizon.net)
20.23.26 #       <natanelho> now ubuntu gives some problems :-(
20.23.38 #       <natanelho> trying to extract yr zip
20.23.46 #       <natanelho> it says "ok"
20.24.08 #       <natanelho> then I cant see any new file in the output dir
20.24.57 #       <Mihail> try reconnect
20.25.39 #       <natanelho> nooo
20.25.54 #       <natanelho> cant extract the files u gave me
20.25.59 #       <natanelho> inside my pc
20.27.21 #       <Mihail> Try extract it in home user directory
20.28.19 #       <natanelho> in the end I used the installer... worked!
20.28.23 #       <natanelho> thx!
20.28.37 #       <natanelho> wow I really appriciate your help!
20.29.01 #       <natanelho> the other pasimists really almost made me give up....
20.30.02 #       <natanelho> I installed latest build, with only "rockbox" being selected (no games/themes/fonts)
20.31.22 #       <Mihail> We have work on special bootloader from sd card for similarcase (http://forums.rockbox.org/index.php/topic,51304.msg237134.html) But now forum is down :(
20.32.30 #       <natanelho> try google cache
20.32.43 #       <natanelho> I'm looking forward to it!
20.33.03 #       <Mihail> Probably your problem was in bad usb cable and  you can try again with full sized partition
20.33.41 #       <natanelho> it wasnt the cable, it was the port.
20.34.00 #       <natanelho> interestingly everything else works fine on it
20.35.50 #       <natanelho> hmmm now the servers load me a "database error" page... hmmm it wasnt there 2 hrs ago...
20.44.18 Join    edhelas [0] (~edhelas@145.133.43.230)
20.49.12 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
20.51.25 Quit    alexweissman (Remote host closed the connection)
20.53.39 Quit    PurlingNayuki (Ping timeout: 248 seconds)
21.16.39 Join    JanC_ [0] (~janc@lugwv/member/JanC)
21.16.42 Join    idonob [0] (~Owner@static-173-212-139-201.ptr.terago.net)
21.17.54 Quit    JanC (Killed (barjavel.freenode.net (Nickname regained by services)))
21.17.54 Nick    JanC_ is now known as JanC (~janc@lugwv/member/JanC)
21.22.52 Join    rela_ [0] (~x@p200300764D68AA00A0B011247A05BFD0.dip0.t-ipconnect.de)
21.26.04 Quit    rela (Ping timeout: 260 seconds)
21.36.02 Join    alexweissman [0] (~alexweiss@2601:143:8001:e5f1:509a:96c1:cdc4:95f3)
21.50.08 Join    PurlingNayuki [0] (~Thunderbi@114.255.40.10)
21.52.39 Quit    skapazzo (Quit: Lost terminal)
21.54.39 Quit    PurlingNayuki (Ping timeout: 265 seconds)
21.54.55 Quit    rela_ (Quit: Leaving)
21.56.54 ***     Saving seen data "./dancer.seen"
21.56.54 Join    Jinx [0] (Dojo@unaffiliated/jinx)
22.02.14 Quit    natanelho (Ping timeout: 260 seconds)
22.16.09 Join    smoke_fumus [0] (~smoke_fum@dynamic-vpdn-93-125-14-78.telecom.by)
22.35.55 Quit    Mihail (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
23.12.13 Join    mutnai [0] (6db91733@gateway/web/freenode/ip.109.185.23.51)
23.12.28 Quit    mutnai (Client Quit)
23.19.22 Quit    prof_wolfff (Ping timeout: 246 seconds)
23.39.09 Join    prof_wolfff [0] (~prof_wolf@82.159.0.123.dyn.user.ono.com)
23.51.48 Quit    edhelas (Read error: Connection reset by peer)
23.56.57 ***     Saving seen data "./dancer.seen"
23.57.33 Join    edhelas [0] (~edhelas@145.133.43.230)