Hello,
I am using PAN1740, trying to see how can I integrate DA14580 into my device.
There seems to be an issue with connection manager, it cannot load neither default, nor another firmware.
All I get when I start connection manager is:
hex2bin v1.0.10, Copyright (C) 2012 Jacques Pelletier & contributors
Lowest address = 00000000
Highest address = 00003EEB
Pad Byte = FF
8-bit Checksum = A0
And then when I try to Load a firmware and boot as central:
====> [11:42:22.486] Rx <====
UART COM7 Open====> [11:42:22.500] Tx <====
年代rc Task : 0x3f (TASK_APP)
Dst Task : 0xd (TASK_GAPM)
Msg Id : 0x3402 (GAPM_RESET_CMD)
Operation : 0x01
Payload : 02 34 0d 00 3f 00 01 00 01
Driver is installed and seem to work properly, COM 7 is detected.
Any ideas what should I do?
Here's a screenshot:http://prntscr.com/a1cwwh
Hi Alex,
Try to run the connection manager as an administrator and also make sure that the default uart pins are connected (jumpers in P04/P05) in case you are using a pro or a basic kit and not a dongle. Also make sure that the Connection Manager you have installed is the latest version.
Thanks MT_dialog
Hello,
Thanks for the reply!
I am using a dongle, PAN1740;
I am using "Administrator" type account, Windows 7, 64 bit;
年代oftware version of Connection Manager is the latest - 3.0.10, I downloaded it from here
年代egger driver seems to work fine, it is detected by device manager and terminal SW, it can be opened, closed, etc.
COM port access and Connection Manager seem to work without any problem.
I suppose the problem is somewhere between the Communication manager and the DA1458x, if I have to make a guess, there is no response from the DA to the 0x3402 (GAPM_RESET_CMD) and the process stops there - DA either doesn't receive or doesn't respond to that command.
Regards,
Alex Torofiev
Hi Alex,
When opening the tool it should make a conversion of the default .hex file(full_emb.hex)to binary and connect directly to the JTAG device using the JLink.exe file. You should be able to see the commands in the loadhex.bat file that is located in the Connection manager in the bin directory. i ve attached the proper messages you should see when opening the CM. Can you please re-install the Connection manager in case something went wrong during the installation proccess.
In your case the only message i see is the .hex2bin conversion output i dont see any execution of the Jlink.exe with the loadbin.txt parameter the connection or the download procedure of the .bin file.
Also what you can try is to manually run the donwloading procedure using the command line, just open the windows command line and navigate to to the Connection Manager/bin/firmware upload, then you can run the Jlink.exe "loadbin.txt" that should upload the full_emb.bin file in the 580 and then by opening the connection manager you can boot as central or as peripheral.
Thanks MT_dialog
Hi again and thanks for the quick reply,
我重新安装CM,也试穿了两个广告样稿uters to rule out any OS, usb and SW specifics. The result is the same.
I have no JTAG device, I am using PAN1740, expecting to be able to do the programming via USB to UART.
If I run JLink.exe manually I get:
年代EGGER J-Link Commander V4.72 ('?' for help)
Compiled Jun 12 2013 15:47:30
DLL version V4.72, compiled Jun 12 2013 15:47:08
Firmware: J-Link OB-SAM3U128 V1 compiled Feb 11 2016 16:04:25
Hardware: V1.00
年代/N: 480078265
VTarget = 3.300 v
Info: Could not measure total IR len. TDO is constant high.
Info: Could not measure total IR len. TDO is constant high.
No devices found on JTAG chain. Trying to find device on SWD.
Info: Found SWD-DP with ID 0x0BB11477
Info: FPUnit: 4 code (BP) slots and 0 literal slots
Info: Found Cortex-M0 r0p0, Little endian.
Cortex-M0 identified.
JTAG speed: 100 kHz
--------------------
If I run startup.bat I get a problem in loadbin.txt - I actually have no such file, I definitely haven't deleted it, I don't know where it should be and where does it come from :)
hex2bin v1.0.10, Copyright (C) 2012 Jacques Pelletier & contributors
Lowest address = 00000000
Highest address = 00003EEB
Pad Byte = FF
8-bit Checksum = A0
Tools directory: C:\Program Files\ConnectionManager\bin\firmware_upload\
Using HEX file: "C:\Program Files\ConnectionManager\bin\firmware_upload" "full_emb.hex"
--- Generated JLink Script File ---
---
年代EGGER J-Link Commander V4.72 ('?' for help)
Compiled Jun 12 2013 15:47:30
Unknown command line option loadbin.txt.
-----------------
If I just run ConnectionManager.exe I get almost nothing:
hex2bin v1.0.10, Copyright (C) 2012 Jacques Pelletier & contributors
Lowest address = 00000000
Highest address = 00003EEB
Pad Byte = FF
8-bit Checksum = A0
-------------
年代o probably the problem is in loadbin.txt?
Kind regards,
Alex Torofiev
Hello,
I found the solution of my problem in this topic:
http://support.dialog-semiconductor.com/%E2%80%9Dunknown-command-line-op...
Check out the third post by Ingo (Panasonic).
I created "loadbin.txt" with the specified content and now it seems to work.
I do not know why this file was missing, but it seems it happens to some users - several in that topic had that issue and just running the ConnectionManager.exe doesn't output the proper error message, so the users can't figure out that there is a file missing. I suppose this would be easy to implement a start up check for that in ConnectionManager or see why this file is skipped sometimes in instalation, if you think that makes sense.
Thanks for the support once again, it was helpful!
Kind regards,
Alex Torofiev
Hi Alex,
I was about to send you my loadbin.txt file. Thanks for the indication that your problem is solved.
Thanks MT_dialog