Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rddrone_fmuk66: fatal error upon running basic samples #44314

Closed
landonh12 opened this issue Mar 29, 2022 · 0 comments · Fixed by #44780
Closed

rddrone_fmuk66: fatal error upon running basic samples #44314

landonh12 opened this issue Mar 29, 2022 · 0 comments · Fixed by #44780
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP priority: low Low impact/importance bug

Comments

@landonh12
Copy link
Contributor

landonh12 commented Mar 29, 2022

Describe the bug
When attempting to build, flash, and debug the following samples on rddrone_fmuk66:

  1. samples/basic/blinky
  2. samples/basic/blinky_pwm
  3. sampes/hello_world

Zephyr does not supply any console output nor does it control the LEDs as intended.

To Reproduce
Steps to reproduce the behavior:

  1. Build one of the samples mentioned above for target rddrone_fmuk66
  2. Flash the resulting binary file using west flash
  3. Run west debug, continue, and wait approximately 10 seconds, then provide a SIGTRAP (Ctrl+C)
  4. Code will break on one of the following:
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
z_fatal_error (reason=0, esf=0x20000fa8 <z_interrupt_stacks+2024>) at /home/landon/git/zephyrproject/zephyr/include/arch/arm/aarch32/asm_inline_gcc.h:56
56		__asm__ volatile(
(gdb) 
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
arch_system_halt (reason=reason@entry=0) at /home/landon/git/zephyrproject/zephyr/kernel/fatal.c:32
32		}

Additional context
Followed the "Getting Started Guide" here: https://docs.zephyrproject.org/latest/getting_started/index.html
Once this was finished, I tried building for the rddrone_fmuk66 first.
This was tried on two different board revisions - RevD and RevE, and the same error occurs.
Other samples were not attempted.
Using a Dell XPS 13 running Ubuntu 20.04 to build.
Versions:

$ cmake --version
cmake version 3.22.2
$ python3 --version
Python 3.8.10
$ dtc --version
Version: DTC 1.5.0
@landonh12 landonh12 added the bug The issue is a bug, or the PR is fixing a bug label Mar 29, 2022
@carlescufi carlescufi added platform: NXP NXP priority: low Low impact/importance bug labels Mar 29, 2022
@danieldegrasse danieldegrasse self-assigned this Apr 11, 2022
@dleach02 dleach02 removed their assignment Apr 12, 2022
mbolivar-nordic pushed a commit that referenced this issue Apr 13, 2022
Correct the following errors in rddrone pinmux:
- Pin selection for UART4 RTS line was incorrect, should use PTE27
- Pin selection for red PWM LED was incorrect, should use PTD1
- FlexCAN0/1 RX should not have pullup resistors (per prior pinmux.c
settings)
- FTM0_CH1_PTA4 does not require a pullup resistor
- LPUART0_RX_PTD8 requires a pullup resistor for UART RX to work

Fixes #44314

Signed-off-by: Daniel DeGrasse <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants