boot跳转app1异常 | 低功耗蓝牙 | 汇顶科技开发者社区

提问

标签

软件开发

设计支持

您的项目私密技术问题如需获得一对一支持，请点击下方联系我们。

联系我们

boot跳转app1异常 GR551x

178***711

2026-04-06 13:08

环境

1.GR5515I0NDA芯片，普冉8M外部flash，qspi通讯

2.固件版本GR551x_SDK_V2.0.2

3.boot使用原厂工程，关闭所有东西，只保留跳转

4.app1采用free的示例工程

现象

1.app1注释ble_stack_init(ble_evt_handler, &heaps_table);时，boot跳转成功，最起码工程线程运行正常

2.app1打开ble_stack_init(ble_evt_handler, &heaps_table);，boot跳转后，app1没有任何log输出

3.之前用过5331的芯片并不会这个样子，当然5331有宏定义可以关闭蓝牙功能，5515并不行，怀疑boot中初始化或者在什么地方调用了协议栈的相关东西

1关注

0收藏

0赞成

2个回答

热门最新

zhongchengzhi

汇顶员工

2026-04-08 14:11

您好，关于“pp1打开ble_stack_init(ble_evt_handler, &heaps_table);，boot跳转后，app1没有任何log输出”，您用jlink连接调试，看卡在哪里呢？

1条评论

0赞成

0收藏

您的评论

178***711

2026-04-08 17:01

我提取了部分信息，帮忙观察一下

向量表

Free示例工程

; Vector Table Mapped to Address 0 at Reset

AREA RESET, DATA, READONLY

EXPORT __Vectors

EXPORT __Vectors_End

EXPORT __Vectors_Size

IMPORT NMI_Handler

IMPORT HardFault_Handler

IMPORT MemManage_Handler

IMPORT BusFault_Handler

IMPORT UsageFault_Handler

IMPORT SVC_Handler

IMPORT DebugMon_Handler

IMPORT PendSV_Handler

IMPORT SysTick_Handler

IF :DEF:NO_SCATTER

__Vectors DCD __initial_sp ; Top of Stack

ELSE

IMPORT |Image$$ARM_LIB_STACK$$ZI$$Limit|

__Vectors DCD |Image$$ARM_LIB_STACK$$ZI$$Limit| ; Top of Stack

ENDIF

DCD Reset_Handler ; Reset Handler

DCD NMI_Handler ; NMI Handler

DCD HardFault_Handler ; Hard Fault Handler

DCD MemManage_Handler ; MPU Fault Handler

DCD BusFault_Handler ; Bus Fault Handler

DCD UsageFault_Handler ; Usage Fault Handler

DCD 0 ; Reserved

DCD SVC_Handler ; SVCall Handler

DCD DebugMon_Handler ; Debug Monitor Handler

DCD 0 ; Reserved

DCD PendSV_Handler ; PendSV Handler

DCD SysTick_Handler ; SysTick Handler

__Vectors_End

boot示例工程

; Vector Table Mapped to Address 0 at Reset

AREA RESET, DATA, READONLY

EXPORT __Vectors

EXPORT __Vectors_End

EXPORT __Vectors_Size

IMPORT NMI_Handler

IMPORT HardFault_Handler

IMPORT MemManage_Handler

IMPORT BusFault_Handler

IMPORT UsageFault_Handler

IMPORT SVC_Handler

IMPORT DebugMon_Handler

IMPORT PendSV_Handler

IMPORT SysTick_Handler

IF :DEF:NO_SCATTER

__Vectors DCD __initial_sp ; Top of Stack

ELSE

IMPORT |Image$$ARM_LIB_STACK$$ZI$$Limit|

__Vectors DCD |Image$$ARM_LIB_STACK$$ZI$$Limit| ; Top of Stack

ENDIF

DCD Reset_Handler ; Reset Handler

DCD NMI_Handler ; NMI Handler

DCD HardFault_Handler ; Hard Fault Handler

DCD MemManage_Handler ; MPU Fault Handler

DCD BusFault_Handler ; Bus Fault Handler

DCD UsageFault_Handler ; Usage Fault Handler

DCD 0 ; Reserved

DCD SVC_Handler ; SVCall Handler

DCD DebugMon_Handler ; Debug Monitor Handler

DCD 0 ; Reserved

DCD PendSV_Handler ; PendSV Handler

DCD SysTick_Handler ; SysTick Handler

__Vectors_End

异常观察：

SEGGER J-Link Commander V7.98a (Compiled Jul 19 2024 15:01:50)

DLL version V7.98a, compiled Jul 19 2024 15:01:03

Connecting to J-Link via USB...O.K.

Firmware: J-Link Pro V4 V12 PLUS Oct compiled 1 2024 13:26:37

Hardware version: V12.00

J-Link uptime (since boot): 0d 02h 15m 25s

S/N: 601022668

License(s): FlashBP, GDB, JFlash, FlashDL, RDI

USB speed mode: Full speed (12 MBit/s)

IP-Addr: 255.255.255.255 (DHCP)

VTref=1.889V

Type "connect" to establish a target connection, '?' for help

J-Link>connect

Please specify device / core. <Default>: CORTEX-M4

Type '?' for selection dialog

Device>

Please specify target interface:

J) JTAG (Default)

S) SWD

T) cJTAG

TIF>S

Specify target interface speed [kHz]. <Default>: 4000 kHz

Speed>

Device "CORTEX-M4" selected.

Connecting to target via SWD

Found SW-DP with ID 0x2BA01477

DPIDR: 0x2BA01477

CoreSight SoC-400 or earlier

Scanning AP map to find all available APs

AP[1]: Stopped AP scan as end of AP map has been reached

AP[0]: AHB-AP (IDR: 0x24770011)

Iterating through AP map to find AHB-AP to use

AP[0]: Core found

AP[0]: AHB-AP ROM base: 0xE00FF000

CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)

Found Cortex-M4 r0p1, Little endian.

FPUnit: 6 code (BP) slots and 2 literal slots

CoreSight components:

ROMTbl[0] @ E00FF000

[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7

[0][1]: E0001000 CID B105E00D PID 003BB002 DWT

[0][2]: E0002000 CID B105E00D PID 002BB003 FPB

[0][3]: E0000000 CID B105E00D PID 003BB001 ITM

[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU

Memory zones:

Zone: "Default" Description: Default access mode

Cortex-M4 identified.

J-Link>mem32 0x0100F000 2

0100F000 = 30040000 0100F1F1

J-Link>r

Reset delay: 0 ms

Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.

Reset: Halt core after reset via DEMCR.VC_CORERESET.

Reset: Reset device via AIRCR.SYSRESETREQ.

J-Link>g

Memory map 'after startup completion point' is active

J-Link>h

PC = 47BB70EE, CycleCnt = 2A87FFBC

R0 = 3003FE00, R1 = 00000001, R2 = 47BB70EF, R3 = 01014DE5

R4 = 3003FE38, R5 = 30007FEC, R6 = 1A87A484, R7 = 030FF010

R8 = 00000000, R9 = 3003FE94, R10= 00000000, R11= 01022260

R12= 0000C007

SP(R13)= 3003FE00, MSP= 3003FE00, PSP= 58FEFA60, R14(LR) = 01014DEF

XPSR = 21000003: APSR = nzCvq, EPSR = 01000000, IPSR = 003 (HardFault)

CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = 1F16FC61, FPS1 = 400A5365, FPS2 = 00000000, FPS3 = 40590000

FPS4 = E176BA40, FPS5 = 74C3F81D, FPS6 = C4403CC8, FPS7 = CFD0A285

FPS8 = F4C7E3E4, FPS9 = C7CBC875, FPS10= 651D0DD1, FPS11= 5023A3A5

FPS12= D6CCEAFD, FPS13= F658DA30, FPS14= FC4924CE, FPS15= E0FFF8E2

FPS16= F1D7EDAD, FPS17= 7A082E81, FPS18= 48189C04, FPS19= F5413674

FPS20= EDC00D81, FPS21= F8B00C44, FPS22= F3374F09, FPS23= 25558985

FPS24= BD540F3B, FPS25= BE94A830, FPS26= C409703E, FPS27= F26C4E86

FPS28= F62E06A2, FPS29= AEE503B5, FPS30= 838E0443, FPS31= 5CAD1884

FPSCR= 03000000

J-Link>regs