Replies: 2 comments 1 reply
-
Hi @Requasar! We appreciate you submitting your first issue for our open-source project. 🌟 Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Origin
https://docs.zephyrproject.org/latest/releases/release-notes-4.1.html
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm/boot/dts?h=am6-abi-ti-linux-4.19.y
Purpose
Add initial board support for the BeagleBone Black (Rev C) based on the TI AM335x SoC. The goal is to get a minimal "hello_world" sample to build and run.
Mode of Integration
This is not an integration request. I am seeking community support for a blocking DTS issue for a personal project.
Maintainership
Seeking community guidance to resolve a blocking DTS issue first. A maintainer can be assigned once the port is functional.
Pull Request
No response
Description
PROBLEM DESCRIPTION
I am trying to get the BeagleBone Black (Rev C) board running with Zephyr v4.1.0 for a personal project.
After extensive debugging, I am consistently blocked by a persistent DTS parsing error. My analysis suggests this is a "context loss" issue within the build system, where the parser fails to correctly process node properties.
The consistent, blocking error is:
devicetree error: unexpected 'interrupt-cells:' length in binding for <Node /ocp/interrupt-controller@48200000 in 'zephyr/misc/empty_file.c'> - 0 instead of 1
The reference to
empty_file.c
is the key symptom. This happens even when all definitions are placed within a single, self-contained DTS file, ruling out simple#include
or pathing issues.REPRODUCIBLE REPOSITORY & RELEVANT FILES
To make debugging as easy as possible, I have created a dedicated GitHub repository containing all the necessary files in their correct Zephyr directory structure.
>> REPOSITORY LINK: https://github.com/Requasar/Beaglebone_black_Zephyr <<
MY ANALYSIS OF THE CORE PROBLEM
My analysis points to a direct contradiction concerning the
interrupt-controller
node.The error message claims
#interrupt-cells
is0
, but my source files explicitly define it as1
.In my DTS file (
.../dts/arm/ti/am33xx.dtsi
in the repo):In my YAML binding file (
.../dts/bindings/interrupt-controller/ti,am33xx-intc.yaml
in the repo): To be certain, I enforced this rule withconst: 1
, but it had no effect on the error.This demonstrates that even though the source files are correct, the build system's parser is failing to read the value correctly.
MY REQUEST
I am simply trying to get it working and am hoping for some guidance from the community. I have reached the limit of my debugging abilities.
I would be extremely grateful for any help on:
empty_file.c
context-loss error?https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm/boot/dts?h=am6-abi-ti-linux-4.19.y
and i thought my .dtsi files are not compatible with zephyr because i didn't create them directly for zephyr and it can create issues but i am not sure about it. Should i expect those files to work zephyr with few changes?
Thank you for your time and assistance.
FULL ERROR LOG & ENVIRONMENT
west build -b beaglebone_black samples/hello_world
Beta Was this translation helpful? Give feedback.
All reactions