Xduoo x3

[hd321kbps]

Is Rockbox for the player Xduoo x3?
Maybe someone will take? Now such a stir on the forums!
Built on a powerful processor Ingenic JZ4760B and has an analog DAC CS4398 from Cirrus Logic, and operational amplifiers OPA1612 and LMH6643
More about him can be found here.

[saratoga]

Is Rockbox for the player Xduoo x3?

No, just the devices on the front page. 

If you're interested in working on rockbox, see:

http://www.rockbox.org/wiki/NewPort

[pamaury]

Hi,
this is interesting. Me and Marcin Bukat are working on porting Rockbox to the Fiio X1 that uses the JZ4760B, PCM5142 DAC and OPA2322 + ISL28291 amplifiers: http://www.rockbox.org/wiki/FiioX1

The first step would be to document the player on the wiki, in a similar fashion to the Fiio X1: describe components, upload PCB pictures if you have some. Then try to get the firmware, possibly using a firmware update and try to extract it using our packtools in our repository (utils/jz4760/packtools). You can also come on our IRC channel to discuss: see http://www.rockbox.org/irc/ and my peudo is pamaury.

[pamaury]

I have created a wiki page to gather some information about the device, it can be found at http://www.rockbox.org/wiki/XDuooX3. I don't have the device so it's all based on the firmware update released.

[charleski]

If someone can add me to the Wiki users group I can edit there directly. No-one was available on IRC.

To get to recovery mode, turn the device off, press and hold the Esc/Home button and plug in a USB cable. The device appears in Windows Device Manager as a JZ4760 USB Boot Device, USB\VID_601A&PID_4760\7&1ea98c86&0&4 USB class FF USB protocol 50 (i.e vendor ID 601A, product ID 4760 as in the wiki). To return to normal operation, disconnect the USB cable and press the recessed reset button on the right side.

To update the device, navigate to TopMenu->Setting->Upgrade->Yes. The new firmware must be a file named 'update.zip' placed in the root directory of a uSD card formatted with FAT32.

[nightgost]

https://infinit.io/_/j7zJqy4

some inside pics.

[pamaury]

Hi,
I have updated the wiki page http://www.rockbox.org/wiki/XDuooX3 to add the PCB scans. Using this and some binary reverse engineering, I have concluded that similarly to the Fiio X1, it uses a SLC NAND + mobile DDR RAM MCP. The RAM size is 64MiB and the NAND size is 128MB.

[XVortex]

Hi to all.
Hmm. It looks like a good platform for experiments on rockbox porting. But I do not see any uart pins on the board. Serial output is helpful for debugging.

[pamaury]

Hmm. It looks like a good platform for experiments on rockbox porting. But I do not see any uart pins on the board. Serial output is helpful for debugging.

MP3 players usually don't have any deug pins on retail versions.  The first part to a port is usually to make the screen work, to display some information. That's what I plan to do first anyway. I bought the player but I won't have it until another 10 to 15 days:

[staeff]

I'm very interested in this port. However, I have not much knowledge about embedded development.

Can I do anything to support this?

[pamaury]

Hi,
sorry I wanted to answer earlier. If you have no knowledge of embedded systems, it's gonna be tough for you to help with the development. However when (I hope) the port is in early stage, heavy testing and reporting problems is much appreciated.

[XVortex]

Is there any info about X3 GPIO's and OLED interface?

[pamaury]

Hi,
short answer: no.
So far I haven't played much with the X3. I sent an email to xDuoo to ask them for the source of the Linux Kernel, but I admit I am not overly confident.
Otherwise, the obvious way to go is to hack the firmware upgrade image to include a custom program (or possibly a remote shell) and basically poke in /sys or /proc to see what kind of information is there. I expect I'll have to do some reverse engineering of binary-only modules anyway but if I could avoid disassembling the kernel that would much better.
For the LCD, the nicest outcome would be to find the exact controller used and get the datasheet but this is not always possible, we'll see how it goes.
Another thing is that they are using uboot, so maybe they display some splash screen from uboot in which case some LCD code will be in uboot, which will be much easier to disassemble (again uboot is GPL but it's not clear if they will provide any source code).

[XVortex]

I've checked u-boot and I did not find any LCD/OLED code or any fonts/sprites in it.
This code is somewhere in internal kernel module.

[nightgost]

What kind of programmer do you guys need? C++ expert? C?

How about the answers from Xduoo? are they collaborating?

I'd like to apply for beta tester. also for paying some beers to those who can make this possible.