--- Log for 21.08.121 Server: lithium.libera.chat Channel: #rockbox --- Nick: rb-logbot Version: Dancer V4.16 Started: 11 days and 14 hours ago 00.12.45 *** Saving seen data "./dancer.seen" 02.12.47 *** No seen item changed, no save performed. 03.30.36 Join ZincAlloy [0] (~Adium@ip5f5abcae.dynamic.kabel-deutschland.de) 04.12.50 *** No seen item changed, no save performed. 05.28.38 Join lebellium [0] (~lebellium@2a01:cb10:2e:2000:4423:4dcc:dba8:6f39) 06.11.13 Join akaWolf [0] (~akaWolf@2a05:3580:df03:1a00:21e:8cff:fe18:61) 06.12.53 *** No seen item changed, no save performed. 07.19.43 Quit akaWolf (Remote host closed the connection) 07.23.23 Join akaWolf [0] (~akaWolf@akawolf.org) 08.12.56 *** Saving seen data "./dancer.seen" 08.52.45 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net) 10.12.57 *** No seen item changed, no save performed. 10.35.45 Quit tomato (Ping timeout: 248 seconds) 10.49.01 Join tomato [0] (~tomato@user/tomato) 11.11.04 Join F3l1x_10m [0] (~Al3x_10m@user/f3l1x-10m/x-3393542) 12.09.14 Quit speachy (Quit: WeeChat 3.2) 12.13.00 *** Saving seen data "./dancer.seen" 13.14.27 Join speachy [0] (~speachy@209.2.65.77) 13.14.27 Quit speachy (Changing host) 13.14.27 Join speachy [0] (~speachy@rockbox/developer/speachy) 13.14.27 Mode "#rockbox +v speachy" by ChanServ (ChanServ@services.libera.chat) 13.39.05 Join look [0] (~look@e200114.upc-e.chello.nl) 13.39.42 # hello! can rockbox run on the sandisk clip sport plus? 13.41.36 # or does it only work on older models? 13.42.04 Join johnb2 [0] (~johnb2@p4fd1050e.dip0.t-ipconnect.de) 13.42.11 # No 13.42.28 # only what is listed on the front page 13.42.37 # well, too bad, thanks for the quick reply :) 13.59.52 Quit johnb2 (Ping timeout: 250 seconds) 14.13.01 *** Saving seen data "./dancer.seen" 14.24.50 Join ats [0] (~ats@cartman.offog.org) 14.36.04 Quit cb (Ping timeout: 272 seconds) 16.07.39 Join cb [0] (~calvin@fctnnbsc38w-47-55-90-145.dhcp-dynamic.fibreop.nb.bellaliant.net) 16.13.02 *** Saving seen data "./dancer.seen" 17.08.59 Nick emacsoma1 is now known as emacsomancer (~emacsoman@136.60.128.68) 17.09.16 Join dconrad [0] (~dconrad@208.38.228.17) 17.23.39 Quit dconrad (Remote host closed the connection) 17.45.18 Quit lebellium (Quit: Leaving) 18.13.05 *** Saving seen data "./dancer.seen" 18.20.08 # speachy: i got an xduoo x3 but USB isn't working that I can tell. is this normal? it only seems to perform charging. 18.20.21 # maybe it's the cable. i'll try a different one. 18.21.37 # oh joy. it's a charge only cable. no data lines. 18.23.01 # weird. it makes a clicking sound or something when i turn it on. 18.32.16 Join dconrad [0] (~dconrad@208.38.228.17) 18.52.03 Join JanC_ [0] (~janc@user/janc) 18.54.10 Quit JanC (Ping timeout: 240 seconds) 18.55.07 Nick JanC_ is now known as JanC (~janc@user/janc) 19.15.22 Quit tchan (Ping timeout: 268 seconds) 19.15.42 Join tchan [0] (~tchan@c-98-206-141-238.hsd1.il.comcast.net) 19.25.12 # yep, relays in the power supply section 19.26.53 # speachy: pretty solid device but mine is a bit weird. i have to use a tool to get my sd card to lock into place. 19.27.12 # also, does rockbox care which sd card it is stored on? 19.28.04 # nope, but IIRC the bootloader won't fail over to the second card if both are inserted at startup 19.28.35 # interesting. 19.29.14 # old old bootloader build, lots of bugs fixed since then but didn't have the ability to generate a new flashable image 19.29.38 # why's that? 19.29.58 # the process isn't understood? 19.30.01 # too large? 19.30.15 # it was manually put together by xvortex. 19.30.20 # oh. 19.30.27 # so you don't know how to do it. 19.31.01 # speachy: what bugs were fixed that pertain to the bootloader? 19.32.01 # we can piggyback on the x1000 work done by amachronic. rework the build to generate the spl at the same time, then figure out how to retain dualboot 19.32.35 # this would work for the X3? even though it's a different SOC? 19.32.54 # fundamental low-level issues in the clocking and sd code, plus a lot of minor niggles in the bootloader itself 19.33.02 # ah i see. 19.33.38 # the low-level platform code (startup, asm routines, etc) also had a lot of issues I've since fixed. 19.34.04 # we should probably patch it then but how? 19.34.18 # this was about the time the hardware turned into mostly unobtanium 19.34.27 # i got my hands on one. 19.34.30 # recently 19.34.32 # but yea 19.34.37 # it's rare to find on ebay 19.34.40 # and my motivation to keep at it dwindled considerably. 19.35.03 # the x1000 is an evolution of the jz47xx series 19.35.27 # so how can we generate a new flash image? 19.36.06 # is there even any interest in trying to fix this now? 19.36.24 # have to generate a new flashable image, which means generating the spl (ie 1st-stage bootloader) that can then bootstrap the rest out of NAND 19.36.44 # is part of that already handled by rockbox tool chain? 19.37.41 # IIRC what actually was done is that the OF bootloader was hacked to load rockbox instead of the main linux system 19.38.00 # (I mean the rockbock bootloader binary) 19.38.16 # usnig the lock switch to determine which one was invoked 19.38.39 # basically the same trigger used on the gigabeat S 19.38.52 # xvortex was kinda vague on how he did it and couldn't provide any technical details/scripts 19.39.07 # and I didn't have the bandwidth to reverse-engineer things further 19.39.59 # he then took the stock OF firmware update image, and hacked in scripts/etc to ensure the patched bootloader flash partition was properly updated. 19.41.56 # that latter stuff is easy to reuse but the trick is to fix up 19.42.40 # so i need to find a place to launch the bootloader from 19.42.46 # the original bootloader image. IIRC xduoo never provided a pristine bootloader to work from 19.43.01 # (or sources) 19.43.41 # but in theory the new rockbox bootloader binary could be patched into the correct place of that binary and things will JustWork(tm) 19.43.58 # just a matter of motivation+time 19.45.44 # i wonder if we can use uboot to launch it. 19.46.47 # according to the wiki there's two options 19.47.03 # after linux boots is probably untenable unless kexec or similar is a choice 19.50.31 # I believe the real work is done in the stage1 spl. based on the switch it reads either the rockbox or uboot. 19.51.31 # it suggests the first tier bootloader is 8KB 19.52.02 # says nothing about where it is loaded from. 19.52.16 # just from the NAND. 19.52.33 # yep, looks like the rb bootloader binary is at offset 0x2000 19.53.30 # there's no attempt to document the NAND 19.53.37 # so hard to say 19.54.24 # hm 19.54.39 # we need a better way to install the bootloader 19.54.54 # something like beastpatcher for the xduo 19.55.16 # it's easy enough to modify the hacked update image. 19.55.33 # as that piggybacks on the existing xduoo update process 19.55.57 # i know just would like a better solution than binary diff 19.56.00 # if that makes sense 19.56.28 # we only bother with a binary diff due to the technically-not-allowed distribution of xduoo firmware images 19.57.40 # another option is to figure out how to repack it. 19.57.59 # and the uboot binary starts at offset 0x22004 19.58.01 # but in any case there's no way to update it until we can figure out how the existing hack works. 19.58.16 # so we have 128K to play with. 19.58.44 # it looks like we can recover if we botch it 19.58.47 # is that correct? 19.59.13 # " The JZ4760 chip has a usb recovery mode documented in the datasheet. The xDuoo X3 can be put in this mode by the following procedure: " 19.59.17 # yes but it's going to involve using jztool 19.59.26 # so it's not straightforward. 19.59.42 # well that'll help if i need to recover from a bad attempt 20.00.10 # this is a pretty good unit 20.00.39 # in any case 20.01.04 # it sounds like you're saying i should work off the existing update payload 20.01.22 # and see if i can hack the bootloader over the existing spot. 20.01.36 # yep. don't see why that won't work, aside from the ususal bootloader bugs 20.01.56 # if the entry point is retained it should work 20.02.20 # let's see if the bootloader still compiles 20.02.36 # it does. 20.03.03 # o.O i see 20.03.14 # i need to recompile my toolchains since i lack mips 20.03.29 # speachy: looks like i've found my next project once i finish with gigabeat S 20.04.19 # i think the xduo should get a fix up. it's hard to find but it still pops up so it's not like the hd300. :P 20.04.47 # speachy: btw, where did you get these numbers? 20.05.02 # inspecting the binary 20.05.05 # Oh. 20.05.27 # so rockbox bootloader is placed right after the first 8K? 20.05.33 # appears that way 20.05.35 # starting at location 0x2000 or 8192 20.05.54 # interesting 20.06.16 # well given what i'm reading it could be as simple as overlaying a new bootloader binary at that location 20.06.25 # as long as it doesn't touch ubot 20.06.42 # you know what's funny? 20.06.47 # as long as the binary is 128KB or less 20.06.58 # yea, no different than how coldfire is. 20.07.05 # it's placed at the last 64K of the ROM 20.07.14 # btw this is rearranged from the the OF. u-boot must have been compiled to be relocatable. 20.07.40 # if i get a working update zip 20.07.54 # will you want to setup a new bdiff for it? 20.08.20 # it's probably easiest to try to work off the existing one 20.08.24 # yep, there are definitely issues with the ancient snapshot that binary was generated from 20.08.44 # you mean the bootloader we have? 20.08.50 # that's the main thing we got 20.09.04 # the rest should largely just be the OF 20.09.07 # warts and all 20.09.20 # yep 20.09.40 # gimme a few to confirm this 20.09.46 # before you possibly brick things 20.10.35 # ok 20.13.05 Quit ZincAlloy (Quit: Leaving.) 20.13.08 *** Saving seen data "./dancer.seen" 20.18.05 Quit dconrad (Remote host closed the connection) 20.23.00 # seems the rootfs image was modified 20.23.03 # what else 20.23.29 # * braewoods boggles. 20.23.36 # the linux kernels are also different 20.29.31 Join dconrad [0] (~dconrad@208.38.228.17) 20.54.41 # braewoods: it looks like that should be safe 20.55.03 # it looks like they patched the uboot kernel 20.55.07 # given the script differences 20.55.11 # err 20.55.13 # uboot image 20.56.59 # I'm still missing where it skips over the spl when it copies the data out of nand but otherwise yeah, it's clearly just blindly reading at one offset or the other based on the lock switch 20.58.17 # so it's safe to blindly replace the rockbox binary at 128K at offset 2K. 20.58.45 # i don't know why he changed the linux kernels 20.58.52 # it may have just been changes to their containers 20.59.01 # dunno. 20.59.37 # we can strip out the kernels & rootfs so the update image only mangles the bootloader partition. 21.12.30 # would there be a point to that? 21.12.37 # in any case i'll do some research into it 21.12.53 # makes for a much smaller image only containing what's needed. 21.13.11 # the bootloader definitely needs work. 21.13.35 # well i'd want to know what the original changed and why 21.13.48 # i'm going to look at the linux kernel and see how it differs 21.13.58 # don't bother with the linux side of things 21.14.05 # we genuinely don't care. 21.14.16 # since it has no effect on anything we actually execute. 21.14.27 # the uboot part does 21.14.34 # to a degree 21.15.09 # hmm. I suppose it's possible they rejiggered the flash layout 21.15.23 # to make room for the rockbox bootloader binaru 21.33.38 Quit look (Read error: Connection reset by peer) 21.49.57 # speachy: i think i see why he modded it. 21.50.07 # i compared the actual files in it 21.50.14 # there's hooks for arbitrary code execution. 21.50.36 # in the final product this should not be needed. 21.50.56 # likewise the kernels can probably be kept unmodded 21.52.23 # given the lack of original source i want to keep the OF as pure as possible 21.52.41 # this bootloader smells of messy bits 21.52.52 Join cockroach [0] (~blattodea@user/cockroach) 21.53.54 # though it's weird how the OF wastes space on stuff it doesn't really need 21.54.07 # like networking software when the SoC has no NICs 21.54.40 # eh, would be extra effort to remove it 21.54.54 # think of generic devlelopment boards 21.55.03 # it's not like they needed flash space 21.56.32 # Build Server message: 3New build round started. Revision e07c460eef, 303 builds, 8 clients. 21.56.47 # ok, this will bring the essential bootloader fixups 21.57.20 Quit dconrad (Remote host closed the connection) 21.57.45 # there's more work to be done (eg don't initialize the display unless there's an error or we're entering USB mode) 22.08.00 # so far it seems the main changes under tools is the additions of 2 programs and the script 22.08.18 # so i think we might be able to get away with just keeping those changes and updating uboot blob 22.08.34 # let me see how the script is different 22.09.26 # ah just some script code to reprogram uboot 22.09.39 # i can't see any reason to retain the changes to the rest of it 22.09.46 # the linux files anyway 22.10.01 # probably best to leave it alone since we're a hosted port now 22.10.07 # err native 22.10.24 Quit cockroach (Ping timeout: 250 seconds) 22.10.29 # Build Server message: 3Build round completed after 838 seconds. 22.10.31 # Build Server message: 3Revision e07c460eef result: 4 errors 0 warnings 22.13.09 *** Saving seen data "./dancer.seen" 22.14.22 # speachy: DANGER WILL ROBINSON 22.22.47 # grr. gonna have to blacklist uzziyah-munkis 22.23.08 # Build Server message: 3New build round started. Revision 2c9e2db721, 303 builds, 8 clients. 22.23.20 # ok, another commit of bootloader things. 22.23.51 # at the point where I'd consider it ready to do the binary cut-n-paste 22.34.01 Quit advcomp2019 (Ping timeout: 252 seconds) 22.38.12 # Build Server message: 3Build round completed after 904 seconds. 22.38.14 # Build Server message: 3Revision 2c9e2db721 result: 4 errors 0 warnings 22.41.35 # speachy: same? 22.59.15 Join dconrad [0] (~dconrad@208.38.228.17) 23.01.41 Quit dconrad (Read error: Connection reset by peer) 23.01.52 Join dconrad [0] (~dconrad@208.38.228.17) 23.05.37 Quit skipwich (Ping timeout: 248 seconds) 23.08.16 # I'll deal with the blacklist tomorrow if he dpesn't fix it by then 23.37.57 # oh 23.47.03 # lol. xduoo x3 OF manual... 23.47.10 # "charing the battery" 23.47.33 Join Saijin_Naib [0] (~Saijin_Na@2603-7081-1d05-7230-f540-b6ad-b3a7-74ac.res6.spectrum.com) 23.54.01 Join Saijin_Naib_ [0] (~Saijin_Na@2603-7081-1d05-7230-a8f8-1a2e-1942-ed6e.res6.spectrum.com) 23.54.13 Join Saijin_Naib__ [0] (~Saijin_Na@2603-7081-1d05-7230-f540-b6ad-b3a7-74ac.res6.spectrum.com) 23.56.08 Quit Saijin_Naib (Ping timeout: 250 seconds) 23.58.18 Quit Saijin_Naib_ (Ping timeout: 250 seconds)