Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help: Ingenic XBurst2 X2000 SoC series USB serial port connetion #1

Open
andreoliveirapguerra opened this issue Sep 21, 2023 · 6 comments

Comments

@andreoliveirapguerra
Copy link

I saw that there is a sand clock on the X2000 USB serial port, does it means it does not have those capabilities?

Context: I own a Creality K1 3d printer, which uses an modified board that runs on the X2000 and the ingenic linux kernel. But while trying to get an serial connetion, I cannot seem to be able to get the board and kernel to recognize the other USB.
the lsusb command returns to me:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and the ls /dev/tty* command outputs this:

/dev/tty    /dev/tty15  /dev/tty22  /dev/tty3   /dev/tty37  /dev/tty44  /dev/tty51  /dev/tty59  /dev/tty9
/dev/tty0   /dev/tty16  /dev/tty23  /dev/tty30  /dev/tty38  /dev/tty45  /dev/tty52  /dev/tty6   /dev/ttyS0
/dev/tty1   /dev/tty17  /dev/tty24  /dev/tty31  /dev/tty39  /dev/tty46  /dev/tty53  /dev/tty60  /dev/ttyS1
/dev/tty10  /dev/tty18  /dev/tty25  /dev/tty32  /dev/tty4   /dev/tty47  /dev/tty54  /dev/tty61  /dev/ttyS2
/dev/tty11  /dev/tty19  /dev/tty26  /dev/tty33  /dev/tty40  /dev/tty48  /dev/tty55  /dev/tty62  /dev/ttyS3
/dev/tty12  /dev/tty2   /dev/tty27  /dev/tty34  /dev/tty41  /dev/tty49  /dev/tty56  /dev/tty63  /dev/ttyS5
/dev/tty13  /dev/tty20  /dev/tty28  /dev/tty35  /dev/tty42  /dev/tty5   /dev/tty57  /dev/tty7   /dev/ttyS7
/dev/tty14  /dev/tty21  /dev/tty29  /dev/tty36  /dev/tty43  /dev/tty50  /dev/tty58  /dev/tty8   /dev/ttyS9

The build roots for this were:
ftp://ftp.ingenic.com.cn/DevSupport/X2000/X2000/01_SW/07_kernel4.4.94_x2000-sdk_v8.0-20220125 ftp://ftp.ingenic.com.cn/DevSupport/X2000/X2000/01_SW/01_Buildroot_dl

The modded creality board from their official github here:
https://github.com/CrealityOfficial/K1_Series_Annex/blob/main/pin%20out/motherboard-en.PNG

@ReimuNotMoe
Copy link
Member

What do you mean by sand clock?

Sorry, but we are unable to give support for devices that use Ingenic's own outdated 4.4 kernel.

@andreoliveirapguerra
Copy link
Author

andreoliveirapguerra commented Sep 22, 2023

I see, than do you know how could I perhaps use this kernel on the board? Creality offers tools for flashing the image, so if perhaps could flash this ingenic comunity board, could I perhaps get it to recognize USB devices properly? Or this Ingenic comunity does not have image for the XBurst2 X2000?

My final objective is simply to obtain serial uart connection from the board, so I can connect it to an rasp that will act as the main MCU and give commands to the X2000. To be able to run octoprint on the printer.

@ClassicOldSong
Copy link
Member

We currently haven't add support for the X2000. You may wait a few months later since we're planning on adding support for the X2000 but we might not be able to provide help for that specific board.

@ClassicOldSong
Copy link
Member

Also X2000 is very capable, there's totally no need for a RPI as a host.

@X-Ryl669
Copy link

X-Ryl669 commented Apr 3, 2024

Also, even if you had a fully working kernel, you won't have the device tree used in Creality's screen module, nor the pinout, nor the GUI software, nor all the additional stuff Creality made to their kernel/drivers for this board to work. I think, unless Creality deliver the source code for their module, you're struck. You might be able to compile Octoprint on Ingenic's MIPS ISA and run it directly on the board itself.

It's very likely the printer motherboard already discuss on the plain serial line (/dev/ttyS something and not USB), so once you've installled octoprint or moonraker, you'll be able to control it.

@ReimuNotMoe
Copy link
Member

It's quite easy to dump the device tree in use from /proc/device-tree/. If the kernel is too old, one can always dump the GPIO pinmux registers using busybox devmem <reg>. So no problem for the pinout part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants