Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

Elfving — Fri, 16 Aug 2024 12:47:27 GMT

Great! Glad to hear it! Sorry about the lack of responsiveness from us on this case.

Feel free to create a new ticket if anything else pops up, and hopefully the responsiveness will be better then.

Regards and have a good week-end!

Elfving

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Fri, 16 Aug 2024 12:33:50 GMT

hi there. yes. while i dont have the exact details, Sofia managed to get it working. As Tobjørn mentioned the issue was input voltage between the NRF and the CanBus Shield. so the solution if im not mistaken was to indivisually power both devices and use a voltage control to make sure the signals where on the expected numbers

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

Elfving — Fri, 16 Aug 2024 11:13:11 GMT

Hello Sofia,

Unfortunately Tobjørn won't have the time to continue the case, but I will take over.

I see its been 3 months since you last spoke. Has there any update on this case from your side?

Regards,

Elfving

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

smh02 — Fri, 31 May 2024 13:46:34 GMT

Hi Torbjørn

Don't worry, I appreciate your time and I'll be waiting for you when you get back. If I get a new result I will be commenting to you.

Regards

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Fri, 31 May 2024 13:14:50 GMT

Hi Sofia

Sorry for the missing response from my side. I see similar issues on my side, but unfortunately I haven't really had time to investigate it further. Next week I am on travel, so I will have to follow this up when I'm back in office the second week of June.

Again sorry for the delay, and if you discover anything interesting in the mean time please update the case.

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

smh02 — Thu, 30 May 2024 15:50:22 GMT

Hi ovrebekk , I was wondering if you could take a look at this ticket I made. I was finally able to send frames from my NRF to Arduino in normal mode, but when I try to recieve frames form Arduino to my NRF don't get anything.

(+) Recieve CAN BUS frames using Seeed CAN BUS Shield V2.0 & NRF52840DK - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

Everything seems to work using the logic shifter TXS0108E.

Thanks for your time! 🙂

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

smh02 — Fri, 24 May 2024 03:31:27 GMT

Hi everyone!

I would like to know if you were able to communicate with another device via CAN using normal mode?

I am working with the same board and the CAN BUS Seeed V2.0 shield so I followed the steps.

I included the overlay you mentioned and also did the 3.3V hack as you indicated. With this I was able to make the Loopback mode work without problems sending and receiving frames as you can see below:

[00:00:08.402,130] <inf> main: -------------------------
[00:00:08.402,160] <inf> main: Initializing CAN bus
[00:00:08.402,160] <inf> main: Asserting device ready.
[00:00:08.402,191] <inf> main: CAN: Device can@0 ready.
[00:00:08.402,191] <inf> main: -------------------------
[00:00:08.402,221] <inf> main: Enabling MODE LOOPBACK.
[00:00:08.402,221] <inf> main: MODE LOOPBACK.
[00:00:08.402,221] <inf> main: -------------------------
[00:00:08.402,252] <inf> main: Trying to set bitrate.
[00:00:08.402,557] <inf> main: Bitrate set.
[00:00:08.402,587] <inf> main: -------------------------
[00:00:08.402,587] <inf> main: Adding reception filter
[00:00:08.402,587] <inf> main: Before adding reception filter.
[00:00:08.402,618] <inf> main: RX filter added successfully. Filter ID: 0
[00:00:08.402,618] <inf> main: -------------------------
[00:00:08.402,618] <inf> main: Trying to start CAN.
[00:00:08.402,832] <inf> main: CAN started
[00:00:08.402,832] <inf> main: -------------------------
[00:00:08.402,832] <inf> main: Waiting for CAN frame
[00:00:09.402,923] <inf> main: Sending CAN frame with ID: 0x7df, DLC: 8
[00:00:09.403,228] <inf> main: CAN frame sent
[00:00:09.403,228] <inf> main: ** ** ** ** ** ** ** **
[00:00:09.403,808] <inf> main: Message sent successfully - Sender: Sender 1
[00:00:09.403,808] <inf> main: tx_callback executed
[00:00:11.403,320] <inf> main: Waiting for CAN frame
[00:00:12.403,472] <inf> main: Sending CAN frame with ID: 0x7df, DLC: 8
[00:00:12.403,747] <inf> main: CAN frame sent
[00:00:12.403,778] <inf> main: ** ** ** ** ** ** ** **
[00:00:12.404,296] <inf> main: Message sent successfully - Sender: Sender 1
[00:00:12.404,327] <inf> main: tx_callback executed

However, when I set the normal mode to receive or send frames I get the same error <err> main: Sending failed [-11] as you can see:

[00:00:08.434,112] <inf> main: -------------------------
[00:00:08.434,143] <inf> main: Initializing CAN bus
[00:00:08.434,143] <inf> main: Asserting device ready.
[00:00:08.434,173] <inf> main: CAN: Device can@0 ready.
[00:00:08.434,173] <inf> main: -------------------------
[00:00:08.434,204] <inf> main: Enabling MODE NORMAL.
[00:00:08.434,204] <inf> main: MODE NORMAL.
[00:00:08.434,204] <inf> main: -------------------------
[00:00:08.434,234] <inf> main: Trying to set bitrate.
[00:00:08.434,539] <inf> main: Bitrate set.
[00:00:08.434,570] <inf> main: -------------------------
[00:00:08.434,570] <inf> main: Adding reception filter
[00:00:08.434,570] <inf> main: Before adding reception filter.
[00:00:08.434,600] <inf> main: RX filter added successfully. Filter ID: 0
[00:00:08.434,600] <inf> main: -------------------------
[00:00:08.434,600] <inf> main: Trying to start CAN.
[00:00:08.434,814] <inf> main: CAN started
[00:00:08.434,814] <inf> main: -------------------------
[00:00:08.434,814] <inf> main: Waiting for CAN frame
[00:00:09.434,906] <inf> main: Sending CAN frame with ID: 0x7df, DLC: 8
[00:00:09.435,211] <inf> main: CAN frame sent
[00:00:09.435,211] <inf> main: ** ** ** ** ** ** ** **
[00:00:11.435,302] <inf> main: Waiting for CAN frame
[00:00:12.435,485] <inf> main: Sending CAN frame with ID: 0x7df, DLC: 8
[00:00:17.435,607] <err> main: Sending failed [-11]
[00:00:17.435,638] <inf> main: ** ** ** ** ** ** ** **
[00:00:19.435,729] <inf> main: Waiting for CAN frame
[00:00:20.435,913] <inf> main: Sending CAN frame with ID: 0x7df, DLC: 8
[00:00:25.436,035] <err> main: Sending failed [-11]
[00:00:25.436,065] <inf> main: ** ** ** ** ** ** ** **

This is the code that i'm using:

#include <zephyr/drivers/can.h>
#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(main);

void tx_callback(const struct device *dev, int error, void *user_data)
{
    char *sender = (char *)user_data;

    if (error != 0) {
        LOG_ERR("Sending failed [%d] - Sender: %s", error, sender);
    } else {
        LOG_INF("Message sent successfully - Sender: %s", sender);
    }
    LOG_INF("tx_callback executed");
}

int send_function(const struct device *can_dev)
{
    struct can_frame frame = {.flags = 0, .id = 0x7df, .dlc = 8, .data = {0x02, 0x01, 0x0c, 0x00, 0x00, 0x00, 0x00, 0x00}};

    LOG_INF("Sending CAN frame with ID: 0x%x, DLC: %d", frame.id, frame.dlc);

    return can_send(can_dev, &frame, K_MSEC(5000), tx_callback, "Sender 1");
}

void rx_callback_function(const struct device *dev, struct can_frame *frame, void *user_data)
{
    char *sender = (char *)user_data;

    LOG_INF("Received CAN frame - Sender: %s", sender);
    LOG_INF("ID: 0x%x, DLC: %d", frame->id, frame->dlc);
    LOG_HEXDUMP_INF(frame->data, frame->dlc, "Data: ");
}

int main(void)
{
    LOG_INF("CanBus-OBD2 samplev11");
    int ret;
    k_sleep(K_MSEC(8000));

    LOG_INF("-------------------------");

    LOG_INF("Initializing CAN bus");

    const struct device *const can_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_canbus));

    LOG_INF("Asserting device ready.");
    if (!device_is_ready(can_dev)) {
        LOG_ERR("CAN: Device %s not ready.", can_dev->name);
        return 0;
    }
    LOG_INF("CAN: Device %s ready.", can_dev->name);

    LOG_INF("-------------------------");

    LOG_INF("Enabling MODE LOOPBACK.");
    ret = can_set_mode(can_dev, CAN_MODE_LOOPBACK);
    if (ret != 0) {
        LOG_ERR("Error setting CAN mode [%d]", ret);
        return 0;
    }
    LOG_INF("MODE LOOPBACK.");

    LOG_INF("-------------------------");

    LOG_INF("Trying to set bitrate.");
    ret = can_set_bitrate(can_dev, 500000);
    if (ret != 0) {
        LOG_ERR("Error setting CAN bitrate [%d]", ret);
        return 0;
    }
    LOG_INF("Bitrate set.");

    LOG_INF("-------------------------");
    LOG_INF("Adding reception filter");

    const struct can_filter my_filter = {
        .flags = CAN_FILTER_DATA, .id = 0x7E8, .mask = CAN_STD_ID_MASK};
    int filter_id;

    char *callback_arg = "Callback argument";

    LOG_INF("Before adding reception filter.");
    filter_id = can_add_rx_filter(can_dev, rx_callback_function, callback_arg, &my_filter);
    if (filter_id >= 0) {
        LOG_INF("RX filter added successfully. Filter ID: %d", filter_id);
    } else {
        LOG_ERR("Failed to add RX filter. Error code: %d", filter_id);
    }
    LOG_INF("-------------------------");

    LOG_INF("Trying to start CAN.");
    ret = can_start(can_dev);
    if (ret != 0) {
        LOG_ERR("Error starting CAN controller [%d]", ret);
        return 0;
    }
    LOG_INF("CAN started");

    LOG_INF("-------------------------");

    while (1) {
        LOG_INF("Waiting for CAN frame");
        k_sleep(K_MSEC(1000));
        ret = send_function(can_dev);
        if (ret != 0) {
            LOG_ERR("Sending failed [%d]", ret);
        } else {
            LOG_INF("CAN frame sent");
        }
        LOG_INF("** ** ** ** ** ** ** **");
        k_sleep(K_MSEC(2000)); // Intervalo de 2 segundos entre envíos
    }

    return 0;
}

Just in case, this is my build configuration:

And my prj.config

CONFIG_POLL=y
CONFIG_CAN=y
CONFIG_SPI=y
CONFIG_CAN_MCP2515=y
CONFIG_CAN_INIT_PRIORITY=80
CONFIG_CAN_MAX_FILTER=5

CONFIG_SHELL=y
CONFIG_CAN_SHELL=y
CONFIG_DEVICE_SHELL=y

CONFIG_GPIO=y
CONFIG_STATS=y
CONFIG_STATS_NAMES=y
CONFIG_STATS_SHELL=y
CONFIG_CAN_STATS=y

CONFIG_RTT_CONSOLE=n

CONFIG_LOG=y
CONFIG_CAN_LOG_LEVEL_DBG=y
CONFIG_SPI_LOG_LEVEL_DBG=n

CONFIG_PRINTK=y
CONFIG_CONSOLE=y

Any ideas? I really don't know if I am missing a file to include in the construction of my application. Also I was wondering if I could include a logic level converter (TXS0108E) to verify if the reason why i can't communicate is due to the difference of voltages in the SPI communication.

I would be very grateful if you could help me :)

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Tue, 14 May 2024 13:55:06 GMT

Hi again

As it happens I had some available time and decided to run a quick test with the Seeed Can-bus v2 shield. As we discussed earlier the voltage is definitely incorrect, but the shield seems to work fine when I cut the 5v line and make a short between the 3V3 and 5V signals on the Shield.

With this hack I can get the counter sample to run without any apparent issues, at least in the default loopback mode.

I use the following overlay:

&arduino_spi {
	status = "okay";
	cs-gpios = <&arduino_header 15 GPIO_ACTIVE_LOW>; /* D9 */

	mcp2515_dfrobot_can_bus_v2_0: can@0 {
		compatible = "microchip,mcp2515";
		spi-max-frequency = <1000000>;
		int-gpios = <&arduino_header 8 0x1>; /* D2 */
		status = "okay";
		reg = <0x0>;
		osc-freq = <16000000>;
		bus-speed = <125000>;
		sample-point = <875>;

		can-transceiver {
			max-bitrate = <1000000>;
		};
	};
};

/ {
	chosen {
		zephyr,canbus = &mcp2515_dfrobot_can_bus_v2_0;
	};
};

My 3.3V hack looks like this:

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Tue, 14 May 2024 08:19:43 GMT

Sounds good, please reach out if you don't hear anything by that time 🙂

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Mon, 13 May 2024 15:22:31 GMT

thanks a lot. im subscribed to the thread but ill ping back :D

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Mon, 13 May 2024 13:19:46 GMT

Sorry for not getting back to you. Even after so long in Nordic I keep overestimating the time I have available for these kinds of things....

My next couple of weeks are pretty packed, but I will set aside some time for evaluating this the last month of May. I can't promise I will get to the bottom of it in the time available, but I will give it a go at least. I will send you an update once I start on the tests.

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Mon, 06 May 2024 19:36:52 GMT

hi there... any updates?

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Tue, 31 Oct 2023 10:11:08 GMT

Ok, thanks for the update. I will get back to you next week then, once I have had some time to take a look.

Regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Mon, 30 Oct 2023 11:57:41 GMT

No really. to be honest i stopped trying because my results were not the same and to me it seems its related to spi communication and i dont really know how to properly debug it.

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Mon, 30 Oct 2023 09:07:22 GMT

Fingers crossed I will be able to reproduce the issue, and find a solution ;)

Did you discover anything else in the mean time that might be helpful to know?

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Fri, 27 Oct 2023 16:12:03 GMT

Almost there then :)

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Fri, 27 Oct 2023 09:05:12 GMT

By coincidence I just received them yesterday! Not sure why it took so long...

Unfortunately I am stuck with another project until the end of next week, so I won't be able to look into this until the week of November 5th.

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Thu, 26 Oct 2023 18:44:44 GMT

hi there! did you had any luck with your shields?

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Tue, 29 Aug 2023 08:15:32 GMT

No worries, just let me know when you have been able to test it.

I am still waiting for the shields I ordered, so there's nothing new to report from my side.

Regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Mon, 28 Aug 2023 23:04:08 GMT

I haven forgotten about this. ill try to test it tomorrow and report back.

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Mon, 21 Aug 2023 10:58:59 GMT

Hi Efrain

I ordered a couple of the Seeed Studio CAN shields, so no need for you to order anything 😉

It is interesting to see that you got something working finally.

The sending failed -11 error is probably coming from here, which indicates that something is wrong with the TX callback since the tx_sem semaphore should be given in the tx_done callback here.

Could you add some logging in your tx_callback(..) function to verify that this function is actually called after you call can_send(..) ?

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Thu, 17 Aug 2023 18:52:46 GMT

hI Torbjørn

I think it could be awsome if you get a can shield (please le me know which one so that i can order the same :) ).

Now with that said i have made some "progress"

Since there was soo much code in the "sample" i cut it down to a simpler one:

//Pretty standar code to recieve frames and send an OBD2 CanFrame

/*
 * Copyright (c)
 *
 * SPDX-License-Identifier: Apache-2.0
 */

#include <zephyr/drivers/can.h>
#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(main);

void tx_callback(const struct device *dev, int error, void *user_data)
{
	char *sender = (char *)user_data;

	if (error != 0) {
		LOG_ERR("Sending failed [%d] - Sender: %s", error, sender);
	}
}

int send_function(const struct device *can_dev)
{
	struct can_frame frame = {.flags = 0, .id = 0x7df, .dlc = 8, .data = {0x02, 0x01, 0x0c}};

	// frame.data[0] = 1;
	// frame.data[1] = 2;

	return can_send(can_dev, &frame, K_MSEC(2000), tx_callback, "Sender 1");
}

void rx_callback_function(const struct device *dev, struct can_frame *frame, void *user_data)
{
	char *sender = (char *)user_data;

	LOG_INF("ID: 0x%x\n", frame->id);
	printk("Received CAN frame\nSender: %s\n", sender);
	printk("ID: 0x%x\n", frame->id);
	printk("DLC: %d\n", frame->dlc);
	printk("Data: ");
	printk("0x%x ", frame->data[0]);
	printk("0x%x ", frame->data[1]);
	printk("0x%x ", frame->data[2]);
	printk("0x%x ", frame->data[3]);
	printk("0x%x ", frame->data[4]);
	printk("0x%x ", frame->data[5]);
	printk("0x%x ", frame->data[6]);
	printk("0x%x ", frame->data[7]);
	printk("\n");
}

int main(void)
{
	LOG_INF("CanBus-OBD2 samplev11");
	int ret;
	k_sleep(K_MSEC(8000));

	const struct device *const can_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_canbus));

	LOG_INF("Asserting device ready.");
	if (!device_is_ready(can_dev)) {
		LOG_ERR("CAN: Device %s not ready.", can_dev->name);
		return 0;
	}
	LOG_INF("CAN: Device %s ready.", can_dev->name);

	LOG_INF("Enabling MODE NORMAL.");
	ret = can_set_mode(can_dev, CAN_MODE_NORMAL);
	if (ret != 0) {
		LOG_ERR("Error setting CAN mode [%d]", ret);
		return 0;
	}
	LOG_INF("MODE NORMAL Enabled.");

	LOG_INF("Trying to set bitrate.");
	ret = can_set_bitrate(can_dev, 500000);
	if (ret != 0) {
		LOG_ERR("Error setting CAN bitrate [%d]", ret);
		return 0;
	}
	LOG_INF("Set bitrate.");

	LOG_INF("Trying to start CAN.");
	ret = can_stop(can_dev);
	if (ret != 0) {
		LOG_ERR("Error stop CAN controller [%d]", ret);
		// return 0;
	}
	LOG_INF("CAN stopped [%d]", ret);

	LOG_INF("Trying to start can.");
	ret = can_start(can_dev);
	if (ret != 0) {
		LOG_ERR("Error starting CAN controller [%d]", ret);
		return 0;
	}
	LOG_INF("CAN started");

	const struct can_filter my_filter = {
		.flags = CAN_FILTER_DATA, .id = 0x7E8, .mask = CAN_STD_ID_MASK};
	int filter_id;

	char *callback_arg = "Callback argument";

	filter_id = can_add_rx_filter(can_dev, rx_callback_function, callback_arg, &my_filter);
	if (filter_id < 0) {
		LOG_ERR("Unable to add rx filter [%d]", filter_id);
	}

	printk("Filter ID: %d\n", filter_id);

	while (1) {
		LOG_INF("Waiting for CAN frame");
		k_sleep(K_MSEC(1000));
		LOG_INF("Sending CAN frame");
		ret = send_function(can_dev);
		if (ret != 0) {
			LOG_ERR("Sending failed [%d]", ret);
		} else {
			LOG_INF("CAN frame sent");
		}
	}
}

Now (both Shields The "seeed" and the "keystudio" seem to "boot up"

And i get the following log:

[00:00:00.251,617] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000aca8 - rx_bufs (nil) - 1
[00:00:00.251,617] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac9c (1), current_rx (nil) (0), tx buf/len 0x2000ac98/1, rx buf/len (nil)/0
[00:00:00.251,678] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.251,708] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.251,800] <dbg> can_mcp2515: mcp2515_init: Presc: 4, BS1: 7, BS2: 2
[00:00:00.251,800] <dbg> can_mcp2515: mcp2515_init: Sample-point err : 0
[00:00:00.252,044] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac48 - rx_bufs (nil) - 1
[00:00:00.252,075] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac50 (2), current_rx (nil) (0), tx buf/len 0x2000ac40/2, rx buf/len (nil)/0
[00:00:00.252,136] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0x2000ac44/4
[00:00:00.252,197] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.252,197] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.252,227] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac30 - rx_bufs (nil) - 1
[00:00:00.252,258] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac28 (1), current_rx (nil) (0), tx buf/len 0x2000ac24/4, rx buf/len (nil)/0
[00:00:00.252,319] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.252,349] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.252,380] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac30 - rx_bufs (nil) - 1
[00:00:00.252,410] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac28 (1), current_rx (nil) (0), tx buf/len 0x2000ac24/4, rx buf/len (nil)/0
[00:00:00.252,471] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.252,471] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
*** Booting Zephyr OS build v3.3.99-ncs1 ***
[00:00:00.252,563] <inf> main: CanBus-OBD2 samplev11
[00:00:08.252,624] <inf> main: Asserting device ready.
[00:00:08.252,685] <inf> main: CAN: Device can@0 ready.
[00:00:08.252,685] <inf> main: Enabling MODE NORMAL.
[00:00:08.252,716] <inf> main: MODE NORMAL Enabled.
[00:00:08.252,716] <inf> main: Trying to set bitrate.
[00:00:08.252,746] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac60 - rx_bufs (nil) - 1
[00:00:08.252,777] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac68 (2), current_rx (nil) (0), tx buf/len 0x2000ac58/2, rx buf/len (nil)/0
[00:00:08.252,838] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0x2000ac5c/4
[00:00:08.252,899] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:08.252,899] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:08.252,960] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac48 - rx_bufs (nil) - 1
[00:00:08.252,990] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac40 (1), current_rx (nil) (0), tx buf/len 0x2000ac3c/4, rx buf/len (nil)/0
[00:00:08.253,051] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:08.253,051] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:08.253,082] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac48 - rx_bufs (nil) - 1
[00:00:08.253,112] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac40 (1), current_rx (nil) (0), tx buf/len 0x2000ac3c/4, rx buf/len (nil)/0
[00:00:08.253,173] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:08.253,204] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:08.253,234] <inf> main: Set bitrate.
[00:00:08.253,234] <inf> main: Trying to start CAN.
[00:00:08.253,265] <err> main: Error stop CAN controller [-120]
[00:00:08.253,265] <inf> main: CAN stopped [-120]
[00:00:08.253,295] <inf> main: Trying to start can.
[00:00:08.253,295] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac50 - rx_bufs (nil) - 1
[00:00:08.253,326] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac48 (1), current_rx (nil) (0), tx buf/len 0x2000ac44/4, rx buf/len (nil)/0
[00:00:08.253,387] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:08.253,417] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:08.253,448] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac20 - rx_bufs 0x2000ac28 - 1
[00:00:08.253,479] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac30 (2), current_rx 0x2000ac40 (2), tx buf/len 0x2000ac1c/2, rx buf/len (nil)/2
[00:00:08.253,509] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/1
[00:00:08.253,540] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x2000ac67/1
[00:00:08.253,570] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:08.253,570] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:08.253,601] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:08.253,631] <inf> main: CAN started
Filter ID: 0
[00:00:08.253,662] <inf> main: Waiting for CAN frame
[00:00:09.253,753] <inf> main: Sending CAN frame
[00:00:09.253,814] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac40 - rx_bufs (nil) - 1
[00:00:09.253,814] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac58 (2), current_rx (nil) (0), tx buf/len 0x2000ac3c/1, rx buf/len (nil)/0
[00:00:09.253,875] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0x2000ac48/13
[00:00:09.254,028] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:09.254,028] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:09.254,089] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x2000ac58 - rx_bufs (nil) - 1
[00:00:09.254,089] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x2000ac40 (1), current_rx (nil) (0), tx buf/len 0x2000ac3c/1, rx buf/len (nil)/0
[00:00:09.254,150] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:09.254,180] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:09.254,211] <inf> main: CAN frame sent
[00:00:09.254,211] <inf> main: Waiting for CAN frame
[00:00:10.254,302] <inf> main: Sending CAN frame
[00:00:12.254,425] <err> main: Sending failed [-11]
[00:00:12.254,455] <inf> main: Waiting for CAN frame
[00:00:13.254,608] <inf> main: Sending CAN frame
[00:00:15.254,699] <err> main: Sending failed [-11]
[00:00:15.254,730] <inf> main: Waiting for CAN frame
[00:00:16.254,882] <inf> main: Sending CAN frame
[00:00:18.254,974] <err> main: Sending failed [-11]

Any ideas?

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Wed, 16 Aug 2023 08:03:37 GMT

Hi Efrain

If there is no working communication between the nRF device and the MCP2515 it makes sense that the log output would be the same. It seems the new shield is also using 5V supply.

I think it is hard to debug this further without the ability to scope the SPI lines, and some way of adjusting the supply voltage on the CAN shield in order to be compatible with the nRF device.

Like I said I am happy to order a shield and do some testing on my own, but this will take some time.

Best regards
Torbjørn

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ejromero2 — Tue, 15 Aug 2023 19:12:25 GMT

Hi!

So i got my new shield. i got the Keystudio_ks0411. - KS0411 keyestudio CAN-BUS Shield - Keyestudio Wiki

But... im getting exactly the same answer than the Seeed shield.

uart:~$ Error starting CAN control--- 334 messages dropped ---
[00:00:00.528,076] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
--- 78 messages dropped ---
[00:00:00.528,259] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x20004438 - rx_bufs 0x20004440 - 1
[00:00:00.528,289] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x20004448 (2), current_rx 0x20004458 (2), tx buf/len 0x20004434/2, rx buf/len (nil)/2
[00:00:00.528,350] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/1
[00:00:00.528,381] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x2000447f/1
[00:00:00.528,411] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.528,442] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.528,472] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.528,625] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x20004438 - rx_bufs 0x20004440 - 1
[00:00:00.528,656] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x20004448 (2), current_rx 0x20004458 (2), tx buf/len 0x20004434/2, rx buf/len (nil)/2
[00:00:00.528,717] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/1
[00:00:00.528,747] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x2000447f/1
[00:00:00.528,778] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.528,808] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.528,839] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.529,022] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x20004438 - rx_bufs 0x20004440 - 1
[00:00:00.529,052] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x20004448 (2), current_rx 0x20004458 (2), tx buf/len 0x20004434/2, rx buf/len (nil)/2
[00:00:00.529,113] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/1
[00:00:00.529,144] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x2000447f/1
[00:00:00.529,174] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.529,205] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.529,235] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.529,266] <err> can_mcp2515: Timeout trying to set MCP2515 operation mode
[00:00:00.529,296] <err> can_mcp2515: Failed to set the mode [-5]

RE: Running CAN-BUS Sample with different shield (NRF52840DK & Seeed CAN BUS Shield V2.0)

ovrebekk — Fri, 11 Aug 2023 06:40:39 GMT

Hi Efrain

Sounds good, I will wait for your report then. I am guessing you will have more success with the supported shields.

Good luck 🙂

Best regards
Torbjørn