Provide Pinout for the module

[StoneColdCrazy]

In the current version it is not apparent to what extent the CB1 is compatible with a CM4. Many functions are not possible (as an example the CSI port). By providing the pinout and the associated functions, technical incompatibilities can be derived more quickly. I have not been able to find any information on this so far.

With the provision, many questions would explain themselves.

[emesix]

How do you know that the SPI bus is not connected to the "Header" ?
We are complaining that the linux distrobution is missing SPI support. If that support is working then we can check the SPI wiring to the header.

[StoneColdCrazy]

I don't know that SPI has not been released, but as I said, there are no pinout descriptions that could help enormously. There are simply too many differences between CB1 and CM4.

Examples are among others the above mentioned PCIE on the CM4, since the H616 does not give this out of the chip, this will probably not be available. However, there is quite a bit the other way around. For example, the H616 has multiple USB outputs, but this may not be mapped on the header.

My point with the pinout is that this board is a good alternative to a CM4 in several areas aside from 3D printing. However, it should also be clear which pins go to the header here. Also this would help enormously to create own distributions, if the hardware would be known among other things by schematics.

[looxonline]

A pinout should be coming soon.

[ghent360]

Yes please pinout and more hardware details. I see there are some debug UART pads on the CB1, please document.

[emersonsc]

A pinout should be coming soon.

Its been over a month... where is it? Why hasnt Biqu/BTT released how THEY got input shaper working, since they claim this combo is compatible. I have a Manta 8 with a CB1 and unless i use the orange pi image and someone elses walkthrough I cant actually use an adxl and input shaper.

[looxonline]

A pinout should be coming soon.

Its been over a month... where is it? Why hasnt Biqu/BTT released how THEY got input shaper working, since they claim this combo is compatible. I have a Manta 8 with a CB1 and unless i use the orange pi image and someone elses walkthrough I cant actually use an adxl and input shaper.

Input shaper just works as long as you install the extra packages needed (as per the klipper guide) and use python 3. There is no, zilch, zero, nada secret sauce. Just specify the pins in the config and go...

[emersonsc]

A pinout should be coming soon.

Its been over a month... where is it? Why hasnt Biqu/BTT released how THEY got input shaper working, since they claim this combo is compatible. I have a Manta 8 with a CB1 and unless i use the orange pi image and someone elses walkthrough I cant actually use an adxl and input shaper.

Input shaper just works as long as you install the extra packages needed (as per the klipper guide) and use python 3. There is no, zilch, zero, nada secret sauce. Just specify the pins in the config and go...

Again... Where is the pin out? It was supposed to be provided. What's the pin out using a CB1?

[emersonsc]

Also, where is the documentation on how to set up the adxl on the Manta and cb1 board? SPI header on the MCU or GPIO pins for the CB1? If so what's the pin out for the CB1 GPIO pins?

[Michelinu]

After 6 weeks the GPIO PINOUT for the CB1 is still a mistery for BTT/Biqu. The CB1 is currently useless for whom needs GPIO pins.

I did some research and discovered that in the M4P user manual there's a PINOUT for the CB1, here it is.

You have to take the name after the underscore for the PIN you need. Then use this table https://wiki.pine64.org/wiki/SOPine_GPIO_Alternate_Functions_Table to get the GPIO<number>.
I tried with some "PC" pins and it seems to work

[emersonsc]

After 6 weeks the GPIO PINOUT for the CB1 is still a mistery for BTT/Biqu. The CB1 is currently useless for whom needs GPIO pins.

I did some research and discovered that in the M4P user manual there's a PINOUT for the CB1, here it is.

You have to take the name after the underscore for the PIN you need. Then use this table https://wiki.pine64.org/wiki/SOPine_GPIO_Alternate_Functions_Table to get the GPIO<number>. I tried with some "PC" pins and it seems to work

It's sad no one here from BTT can bother to comment with something so simple. They designed the d*** board why is it so hard for them to release the information so we can utilize what they made and we paid for?

I also love the crickets on the adxl. We keep getting told it works... But no one wants to say HOW. No explanation, no walk through, no documentation. Just "it does work"

[Michelinu]

After 6 weeks the GPIO PINOUT for the CB1 is still a mistery for BTT/Biqu. The CB1 is currently useless for whom needs GPIO pins.
I did some research and discovered that in the M4P user manual there's a PINOUT for the CB1, here it is.
You have to take the name after the underscore for the PIN you need. Then use this table https://wiki.pine64.org/wiki/SOPine_GPIO_Alternate_Functions_Table to get the GPIO<number>. I tried with some "PC" pins and it seems to work

It's sad no one here from BTT can bother to comment with something so simple. They designed the d*** board why is it so hard for them to release the information so we can utilize what they made and we paid for?

I also love the crickets on the adxl. We keep getting told it works... But no one wants to say HOW. No explanation, no walk through, no documentation. Just "it does work"

As far as concerns ADXL345 I tried to configure it by using the informations provided by stas2z here: #9 (comment)
Since his wiring scheme looks a bit messy, I made a new one

I'm still waiting to receive my ADXL so I can't test it to confirm that it works. I'm using latest version of CB1 official firmware (2.2.0) and I don't get any error causing Klipper to not boot. Theorically by wiring it correctly, it should work

[emersonsc]

As far as concerns ADXL345 I tried to configure it by using the informations provided by stas2z here: #9 (comment) Since his wiring scheme looks a bit messy, I made a new one

I'm still waiting to receive my ADXL so I can't test it to confirm that it works. I'm using latest version of CB1 official firmware (2.2.0) and I don't get any error causing Klipper to not boot. Theorically by wiring it correctly, it should work

I saw those steps, but it requires the use of an image from another manufacturer. BTT claims it works with theirs, but had provided nothing as far as HOW.

Did you follow everyone one of those steps to make it work with the BTT image? If you had to change things, can you provide your steps?

[Michelinu]

As far as concerns ADXL345 I tried to configure it by using the informations provided by stas2z here: #9 (comment) Since his wiring scheme looks a bit messy, I made a new one
I'm still waiting to receive my ADXL so I can't test it to confirm that it works. I'm using latest version of CB1 official firmware (2.2.0) and I don't get any error causing Klipper to not boot. Theorically by wiring it correctly, it should work

I saw those steps, but it requires the use of an image from another manufacturer. BTT claims it works with theirs, but had provided nothing as far as HOW.

Did you follow everyone one of those steps to make it work with the BTT image? If you had to change things, can you provide your steps?

He stated that it got it working by using his custom OrangePi image for CB1 - he doesn't exclude that it might work also with the latest official images from BTT. If you flash the "Klipper" image all the required libraries, NumPy and the linux MCU host are already installed. If you are using the "minimal" image you have to install them by following the Klipper documentation: https://www.klipper3d.org/Measuring_Resonances.html

Since the raspi-config command is not available, I added the following entries in my /boot/BoardEnv.txt to enable SPI:

overlays=spi-spidev
param_spidev_spi_bus=1
param_spidev_spi_cs=1
param_spidev_max_freq=1000000

Running ls -1 /dev/spidev* I get /dev/spidev1.1 as output - so I imagine that it did the trick.
Trying using the GPIO74 as OUTPUT_PIN and testing it with a multimeter, I have the confirmation that pin n.15 in the 40-pin header (that normally is GPIO22 - the cyan wire in my wiring diagram) is GPIO74 in CB1.

Here's my current adxl345.cfg file (that you can #include in your printer.cfg or paste the content directly in that):

[mcu rpi]
serial: /tmp/klipper_host_mcu

[adxl345]
cs_pin: rpi:gpiochip0/gpio74
spi_bus: spidev1.1

[resonance_tester]
accel_chip: adxl345
probe_points:
  100, 100, 20

Running sudo cat /sys/kernel/debug/gpio displays that gpio-74 is used by Klipper.

As said before, I still didn't get my ADXL345 so I can't confirm it's really working

[Borillion]

GPIO Access Denied #44

Thank you this is very helpful :)

[Borillion]

[Michelinu]

"I can not get it for you" -> "We can make a pinout diagram/scheme/table since we "developed" it. We did our job and you already bought it, so we are not interested at using our time to solve your problem/doubt. Do it by yourself, if you can".

Since the company is not interested at publishing further documentation about the CB1, I created a thread that regroup all the info already published by some users and the ones I discovered: #47

[looxonline]

"I can not get it for you" -> "We can make a pinout diagram/scheme/table since we "developed" it. We did our job and you already bought it, so we are not interested at using our time to solve your problem/doubt. Do it by yourself, if you can".

Since the company is not interested at publishing further documentation about the CB1, I created a thread that regroup all the info already published by some users and the ones I discovered: #47

I have been discussing this with them. I am not sure why they have not released it yet. They should have. I have all of the data and will try to put something together soon. In the meanwhile, if anyone has a specific question about a pin then they can ask me.

[Borillion]

"I can not get it for you" -> "We can make a pinout diagram/scheme/table since we "developed" it. We did our job and you already bought it, so we are not interested at using our time to solve your problem/doubt. Do it by yourself, if you can".
Since the company is not interested at publishing further documentation about the CB1, I created a thread that regroup all the info already published by some users and the ones I discovered: #47

I have been discussing this with them. I am not sure why they have not released it yet. They should have. I have all of the data and will try to put something together soon. In the meanwhile, if anyone has a specific question about a pin then they can ask me.

Not much to go by but started mapping out some of what I can find from the datasheets of the different carrier boards into a csv.

https://github.com/Borillion/CB1/blob/main/CM4toCB1_GPIOMapping.csv

[emersonsc]

A pinout should be coming soon.

Where's the pinout? Its been over 3 months.

[mutlubasdas]

As far as concerns ADXL345 I tried to configure it by using the informations provided by stas2z here: #9 (comment) Since his wiring scheme looks a bit messy, I made a new one
I'm still waiting to receive my ADXL so I can't test it to confirm that it works. I'm using latest version of CB1 official firmware (2.2.0) and I don't get any error causing Klipper to not boot. Theorically by wiring it correctly, it should work

I saw those steps, but it requires the use of an image from another manufacturer. BTT claims it works with theirs, but had provided nothing as far as HOW.
Did you follow everyone one of those steps to make it work with the BTT image? If you had to change things, can you provide your steps?

He stated that it got it working by using his custom OrangePi image for CB1 - he doesn't exclude that it might work also with the latest official images from BTT. If you flash the "Klipper" image all the required libraries, NumPy and the linux MCU host are already installed. If you are using the "minimal" image you have to install them by following the Klipper documentation: https://www.klipper3d.org/Measuring_Resonances.html

Since the raspi-config command is not available, I added the following entries in my /boot/BoardEnv.txt to enable SPI:

overlays=spi-spidev
param_spidev_spi_bus=1
param_spidev_spi_cs=1
param_spidev_max_freq=1000000

Running ls -1 /dev/spidev* I get /dev/spidev1.1 as output - so I imagine that it did the trick. Trying using the GPIO74 as OUTPUT_PIN and testing it with a multimeter, I have the confirmation that pin n.15 in the 40-pin header (that normally is GPIO22 - the cyan wire in my wiring diagram) is GPIO74 in CB1.

Here's my current adxl345.cfg file (that you can #include in your printer.cfg or paste the content directly in that):

[mcu rpi]
serial: /tmp/klipper_host_mcu

[adxl345]
cs_pin: rpi:gpiochip0/gpio74
spi_bus: spidev1.1

[resonance_tester]
accel_chip: adxl345
probe_points:
  100, 100, 20

Running sudo cat /sys/kernel/debug/gpio displays that gpio-74 is used by Klipper.

As said before, I still didn't get my ADXL345 so I can't confirm it's really working

This works!

Thank you so much!!

[frutabruta]

The pinout has been released: Link

[Borillion]

@frutabruta thank you. @bigtreetech this is so very much appreciated, and was a long time coming. <3

[looxonline]

@frutabruta thank you. @bigtreetech this is so very much appreciated, and was a long time coming. <3

Schematic is also up on the official github. You'll see quicker turnaround on the pinout in the future. Schematic will have a delay of a few months to prevent competitors from copying design points.

[x2ocoder]

@looxonline Consider adjusting the policy for releasing pinouts.

If the team released pages 9 and 10 documenting A1-100 and B101-200, it would have made the module much easier to use by the community without disclosing any internal wiring "secrets".

By hiding the entire schematic, the community was not able to understand how to implement projects outside the source code that your team distributed. This really limited the usefulness of your product for months.

Limiting usefulness is not a benefit to anyone.

[looxonline]

@looxonline Consider adjusting the policy for releasing pinouts.

If the team released pages 9 and 10 documenting A1-100 and B101-200, it would have made the module much easier to use by the community without disclosing any internal wiring "secrets".

By hiding the entire schematic, the community was not able to understand how to implement projects outside the source code that your team distributed. This really limited the usefulness of your product for months.

Limiting usefulness is not a benefit to anyone.

Absolutely agreed. I only started working for BTT three days ago but this is something that I am going to be like a dog with a bone. I will hang onto it with each release to make sure that it happens. The full pinout will be released in a well crafted manual for each subsequent SBC product from now on...and there are some awesome SBC products in the pipeline ;)

[x2ocoder]

Congratulations on your new position!

As a recommendation for the other boards, clarify which pins are for the MCU vs the CB1.

Exposed Names for user-side pins without knowing which chips they go to make schematics misleading.
Here's an example: bigtreetech/Manta-M4P#8

[looxonline]

Congratulations on your new position!

As a recommendation for the other boards, clarify which pins are for the MCU vs the CB1.

Exposed Names for user-side pins without knowing which chips they go to make schematics misleading. Here's an example: bigtreetech/Manta-M4P#8

Also a good point. This is done well on the 40 pin header but not elsewhere in the sch. Will work on that.

[x2ocoder]

Here's an example of where a 40 Pin Header Pinout should be reclarified/rechecked since CB1-PG7 does not seem to actually go to the 40 Pin Header as documented.

bigtreetech/Manta-M4P#7

[Jckf]

If anyone else ends up here looking for the CB1 GPIO numbers; here's a spreadsheet I put together using the information @Michelinu posted above.