Can't find chipid registering Nano 2


#1

I just installed the studio and am trying to register and virtualise the nano 2 - I keep getting the error "can’t find chipid"

I am using an Apple Mac for the upload - do I need to install something for daplink, although I can see the divide in finder.

any ideas on what the problem may be

many thanks

Cindy


#2

Hi Cindy Alice,

If finder can see the device as mass storage device, The Zerynth Studio should recognized the RedBear Nano 2.
To better understand you issue, can you post me the log message of the following commands:

- open iTerm with only the RedBear Nano 2 plugged into your machine;
- tap “ztc device discover --matchdb” in the terminal (post me the results)
- if you see the device with alias field filled, tap “ztc device register zs” in the terminal (post me the results)

keep me posted


#3

I have the same issue. “ztc device discover --matchdb” returns (the xxxx’s are a 40 character hex string):

RedBear Nano 2  zs:redbear_nano2:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx            xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx                         RedBearNano2  /dev/tty.usbmodem1A13422  /Volumes/DAPLINK

"ztc device register zs" returns:

[info]> Starting device registration

[error]> Can't find chipid

Is there any other information I can send to help diagnose this?

Thanks


#4

Matteo

here is the result of the act command

name            alias                                                      target    uid                                       chipid    remote_id    classname     port                    disk

--------------  ---------------------------------------------------------  --------  ----------------------------------------  --------  -----------  ------------  ----------------------  ----------------

RedBear Nano 2  zs:redbear_nano2:ae277c6a3c579e31062768db6901713bd203f90f            ae277c6a3c579e31062768db6901713bd203f90f                         RedBearNano2  /dev/tty.usbmodemFD132  /Volumes/DAPLINK

as you can see the chipped field is blank as is the remoteid and target fields.


the second command returned

imac:~ cindy$ ztc device register zs

[info]> Starting device registration

[error]> Can't find chipid


whats next? 

thanks Cindy

#5

Update 
I just repeated the whole exercise on WINDOWS 10 - 64 bit. The results are the same except for the port id - COM3:
Cindy


#6

Ok, seems like the ztc is able to open the serial port but unable read properly.

You can insert the following line in devcmd.py source file to help the debug:

- Open the file in this path:
    -->  ~/.zerynth2/dist/r2.0.4/ztc/devices/devcmd.py  (for Linux and Mac)
    -->  ~/zerynth2/dist/r2.0.4/ztc/devices/devcmd.py  (for Windows)
- Insert this code in line 285:

    print(“lines:”, lines, “cnt:”, cnt, “pos:”, pos)
- Tap again the command in the terminal:<br>&nbsp; &nbsp; ztc device register zs (for Windows and Mac)<br>&nbsp; &nbsp;./ztc device register zs (for Linux - it is necessary to run this command inside the ~/.zerynth2/dist/r2.0.4/ztc folder)<br><br>- Post me the results of the cmd.<br><br>Note: extract of devcmd.py file after modification:<br>
`    ...
    
    lines = []    
    for x in range(10):
`` for x in range(10):
`` line=ch.readline()
`` lines.append(line.strip("\ "))
`` ch.close()
`` cnt = [lines.count(x) for x in lines]
`` pos = cnt.index(max(cnt))
`` print("lines:", lines, "cnt:", cnt, "pos:", pos)
`` if pos>=0 and cnt[pos]>3 and len(lines[pos])>=8:
`` info("Found chipid:",lines[pos])
`` else:
`` fatal("Can't find chipid") ...` ``` ```

#7

the result in windows is attached 



basically - [’’, ‘’,’’,’’,’’,’’,’’,’’,’’,’’] [10,10,10,10,10,10,10,10,10,10] 0

SAME on MAC

thanks


#8

mmm…now we have to understand if there is a problem loading the registering bootloader or if there is a problem with the serial port.

The next step is to copy (drag and drop) the registering bootloader binary file (you can find inside the zip attachment) in the Daplink disk storage (like copy a file inside a usb pen).

After this you can open a serial terminal (examples are: TeraTerm for Windows, Minicom for Linux, and Screen for Mac) choosing the related serial com port and setting the baud rate to 115200.

If everything works you should view the device chip id printed in an infinite loop; in this case your issue regards the loading of the registering bootloader inside the device (have you a Windows 7 machine?).

If you don’t see anything in the terminal you could have a problem in your usb drivers; you can take a look this discussion.

Let me know :) 

Note: this procedure also works for Linux a Mac machines


#9

the drive looks fine COM3 anf f:
however when i copy the bin file tot he DAPLINK i get a FAIL.TXT on the daplink drive - the contents reads “The transfer timed out.”. i can copy a txt document to the drive with no problem

i read the article about USB drivers - but would this be a  problem on both my mac and windows - its windows 10 not 7. 

Any other ideas? 

Teraterm is showing nothing - perhaps because the bin did not load? 

should i delete the daplink drivers and try reinstalling them? …



#10

the drive looks fine COM3 anf f:
however when i copy the bin file tot he DAPLINK i get a FAIL.TXT on the daplink drive - the contents reads “The transfer timed out.”. i can copy a txt document to the drive with no 

i read the article about USB drivers - but would this be a  problem on both my mac and windows - its windows 10 not 7. 

Any other ideas? 

i never tried teraterm since the loader did not copy - i will do this now… its 10pm in aus at the moment



#11
from details.txt on F:


 # DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 1095000031318c5e0c36303333363445a5a5a5a597969905
HIC ID: 97969905
Auto Reset: 1
Automation allowed: 0
Daplink Mode: Interface
Interface Version: 0242
Bootloader Version: 0242
Git SHA: 687816565ab72ec808eba2520eaaa1b26fe5d119
Local Mods: 0
USB Interfaces: MSD, CDC, HID
Bootloader CRC: 0xbe284a3a
Interface CRC: 0x815812e5


#12

i did mention previously it was a windows 10 64 bit machine
i read this - https://github.com/mbedmicro/DAPLink/issues/201


#13

the other file on the daplink drive is MBED.HTM and contains this

<!doctype html>
mbed Website Shortcut


i am now stuck… deleting the daplink driver and reinstalling did not help.

thanks

#14

You have to delete all files inside the DAPLINK disk storage before copying the *.bin file


#15

i did - it makes no difference? 

i wonder if its a nano 2 problem…


#16

any ideas?


#17

I encountered the same problem when using RedBear DAPLink v1.5, but I updated the DAPLink firmware to fix this problem. You can try it.
(https://github.com/redbear/nRF5x/blob/master/daplink/DAPLink_V1.5_Interface_nRF52_20170106.bin)


#18

PROBLEM SOLVED…

I logged a problem with REDBEAR 

Seems i needed updates to the daplink firmware.

Here is a copy of the ticket - 
Ticket: https://redbear.freshdesk.com/helpdesk/tickets/1061

1. Please try to update the DAPLink firmware again:

2. And then try to drag and drop the blink test firmware to the Nano 2 to see if it works: 


thanks for your help and the runaround

Love your product so far 

Cindy


#19

Have the same problem with RedBear Blend v2.

In maintenance mode install the latest firmware for DAPLINK:
MK20_V1.0_Interface_nRF52_20170222.bin

Have this text in DAPLINK drive:

# DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 109300003350ad1f0f30323934353254a5a5a5a597969905
HIC ID: 97969905
Auto Reset: 1
Automation allowed: 0
Daplink Mode: Interface
Interface Version: 0242
Bootloader Version: 0242
Git SHA: af16b1713e236cd4242714179cc2d6bbd2a7e385
Local Mods: 1
USB Interfaces: MSD, CDC, HID
Bootloader CRC: 0xbe284a3a
Interface CRC: 0xcf6e2769

Connect to Zerinth and get this log trying to register:

Loading settings…
Ready!
Checking for updates…
[info] Starting device registration
[info] Burning bootloader…
[error] Can’t burn bootloader! --> Can’t find device disk! Have you mounted the DAP Link device?

In Device manager:

Portable Devices
DAPLINK

Ports(COM & LPT
ECP Printer Port(LPT1)
mbed Serial Port(COM17)

Universal Serial Bus Controllers
mbed Composite Device