Connection Manager

Hi Zeina, unfortunately we only the one version of connection manager available right now.

BR JE_Dialog

你好,

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?

Thanks

Jvp

@ zmakki9:

yes, you can.
Connection Manager should be started in Central mode, and in the window you then can see the packets received, e.g. when pressing a key.

Best regards, BB_Dialog,

Dialog BLE Support Team.

@ DesignExt,

In Connection Manager you should load the file 'full_emb.hex' from the /bin/firmware_upload/ folder (Load Firmware).

Choose the lowest Com port number of the UART com port pair. 'Flow Control' set to 'None'.

After loading the SW, and pressing 'Boot as Central', the left pane should show options and settings for e.g. connection interval etc.

Best regards, BB_Dialog,Dialog BLE Support Team.

Hello BB_Dialog,

thank you for your answers. I have done same. In the previous version(2.0.4) after the loading SW and pressed "Boot as Central" , in the left panel showed all option to scan. But after updated to version 3.0.4, I have loaded the SW , setFlow Control to None and press "Boot as Control" but I receive any anwswer und the left panel is same at the beginning (ohne options connnections).

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?

If this is not succesful, I'll forward your problem to the tool development team.

Best regards, BB_Dialog, Dlalog BLE Support Team

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:

- try another USB port (e.g a non USB3 port).

选择适当的UART串行通讯端口(ν越低mber from the UART pair).

- 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, Copyright (C) 2012 Jacques Pelletier & contributors
Lowest address = 00000000
Highest address = 000034E7
Pad Byte = FF
8-bit Checksum = 30

Tools directory: 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
Unknown command line option 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.
Could it be that in your firmware_upload folder the hex2bin.exe program is missing?
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
Script file read successfully.
DLL version V4.72, compiled Jun 12 2013 15:47:08
Firmware: J-Link ARM Lite V8 compiled Jul 8 2013 18:37:55
Hardware: V8.00
etc.

Best regards, BB_Dialog

Thanks! That was it... the firmware_upload folder had no loadbin.txt for some reason. It was in a path under "my documents".

Hello,
Is there a Connection_manager exe file for WIndows-64bit ---Windows-7?

Thanks
asm

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