Attachments (0)
Nordic Case Info
  • Case ID: 233614
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

zephyr: device tree overlay is very confusing | error: 'DT_INST_0_MICROCHIP_MCP2515_SPI_MAX_FREQUENCY' undeclared here

a3p

i'm trying to get samples/drivers/CAN working with the nrf52

apparantly you need to enable CAN explicitly in menuconfig, which is already confusing because   prj.conf has CONFIG_CAN=y , but by default all i get is "CAN: Device driver not found."

after enabling the driver, the device tree overlay doesnt seem to be compiled in

Fullscreen
1
can_mcp2515.c:610:14: error: 'DT_INST_0_MICROCHIP_MCP2515_BUS_NAME' undeclared here (not in a function)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

however, the mcp2515-dts.overlay file seems broken, because if i add it via

set(DTC_OVERLAY_FILE "${CMAKE_CURRENT_SOURCE_DIR}/mcp2515-dts.overlay")

in CMakeLists.txt  i get:

Fullscreen
1
nrf52_pca10040.dts.pre.tmp:179.22-187.5: ERROR (phandle_references): /soc/spi@40004000: Reference to non-existent node or label "gpioa"
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

nrf's are apparantly called gpio0 instead of gpioa, so i changed that, but that just leads to an even more cryptic error

Fullscreen
1
device tree error: zephyr/dts/bindings/can/microchip,mcp2515.yaml (in 'reg'): 'category' from !included file overwritten ('required' replaced with 'optional')
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

so i edited scripts/dts/edtlib.py and just uncommented that check, which leads me to:

Fullscreen
1
device tree error: 'sjw' is marked as required in 'properties:' in /home/aep/proj/zephyr/zephyrproject/zephyr/dts/bindings/can/microchip,mcp2515.yaml, but does not appear in <Node /soc/spi@40004000/mcp2515@0 in 'nrf52_pca10040.dts.pre.tmp'>
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

so i after removing the broken property, i finally have a working CAN driver.

Parents
  • +1

    Hi,

    with the latest Zephyr master I am able to reproduce the device tree category issue.

    I would report this to the Zephyr project since that is where the CAN sample is maintained.

    rm -rf b && cmake -H. -Bb -DCONF_FILE=prj.conf.mcp2515 -DDTC_OVERLAY_FILE=${PWD}/mcp2515-dts.overlay

    I also had to change from gpioa to gpio0. I believe the sample is wrong to use gpioa and that this also should be reported to the Zephyr project.

Reply
  • +1

    Hi,

    with the latest Zephyr master I am able to reproduce the device tree category issue.

    I would report this to the Zephyr project since that is where the CAN sample is maintained.

    rm -rf b && cmake -H. -Bb -DCONF_FILE=prj.conf.mcp2515 -DDTC_OVERLAY_FILE=${PWD}/mcp2515-dts.overlay

    I also had to change from gpioa to gpio0. I believe the sample is wrong to use gpioa and that this also should be reported to the Zephyr project.

Children
  • 0 in reply to Sebastian Bøe

    thanks. zephyr devs have confirmed and fixed the bug, but the nordic tree is an outdated fork. Can we use upstream zephyr for the nrf91 or will that be missing drivers?

  • 0 in reply to a3p

    Hi,

    the basic set of drivers exist upstream I know, but to what extent (if any) we have extended the drivers downstream I do not know.

    Your choices are to either use upstream zephyr, or wait a few weeks for the patch to arrive downstream, or to try to apply the fix downstream.

Terms of service