Xduoo x3

[wodz]

That is strong statement. AFAIK this implementation is copied from some respected source. It has some quirks (like byte copy for small sizes).

Be that as it may, the empirical evidence points to memset() not working properly.  Disabling the asm memset() allows the vorbis code to work.

(It's setting a 4 byte unaligned buffer to 0 before running a checksum algorithm)

Could you pop up on IRC for live discussion?

[speachy]

Could you pop up on IRC for live discussion?

Just as a heads-up for the lurkers -- wodz fixed a bug in the mips memset() code, and also merged the threading fixes, so it is now possible to build a working Xduoo X3 rockbox image from git master.

(As I've been putting this thing through daily-use paces, I've accumulated a growing pile of additional improvements that IMO are worth merging.  Ah, progress..)

[wodz]

From my POV the main blocker now is the lack of SPL1 code vortex used to prepare bootloader install package. I disassembled this binary and it looks very similar to https://github.com/ingenic-src-android/xboot/blob/jz-4780-4775-common/spl/ so maybe we can cleanly recreate it. Interestingly SPL1 in vortex's package is different to anything I could grab from xduoo site.

I've accumulated a growing pile of additional improvements that IMO are worth merging.  Ah, progress..)

Do not do that. Put small changes in gerrit (or commit directly if you are brave). You can always abandon patch/revert commit. Big pile of changes is a pain to merge and even bigger to debug later if some bug surfaces.

[speachy]

I've accumulated a growing pile of additional improvements that IMO are worth merging.  Ah, progress..)

Do not do that. Put small changes in gerrit (or commit directly if you are brave). You can always abandon patch/revert commit. Big pile of changes is a pain to merge and even bigger to debug later if some bug surfaces.

No worries, I know to keep the individual patches as small and self-contained as possible.

(I have 15 patches staged in my tree, eight of which are already in Gerrit)

[XVortex]

Hi all. Finally I found it:
Here is sources/binaries/script for X3 stock+rockbox stage1: https://mega.nz/#!tlVzGAZK!8lMWGP0WEo_gnVuLLrS2q4yH2BnG2v6TNSTxeCU_LY8

[wodz]

Great thanks!

I have a question however - the script simply concatenates spl1, r-boot and u-boot. In bootloader install file you provide there is definitely padding between spl1, r-boot and u-boot so r-boot starts @0x2000 and u-boot is aligned on nand blocksized offset. Since r-boot is searched @0x40000 and u-boot @0x60000 and nand blocksize is 0x20000 I think flasher puts 2 copies of spl1 @0x0 and @0x20000 (block0 and block1), rockbox bootloader is placed @0x40000 (block2) and u-boot @0x60000 (block3). Could you confirm my understanding of this?

[XVortex]

Yes there are couple of a spare spl areas at the begin of the flash and flasher deals with it automatically.
If you dump the NAND you will get them all. but only one (without errors) is used at boot time.

[wodz]

Interestingly provided spl1 code is terribly broken. gp is not initialized in startup code but is used since .sbss and .sdata sections are not empty.

[mrp]

Hello guys, I have xduoo x3 with Rockbox and recently I have been having issues with the gadget. When I try to turn it on (or when on charger) it just shows the boot logo of Rockbox .. it clicks (makes that sound) .. flashes and all over again .. with a 1 sec interval ... logo-click-flash-logo-click-flash ... all over again ...

hard reset (via button on the side) does not work at all .. do you know what it could be?

[speachy]

Hello guys, I have xduoo x3 with Rockbox and recently I have been having issues with the gadget. When I try to turn it on (or when on charger) it just shows the boot logo of Rockbox .. it clicks (makes that sound) .. flashes and all over again .. with a 1 sec interval ... logo-click-flash-logo-click-flash ... all over again ...

Pull out the SD card(s), what happens?  (bootloader should report an error about not finding an SD card..)

Also, does the OF start up if you power it on with the lock switch set?

If the OF works, and the bootloader errors out as expected without the card(s) present, then your problem is probably a corrupted SD card, and using the latest daily build on a blank SD card would be a worthwhile test.

[mrp]

Hello, I tried:

format the SD card to FAT32 ...

use the default firmware (update.zip file)

Tried to start without SD card and the lock on
this gives the following message:

Code: [Select]

xDuoo Audio
Digital audio player
Tried to start without SD card and the lock off
this gives the following message:

Code: [Select]

xDuoo X3 Rockbox Boot
Version d312ba8M-1603
Mounting disk ...
No partition found
Tried to start it with the SD card and the lock on
this gives the following message:

Code: [Select]

xDuoo Audio
Digital audio player
It even started once here ... that got off again .. via "hard reset" button I was able to make it until "Updating .. do not power off" but then it went off again and the same story..

the initial screen just flashes and the gadget turns off after a sec .. when with lock off (see below)


Tried to start it with the SD card and the lock off
this gives the following message:

Code: [Select]

xDuoo X3 Rockbox Boot
Version d312ba8M-1603
Mounting disk ...
Loading firmware ...
Error: File not found

btw: re Rockbox version ...

is it ok to use this version:
http://xvtx.ru/rockbox/download.htm

or this one:
https://build.rockbox.org/data/rockbox-xduoox3.zip
https://download.rockbox.org/daily/xduoox3/rockbox-xduoox3.zip

the size differs dramatically

[speachy]

Tried to start it with the SD card and the lock on
this gives the following message:

Code: [Select]

xDuoo Audio
Digital audio player
It even started once here ... that got off again .. via "hard reset" button I was able to make it until "Updating .. do not power off" but then it went off again and the same story..

This tells me that your player itself has most likely suffered a hardware failure, if the OF can't even boot up and run properly.  (BTW there was no need to re-flash the firmware..)

btw: re Rockbox version ...

is it ok to use this version:
http://xvtx.ru/rockbox/download.htm

or this one:
https://build.rockbox.org/data/rockbox-xduoox3.zip
https://download.rockbox.org/daily/xduoox3/rockbox-xduoox3.zip

the size differs dramatically

the xvortex "initial setup" is the only working OF image patched with the bootloader, so that is necessary to get going.  Once that is flashed, however, use the rockbox daily builds, as they are much newer than what xvortex has on his web site.

[mrp]

well I somehow made it work ... I can boot to the original one (even tho it still tries to look for the Rockbox - dunno why - when I have the lock off)

with the daily builds -> can I use them right away? or as an update on top of the vortex?

[speachy]

with the daily builds -> can I use them right away? or as an update on top of the vortex?

I'd recommend just nuking the .rockbox directory entirely and starting over with the latest daily build. 

Another option is to use one of the builds put out by Igor Poretsky -- His builds are generally stable, but his tree has a lot of additional patches that aren't upstreamed. (I've merged many of those patches in one form or another, but many remain..)

(There's nothing wrong with the vortex build; it's just quite old at this point. Also, because it was built from an unknown source tree, I can't promise there won't be any subtle issues doing an in-place upgrade due to stale files)

[mrp]

thx I will try it tmrw and let you know .. thx a lot for the help