Blue Pill+ can controller (STM32F103CB)

[eiten]

Hello everyone,

I can't get the canbus controller to work on the blue pill+ (https://github.com/WeActStudio/BluePill-Plus). I tried it with the babbeling and the canopennode example. My overlay looks like this:

/ {
        model = "STM32 Minimum Development Board (Blue)";
        compatible = "stm32_min_dev_blue", "st,stm32f103c8";

        leds {
                led: led {
                        gpios = <&gpiob 2 GPIO_ACTIVE_LOW>;
                };
        };
        chosen {
                zephyr,canbus = &can1;
        };
        buttons {
                compatible = "gpio-keys";
                button0: button_0 {
                        gpios = <&gpioa 0 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>;
                        label = "User Key";
/*                        zephyr,code = <INPUT_KEY_0>;*/
                };
        };
        aliases {
                sw0 = &button0;
        };

};

&can1 {
        pinctrl-0 = <&can_rx_remap1_pb8 &can_tx_remap1_pb9>;
        pinctrl-names = "default";
        status = "okay";
};

For the canopennode, I use this build command: west build -b stm32_min_dev@blue -p -- -DBOARD_FLASH_RUNNER=jlink -DCONF_FILE="prj_no_storage.conf"

I get ENETUNREACH errors:

*** Booting Zephyr OS build v3.7.0-2072-gcba339a6f4e2 ***
[00:00:00.000,000] <dbg> canopen_driver: CO_CANmodule_init: rxSize = 13, txSize = 9
[00:00:00.000,000] <dbg> canopen_driver: CO_CANmodule_init: excessive number of concurrent CAN RX filters enabled (needs 13, 14 available)
[00:00:00.000,000] <inf> app: CANopen stack initialized
[00:00:00.000,000] <inf> app: Green LED not available
[00:00:00.000,000] <inf> app: Red LED not available
[00:00:00.010,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.020,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.040,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.050,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.070,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.081,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.092,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.102,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.113,000] <err> canopen_driver: failed to send CAN frame (err -114)
[00:00:00.124,000] <err> canopen_driver: failed to send CAN frame (err -114)

Any ideas?

Thanks, Edi

[nordicjm]

These boards are notorious for having bad quality (QA failure?) or completely counterfeit chips on. @henrikbrixandersen

[henrikbrixandersen]

I tried it with the babbeling and the canopennode example.

Please try it with the tests/drivers/can/api and tests/drivers/can/timing/ test suites first. If these work, try using a logic analyzer to see the CAN RX/TX signals between the CAN controller and the CAN transceiver (you do have a CAN transceiver attached and connected to a CAN bus, right - otherwise no CAN traffic will take place?).

[eiten]

So to report back... both blue pill and original nucleF108 work now... the problem was a partly defective transceiver...

Thank you all for your effort

[henrikbrixandersen]

Glad you found the issue!