Помощь - Поиск - Пользователи - Календарь
Полная версия этой страницы: TQ6410 и jlink v7 вместе работают?
Форум разработчиков электроники ELECTRONIX.ru > Микроконтроллеры (MCs) > ARM
yuray
Здравствуйте.
Имеется плата TQ6410 (s3c6410) и клон jlink v7 с последней прошивкой.
Первое чем пугают

SEGGER J-Link Commander V4.20h ('?' for help)
Compiled Oct 19 2010 14:02:03
DLL version V4.20h, compiled Oct 19 2010 14:01:59
Firmware: J-Link ARM V7 compiled Sep 6 2010 10:43:31
Hardware: V7.00
S/N:
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDBFull
VTarget = 3.261V
Info: TotalIRLen = 12, IRPrint = 0x0011

WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 5, NumBitsSet = 2)


WARNING: CPU core not found.
No devices found on JTAG chain. Trying to find device on SWD.

WARNING: CPU core not found.

****** Error: Parity error (Data = 0xFFFFFFFF, ReceivedParity = 1)

No device found on SWD.
Did not find any core.
Info: TotalIRLen = 9, IRPrint = 0x0011


*** J-Link V4.20h J-Link V4.20h Warning ***
You are using a J-Link which does not have intelligence for the
selected CPU core (ARM11).

Intelligence enables J-Link to generate sequences for the CPU core.
Without this feature, all sequences are generated by the PC.

Intelligence allows higher target interface speeds and significantly
enhances both speed and stability of the communication with the
target CPU.

You can use this J-Link with your target CPU, but we recommend
using a newer model of J-Link / J-Trace.
*** J-Link V4.20h J-Link V4.20h Warning ***

Found 2 JTAG devices, Total IRLen = 5:
#0 Id: 0x2B900F0F, IRLen: 04, IRPrint: 0x0, ARM ETB
#1 Id: 0x07B76F0F, IRLen: 05, IRPrint: 0x1, ARM1176 Core
ARM11 identified.
J-Link>?

Якобы покупайте v8, а то что?

С opencd
yuray@keeper:~$ /usr/local/bin/openocd -f tq6410.cfg
Open On-Chip Debugger 0.5.0-dev-00591-g09c798a (2010-11-16-13:29)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Warn : Adapter driver 'jlink' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
8000 kHz
adapter_nsrst_delay: 500
jtag_ntrst_delay: 500
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Info : J-Link initialization started / target CPU reset initiated
Info : J-Link ARM V7 compiled Sep 6 2010 10:43:31
Info : JLink caps 0xb9ff7bbf
Info : JLink hw version 70000
Info : JLink max mem block 9000
Info : Vref = 3.261 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0
Info : J-Link JTAG Interface ready
Info : clock speed 8000 kHz
Info : JTAG tap: s3c6410.etb tap/device found: 0x2b900f0f (mfg: 0x787, part: 0xb900, ver: 0x2)
Info : JTAG tap: s3c6410.cpu tap/device found: 0x07b76f0f (mfg: 0x787, part: 0x7b76, ver: 0x0)
Warn : Unexpected idcode after end of chain: 64 0x000007f8
Warn : Unexpected idcode after end of chain: 96 0x000007f8
Warn : Unexpected idcode after end of chain: 128 0x000007f8
Warn : Unexpected idcode after end of chain: 160 0x000007f8
Warn : Unexpected idcode after end of chain: 192 0x000007f8
Warn : Unexpected idcode after end of chain: 224 0x000007f8
Warn : Unexpected idcode after end of chain: 256 0x000007f8
Warn : Unexpected idcode after end of chain: 288 0x000007f8
Warn : Unexpected idcode after end of chain: 320 0x000007f8
Warn : Unexpected idcode after end of chain: 352 0x000007f8
Warn : Unexpected idcode after end of chain: 384 0x000007f8
Warn : Unexpected idcode after end of chain: 416 0x000007f8
Warn : Unexpected idcode after end of chain: 448 0x000007f8
Warn : Unexpected idcode after end of chain: 480 0x000007f8
Warn : Unexpected idcode after end of chain: 512 0x000007f8
Warn : Unexpected idcode after end of chain: 544 0x000007f8
Warn : Unexpected idcode after end of chain: 576 0x000007f8
Warn : Unexpected idcode after end of chain: 608 0x000007f8
Error: double-check your JTAG setup (interface, speed, missing TAPs, ...)
Error: Trying to use configured scan chain anyway...
Error: IR capture error at bit 9, saw 0x0011 not 0x...3
Warn : Bypassing JTAG setup events due to errors
Error: 'arm11 target' JTAG error SCREG OUT 0x00
Error: unexpected ARM11 ID code
Polling target failed, GDB will be halted. Polling again in 100ms
Polling target failed, GDB will be halted. Polling again in 300ms
Polling target failed, GDB will be halted. Polling again in 700ms
Polling target failed, GDB will be halted. Polling again in 1500ms
Polling target failed, GDB will be halted. Polling again in 3100ms
..и так по циклу.

Есть уменьшить частоту до 1Кhz то вроде всё хорошо.
yuray@keeper:~$ /usr/local/bin/openocd -f tq6410.cfg
Open On-Chip Debugger 0.5.0-dev-00591-g09c798a (2010-11-16-13:29)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Warn : Adapter driver 'jlink' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
8000 kHz
1 kHz
adapter_nsrst_delay: 500
jtag_ntrst_delay: 500
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Info : J-Link initialization started / target CPU reset initiated
Info : J-Link ARM V7 compiled Sep 6 2010 10:43:31
Info : JLink caps 0xb9ff7bbf
Info : JLink hw version 70000
Info : JLink max mem block 9000
Info : Vref = 3.261 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0
Info : J-Link JTAG Interface ready
Info : clock speed 1 kHz
Info : JTAG tap: s3c6410.etb tap/device found: 0x2b900f0f (mfg: 0x787, part: 0xb900, ver: 0x2)
Info : JTAG tap: s3c6410.cpu tap/device found: 0x07b76f0f (mfg: 0x787, part: 0x7b76, ver: 0x0)
Info : found ARM1176
Info : s3c6410.cpu: hardware has 6 breakpoints, 2 watchpoints
Warn : ETMv2+ support is incomplete
Info : ETM v3.2

Далее хочу остановить и продолжить выполнение программы.
Запускаю плату, торможу в eboot, жму несколько раз R -- конфиг перечитывает - ок.
запускаю opencd, подключаюсь
uray@keeper:~$ telnet localhost 4444
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x20000153 pc: 0x80061310

Вроде остановилась, в консоле на R уже не реагирует. Пытаюсь запустить продолжение

> resume

Отработала, но консоль не ожила.

> reg pc
Target not halted
pc (/32): 0x80061310
> resume
Target not halted
Command handler execution failed
in procedure 'resume'
> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Abort
cpsr: 0x200001d7 pc: 0x0000000c

(И вдруг pc уже в нулях. Почему?)

Почему не сработала resume?

Спасибо.
yuray
Обнаружилось, что добрые китайцы почему-то не распаяли 0е сопротивление для RTCK (что, впрочем, задокументировали).
После установки перемычки заработало.
10кб/сек в память это нормально?
Для просмотра полной версии этой страницы, пожалуйста, пройдите по ссылке.
Invision Power Board © 2001-2025 Invision Power Services, Inc.