Hi y'all,
我正在研究“连接经理”工具，并有一点咬人的问题我正在处理。
when following the TypeZF_FirstStepGuide(N1-2896A)en Document . I found a problem with the "6.2 Boot as Peripheral Device."
and "6.3 Boot as Central Device."
Normally in the tow cases a window on the left of the framework appears"Advertising" and "Discover/Connect" after pressing "Boot as Peripheral" and "Boot as Central" buttons.
In my case, these two windows do not appear. :s
Thank you for the help
Hi abdelZ,
Are both USB and J-Link connected?
Does your PC recognize J-Link adapter as shown in "6.1 Setup Connection Manager" ?
Is appropriate COM port selected?
Hi Tetsu,
When I plug JLINK with the computer, nothing appears on the computer. But when I plug the FTDI (mini USB) two COM ports appear.
Thanks for the help
Hello,
I am experiencing a similar problem with Connection Manager. I do not know if my PC is recognizing the J-Link Adapter in 6.1 because there is nothing in the documentation that advises me how to determine this. This is what happens:
1.当我将J-Link连接到USB端口时，它将显示在“通用串行总线控制器=> J-Link驱动程序”下的“设备管理器”中。
2. When I plug in the Murata P2ML3078 (with the TypeZF inserted) into a USB port, Device Manager shows 2 devices under "Ports (Com & LPT).
3. One device is USB Serial Port (COM13) and the other is USB Serial Port (COM 14).
4. When I open up Connection Manager, it defaults to COM14, 115,200 baud, Type RTS/CTS and it loads the ""full_emb.hex" file.
5. The main console in Connection Manager reads:
>SEGGER J-Link Commander V4.72 ('?' for help)
>编译2013年6月12日15:47:30
>Unknown command line option loadbin.txt.
6. This is where progress stops. Pressing either Boot as Central Or Boot as Peripheral opens the COM port selected, and the console reads:
UART COM13 Open
====> [13:36:00.967] Tx <====
Src Task : 0x3f (TASK_APP)
Dst Task : 0xd (TASK_GAPM)
味精Id: 0 x3402 (GAPM_RESET_CMD)
Operation : 0x01
Payload : 02 34 0d 00 3f 00 01 00 01
--------------------------------------------------------------------------------
Things I have tried:
A. I have tried selecting the lower COM port COM13, then reloading the default firmware, full_emb.hex.
B. I have tried changing the Baud rate to 57,600 for both Ports, reloading the firmware with each.
C. I have tried using the hex file that was successfully built, installed, and tested in section 5 (full_emb_sysram.hex) just to see if I can get anything to happen.
D. When I do 'C' above, the first section of the log displays "No devices found on JTAG chain. Trying to find device on SWD No device found on SWD. After that the console readout is similar to the figure in 6.1, with lines reading:
>重置延迟:0
>Reset type UNKNOWN: ???
>Info: Could not measure total IR len. TDO is constant high.
--------------------------------------------------------------------------------------------------
I don't think there is anything else that I can try, I am able to use SmartSnippets without any problems. What am I missing here or not doing correct?
Thanks, klim
Hi klim,
Could you try the following steps to make sure the J-LINK / SWD interface is working?
1. Run Keil uVision
2. Select "Project" - "Options" (or press ALT + F7)
3. Select "Debug" tab.
4. Click "Settings" next to pull down menu "J-LINK / J-Trace Cortex".
5. Check "SW Device" area. If you see "ARM CoreSight SW-DP", the chip is correctly recognized by J-Link.
此致，
Tetsu
Hi Tetsu,
Thanks for your help, yes, in uV (V5.14.0.0) I am able to see and connect to the J-Link, that was not the problem.
Very simple as it turns out. I realized that the line reading "Unknown command line option loadbin.txt" was the clue.
Sure enough, the link on my desktop was pointed to a batch file (startup.bat) so I navigated to it, right clicked on it, then set the permissions for all users to "full access".
Now when I start up Connection Manager, I get a console readout with the JLink connection details, etc, ending with the short bit below and indicating success.
---------------------------------------------------------
Loading binary file full_emb.bin
Reading 15536 bytes data from target memory @ 0x00000000.
Verify successful.
----------------------------------------------------------------
希望这有助于别人---克里斯
Hi Chris,
很高兴听到你解决了这个问题。感谢您分享的信息。