# Pin 'PA15' is not a valid pin name on mcu 'EBBCan' **URL:** \ **Category:** General Discussion\ **Created:** [January 31, 2023, 1:34am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319 "2023-01-31T01:34:54Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![mocho](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@mocho](https://klipper.discourse.group/u/mocho)\ **Post date:** [January 31, 2023, 1:34am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/1 "2023-01-31T01:34:54Z")
I’m trying to configure an existing BTT EBB36 can module from other printer in my new Voron 0.2 but klipper is not accepting my configuration With error “Pin ‘PA15’ is not a valid pin name on mcu ‘EBBCan’” Relevant Configuration: ```auto [mcu EBBCan] canbus_uuid: d05fdfdf7adb [tmc2209 extruder] #uart_pin: EBBCan: PA15 uart_pin: EBBCan:PA15 run_current: 0.600 # for LDO 36STH20-1004AHG stealthchop_threshold: 0 sense_resistor: 0.110 ``` I copyed this configuration from a working configuration in other printer and BTT EBB36 1.2 documentation says it’s the correct pin. > **[GitHub - bigtreetech/EBB](https://github.com/bigtreetech/EBB)** > > Contribute to bigtreetech/EBB development by creating an account on GitHub. ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [January 31, 2023, 1:38am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/2 "2023-01-31T01:38:02Z")
Missing a space between EBBCan:PA15 should be EBBCan: PA15 ---
**Author:** ![mocho](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@mocho](https://klipper.discourse.group/u/mocho)\ **Post date:** [January 31, 2023, 1:40am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/3 "2023-01-31T01:40:49Z")
tryed both ways, several times ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [January 31, 2023, 1:44am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/4 "2023-01-31T01:44:19Z")
Then the klipper firmware is not created for an STM32G0B1 ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [January 31, 2023, 7:45am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/5 "2023-01-31T07:45:31Z")
According to the github link in post #1, the UART pin is PA13, not PA15 ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [January 31, 2023, 11:59am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/6 "2023-01-31T11:59:33Z")
@EddyMI3D V1.0 PA13 V1.1 & V1.2 PA15 > **[BigTreeTech%20EBB36%20connections%20information.pdf](https://www.dropbox.com/s/ow06o2i523vmpa1/BigTreeTech%20EBB36%20connections%20information.pdf?dl=0)** ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [January 31, 2023, 12:04pm UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/7 "2023-01-31T12:04:42Z")
In deed, but that is another site… ---
**Author:** ![NAPCAL](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/napcal/32/1794_2.png) [@NAPCAL](https://klipper.discourse.group/u/NAPCAL)\ **Post date:** [January 31, 2023, 6:39pm UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/8 "2023-01-31T18:39:27Z")
Directly from BigTreeTech the manufacturer. More than likely the firmware was complied with the wrong STM32. The V1.1 & 1.2 have the G0B1. ---
**Author:** ![gaby\_64](https://avatars.discourse-cdn.com/v4/letter/g/ba8739/32.png) [@gaby\_64](https://klipper.discourse.group/u/gaby_64)\ **Post date:** [January 31, 2023, 6:54pm UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/9 "2023-01-31T18:54:06Z")
always post klipper.log, it tells the truth ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [February 7, 2023, 12:44pm UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/10 "2023-02-07T12:44:07Z")
A post was split to a new topic: [LGX-Lite extruder on Ebb42](https://klipper.discourse.group/t/lgx-lite-extruder-on-ebb42/6485) ---
**Author:** ![mocho](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@mocho](https://klipper.discourse.group/u/mocho)\ **Post date:** [February 9, 2023, 1:29am UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/11 "2023-02-09T01:29:41Z")
Possible, yes … But i Have done a roll back in klipper (like 50 commits or so) through kiauh and it worked. If it was a a wrong STM32 it should have not worked at all. Made an update now and all seems ok. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [December 6, 2024, 8:04pm UTC](https://klipper.discourse.group/t/pin-pa15-is-not-a-valid-pin-name-on-mcu-ebbcan/6319/12 "2024-12-06T20:04:08Z")