about this theme, I am testing the DA14580 board with the proximity report application and the Connection Manager(using BTLE/USB Dongle). At the first I connect the USB Dongle and start the Connection Manager, then its detected the J-Link CDC UART in the Connection Manager and the verification and script proccess are succesfullly. Then I select "Boot as Central" to conect with DA14580, I scan the devices but in the Address list there are any Address(device) to establish Link. That it ocurred with the version 2.0.4 und I have seen a newer version in the Webpage (3.0.4) then I have installed und I done the same process. Now when I select "Boot as Central" the software doesn't do anything, therefore , It shows any Tab to scan devices. Then I would like know, if that is an error or I am doing some bad?
I've got the EVAL_PAN1740 Development kit with a couple USB dongles with the DA14580 on them. I seem to be having a related problem. I'm using Connection Manager 3.0.6. Here's the startup text, which is also what happens when I try to "Load Firmware...":
Hex2bin v1.0.10,版权所有(c)2012 jacques Pelletier&贡献者 Lowest address = 00000000 Highest address = 000034E7 Pad Byte = FF 8-bit Checksum = 30
工具目录:C:\ Program Files(X86)\ ConnectionManager \ Bin \ Firmware_Upload \ Using HEX file: "C:\Program Files (x86)\ConnectionManager\bin\firmware_upload" "full_emb.hex"
--- Generated JLink Script File ---
SEGGER J-Link Commander V4.72 ('?' for help) Compiled Jun 12 2013 15:47:30 未知命令行选项loadbin.txt。
Okay, so do I have an incompatible J-Link Commander version? When I try to "Boot as Central", nothing happens, presumably because no firmware is loaded.
I can download and debug code using Keil, and I have some limited success using SmartSnippets, but the Connection Manager has been a problem.
sorry for late answer. 可以在您的Firmware_Upload文件夹中缺少Hex2bin.exe程序吗? Or old version? The recent version is dated 26-09-2014 (14:22 Hrs) and size is 54.2 KB. The JLINK.exe has the same date.
The loadbin.txt file should contain the following or similar:
r w2 50000012, A6 W2 50003308, 2e loadbin "full_emb.bin", 0 verifybin "full_emb.bin", 0 r g exit
Following should be be written in the Log window:
--- Generated JLink Script File --- r w2 50000012, A6 W2 50003308, 2e loadbin "full_emb.bin", 0 verifybin "full_emb.bin", 0 r g exit --- SEGGER J-Link Commander V4.72 ('?' for help) Compiled Jun 12 2013 15:47:30 脚本文件已成功读取。 DLL版v4.72,编译6月12日2013 15:47:08 Firmware: J-Link ARM Lite V8 compiled Jul 8 2013 18:37:55 硬件:V8.00. etc.
Hi There, we only have the 32 bit, but it runs just fine on Windows 7 (64 bit). Windows i believe has built in emulator (seamless) which enables 32 apps to run on 64 platforms.
嗨Zeina,不幸的是,我们只有一个版本的连接经理现在可用。
BR JE_Dialog
谢谢。
Concerning the Connection Manager though, can it be used to test the keyboard application?
谢谢
Zeina
你好,
about this theme, I am testing the DA14580 board with the proximity report application and the Connection Manager(using BTLE/USB Dongle). At the first I connect the USB Dongle and start the Connection Manager, then its detected the J-Link CDC UART in the Connection Manager and the verification and script proccess are succesfullly. Then I select "Boot as Central" to conect with DA14580, I scan the devices but in the Address list there are any Address(device) to establish Link. That it ocurred with the version 2.0.4 und I have seen a newer version in the Webpage (3.0.4) then I have installed und I done the same process. Now when I select "Boot as Central" the software doesn't do anything, therefore , It shows any Tab to scan devices.
Then I would like know, if that is an error or I am doing some bad?
谢谢
Jvp
@ zmakki9:
yes, you can.
连接经理should be started in Central mode, and in the window you then can see the packets received, e.g. when pressing a key.
最好的问候,bb_dialog,
Dialog BLE Support Team.
@ DesignExt,
在Connection Manager中,您应该从/ bin / firmware_upload /文件夹(加载固件)加载文件'full_emb.hex'。
Choose the lowest Com port number of the UART com port pair. 'Flow Control' set to 'None'.
加载SW后,并按下“启动作为中央”,左窗格应显示选项和设置。连接间隔等
最好的问候,bb_dialog,Dialog BLE Support Team.
你好bb_dialog,
谢谢您的回答。我做了相同的事情。在以前的版本(2.0.4)在加载SW和按下“启动作为中央”后,在左侧面板中显示了扫描的所有选项。但在更新到版本3.0.4之后,我已将SW,SetFlow控件加载到None,然后按“启动作为控制”,但我收到任何Anwswer und左侧面板在开头(Ohne选项Connections)相同。
best regards,
Jvp
Hello DesignExt,
I'm sorry to hear it's not working for you.
Did you try another USB port - preferably one directly at your PC, not via an external hub?
Did you try to unplug and plug in again?
如果这不成功,我会将您的问题转发给工具开发团队。
最好的问候,bb_dialog,dlalog ble支持团队
你好bb_dialog,
Did you solved the issue described by DesignExt? I'm encountering the same problem...
Thank you
CristiP
Hello CristiPop,
I don't know. This was not fed back to us.
In general when facing this issue, following things mostly solved the Conn.Manager issues:
- 尝试其他USB端口(例如非USB3端口)。
- 选择正确的UART COM端口(UART对中的较低数字)。
- set Hardware Flow control to 'None'.
- take care to use the right GPIO's of the DA14580. On our eval.kits and in the SDK these are defined to P0_4 and P0_5.
Best regrds, BB_Dialog.
I've got the EVAL_PAN1740 Development kit with a couple USB dongles with the DA14580 on them.
I seem to be having a related problem. I'm using Connection Manager 3.0.6. Here's the startup text, which is also what happens when I try to "Load Firmware...":
Hex2bin v1.0.10,版权所有(c)2012 jacques Pelletier&贡献者
Lowest address = 00000000
Highest address = 000034E7
Pad Byte = FF
8-bit Checksum = 30
工具目录:C:\ Program Files(X86)\ ConnectionManager \ Bin \ Firmware_Upload \
Using HEX file: "C:\Program Files (x86)\ConnectionManager\bin\firmware_upload" "full_emb.hex"
--- Generated JLink Script File ---
SEGGER J-Link Commander V4.72 ('?' for help)
Compiled Jun 12 2013 15:47:30
未知命令行选项loadbin.txt。
Okay, so do I have an incompatible J-Link Commander version? When I try to "Boot as Central", nothing happens, presumably because no firmware is loaded.
I can download and debug code using Keil, and I have some limited success using SmartSnippets, but the Connection Manager has been a problem.
Hi dsuilmann,
sorry for late answer.
可以在您的Firmware_Upload文件夹中缺少Hex2bin.exe程序吗?
Or old version?
The recent version is dated 26-09-2014 (14:22 Hrs) and size is 54.2 KB.
The JLINK.exe has the same date.
The loadbin.txt file should contain the following or similar:
r
w2 50000012, A6
W2 50003308, 2e
loadbin "full_emb.bin", 0
verifybin "full_emb.bin", 0
r
g
exit
Following should be be written in the Log window:
--- Generated JLink Script File ---
r
w2 50000012, A6
W2 50003308, 2e
loadbin "full_emb.bin", 0
verifybin "full_emb.bin", 0
r
g
exit
---
SEGGER J-Link Commander V4.72 ('?' for help)
Compiled Jun 12 2013 15:47:30
脚本文件已成功读取。
DLL版v4.72,编译6月12日2013 15:47:08
Firmware: J-Link ARM Lite V8 compiled Jul 8 2013 18:37:55
硬件:V8.00.
etc.
Best regards, BB_Dialog
谢谢! That was it... the firmware_upload folder had no loadbin.txt for some reason. It was in a path under "my documents".
Hi dsuilmann,
I met the same problem like yours. Could you please tell me where I can find the loadbin.txt? I haven't found it..Thank you in advance
SmartSnippets / Resources / Firmware_Upload具有LoadBin.txt,以及ConnectionManager / Bin / Firmware_Upload中其他所有其他内容的旧版本
Hello,
Is there a Connection_manager exe file for WIndows-64bit ---Windows-7?
谢谢
asm
你能回答这个问题吗?question please
Hi There, we only have the 32 bit, but it runs just fine on Windows 7 (64 bit). Windows i believe has built in emulator (seamless) which enables 32 apps to run on 64 platforms.
BR JE_Dialog