RT-Thread / RT-Thread/rt-thread
[Bug] Couldn't run board sample application
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
RT-Thread Version
5.2.0
Hardware Type/Architectures
GD32450Z-EVAL
Develop Toolchain
GCC
Describe the bug
Build & start debug sample located @ bsp\gd32\arm\gd32450z-eval
Appl crashed (hard_fault) on
rt_system_heap_init((void *)HEAP_BEGIN, (void *)HEAP_END);
call in board\board.c
next step in debugger went into hard_fault_handler
To prevent this crash I decresed 2 times available memory (in board.h).
#define GD32_SRAM_SIZE 128
Ok. Program started successfully - Led1 blink. I want to see console output. Connect to COM0 (J1) via RS232-USB converter, open serial-port with putty
but nothing happens. There is no answer from the board.
What should I do to test rtthread-sample on my board ? With GD32_SRAM_SIZE = 256. Or maybe need some fix on sample?
Other additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with bsp\gd32\arm\gd32450z-eval and inspect board\board.c, especially the rt_system_heap_init call, together with the GD32_SRAM_SIZE definition in board.h. Reproduce the hard fault with the GCC build and check the debugger state and serial connection. Done means the sample runs with the expected memory setting and produces console output on COM0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100