关于Linux下通过Jlink烧写stm32板子

发布于 2011-02-11 21:39:51 浏览：12462 订阅该版

15 个回答

bernard 2011-02-11

这家伙很懒，什么也没写！

aozima 2011-02-12

调网络不抓包，调I2C等时序不上逻辑分析仪，就像电工不用万用表！多用整理的好的文字，比截图更省流量，还能在整理过程中思考。

wzc0066 2011-02-14

这家伙很懒，什么也没写！

1. Jlink启动log:

```
zwang@wzc-laptop:~/source/JLink_Linux_V422$ ./start 
SEGGER J-Link Commander V4.22 ('?' for help)
Compiled Dec 17 2010 17:41:09
DLL version V4.22, compiled Dec 17 2010 17:41:06
Firmware: J-Link ARM V7 compiled Sep  6 2010 10:43:31
Hardware: V7.00
S/N: 11111117 
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDBFull 
VTarget = 3.293V
Info: Could not measure total IR len. TDO is constant high.

WARNING: CPU core not found.
No devices found on JTAG chain. Trying to find device on SWD.
Info: Found SWD-DP with ID 0x1BA01477
Info: TPIU fitted.
Info: ETM fitted.
Info:   FPUnit: 6 code (BP) slots and 2 literal slots
Info: Found Cortex-M3 r1p1, Little endian.
Cortex-M3 identified.
JTAG speed: 100 kHz
J-Link>
J-Link>

```

应该是正常启动了。

2. 确定加载地址并通过loadbin加载的log:

```
J-Link>loadbin /home/zwang/work_dir/stm32/rt-thread-read-only/bsp/stm3210/rtthread.bin 0x08000000
Loading binary file... [/home/zwang/work_dir/stm32/rt-thread-read-only/bsp/stm3210/rtthread.bin]
Writing bin data into target memory @ 0x08000000.
J-Link>

```

加载地址应该是0x08000000了，链接脚本stm32_rom.ld里面定义是这个地址，原来同事在keil下烧写的也是这个地址。
从log来看烧写好像没什么问题，只是有一点可疑：烧写一个33K的.bin文件都没延迟，Jlink有那么快吗？

但是烧写完毕之后重启板子执行的仍然是以前从keil下灌入的kernel(有rt_kprintf输出的)，请问原因可能出在什么地方呢 ？