Hi my Name is Kevin,
我想建立我own module for bluetooth reciever.
I always stuck on this problem, and therefore I need your help to guide me what's wrong with the data transmit
1) I'm using SPI on my Module to flash the data, and I use DA 14580 as my Bluetooth Component
2) Whenever I tried to connect my module (which components I believe identical to Smart Tag which has proved worked) using Smart Snippets I always get this message
[INFO @17-11-09 18:27:02] Could not measure total IR len. TDO is constant high.
[ERROR @17-11-09 18:27:02] Could not read memory.
[ERROR @17-11-09 18:27:02] No known chip found while opening JLink connection. Terminating proccess...
3) Yes, I'm using JTAG
4) I connect the module from DA-14580 Basic DevKit
5) I'm using port P 0_0 , P 0_3 , P 0_5 , P 0_6 for my SPI model Flash
Please help me with this problem, I don't understand what's wrong, and I can't connect my module to Smart Snippets
since I believe all the component that I installed and chose is already suitable with the requirement
Kevin.
Hi Kevin
This is an indication from the Jlink software and not from Smart Snippets (when connected via JTAG, Smart Snippets uses the jlink in order to access the device), the connections of the flash are irrelevant with what you are experincing. Apparently there is no connection between the processor on the custom PCB and the Jlink fw that tries to communicate with the device. That could be anything from connections up to problems with the PCB that make the 580 unable to operate. For starters i would start with the PCB and i would check if the bootloader is executing in order to verify that the 580 is operating (pins P04 and P05 should toggle executing part of the bootloader, so when connecting to a terminal you should see the device printing garbage), after that and if the device was operating i would check the connections between the dev kit that implements the JTAG and the custom board. Also i would try to connect with the board using the Jlink itself, instead using Smart Snippets and also i would try to download code via Keil.
Thanks MT_dialog
好吧也许这听起来是一个little bit basic,
Regarding OTP Image, Do I need to burn OTP before I able to burn SPI ? or is it worked separately ?
Hi Kevleo94,
The indication that you get is a generic indication that Jlink provides when its not able to communicate with the processor, you cannot assume anything from that message, as mentioned the communication indication issue can be anything, either that there is a problem with the wires that you are using in order to connect the JTAG with the device (wrong connection, noise over the connection, etc) or that the MCU doesn't respond at all, which again the reasons for that can be quite a few. So verify that the 580 operates with the procedure i mentioned on my previous post.
Regarding the OTP image and the SPI, no you dont have to burn the OTP in order to be able to run a project, you can either download a fw directly to sysram (either via the UART or the JTAG interface) or burn an image on the spi flash and the bootloader will mirror the image to the sysram.
Thanks MT_dialog