frame

Readbear Nano 2 "cannot burn bootloader"

Tried to register / virtualize the new Redbear Nano 2 (nrf52).
It always returns "cannot burn bootloader" in the console.
I also tried a Readbear Blend 2 with the same negative result.
Running on Windows10, DAPLink drive shows up correctly.
Both can be programmed without problems via DAPLink with the standard test hex files from the Redbear Github (e.g. HRM, Blinky).

Are the Nano2 / Blend2 nrf52 boards already supported by Zerynth ?
Does it work for the Zerynth team ?
Do you have some tips for me to check what went wrong ?
I am using Zerynth Studio 2.0.4.

Thanks :)


Comments

  • Hello @svenk,

    Redbear nano2 and blend2 are supported by Zerynth and in our Windows 10 testing machine we haven't spotted any registration problem.

    However, a first easy check is to click the info button (next to the "Z" button) and see if both "port" and "disk" attributes of the device are discovered correctly. 

    Let us know!


    Giacomo Baldi
    Zerynth Head of Software Development
  • svenk Member
    Hi @Giacomo,

    Port is shown as "COM4".
    Disk is shown as "none".

    However, in my Windows Fileexplorer view, the Nano2 is shown as "DAPLINK (J:)" and
    I can open it and drag/drop files there and they get programmed correctly.

    So, the question is, why is Zerynth not seeing/recognizing the J: drive ?
    Can you check the corresponding code or give me some hints how to switch on a verbose log
    or something so that I can see where it fails ?

    Thanks.

    P.S.: This is the contents of the DETAILS.TXT file on the DAPLINK drive:

    # DAPLink Firmware - see https://mbed.com/daplink
    Unique ID: [..]
    HIC ID: [..]
    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

    ([..] I have removed the IDs for security reasons)
  • GiacomoGiacomo Member
    edited February 3
    So, the question is, why is Zerynth not seeing/recognizing the J: drive ?
    Can you check the corresponding code or give me some hints how to switch on a verbose log
    or something so that I can see where it fails ?

    Very weird...
    I will definitely check the code asap. In the meantime, if you want to get some more detailed logs on what happens, you can check the file C:\Users\your-user\zerynth2\dist\r2.0.4\ztc\devices\winusb.py  in particular the function "_get_drive_letter_from_id".

    Issue the command:

    ztc device discover

    in a shell to test device discovery.

    Many thanks for the report



    Giacomo Baldi
    Zerynth Head of Software Development
  • svenk Member
    Hi @Giacomo,

    Output of ztc device discover:
    vid    pid    sid                                               uid                                       port    disk    desc
    -----  -----  ------------------------------------------------  ----------------------------------------  ------  ------  -----------------------
    0D28   0204   109300003131BC5E0C36303333363445A5A5A5A[..]  61fa7abdd32020401310c5283[..]  COM4            mbed Serial Port (COM4)

    ("disk" is empty)

  • Thanks @svenk ;

    I need more details to help debugging the issue. Can you please substitute the file C:\Users\your-user\zerynth2\dist\r2.0.4\ztc\devices\winusb.py with the one attached to this post? (Make a copy of the original first!)

    Then issue the command again, there will be much more logging. You can send it to me privately as it will show details about your machine peripherals.

    Thanks!

    Note: rename winusb.txt to winusb.py...the forum doesn't allow attaching .py files...
    winusb.txt 3.8K
    Giacomo Baldi
    Zerynth Head of Software Development
  • svenk Member
    Hi @Giacomo,

    in the meantime, I have deleted all USB drivers related to mbed or jlink or other hardware debuggers/programmers on my windows machine (also used "show hidden devcices" in dev. mgr., etc.).
    Then I let Windows re-install the DAPLink drivers.
    Et voila, "ztc device discover" now shows the drive letter and I could register & virtualize the Redbear Nano2.

    Strange thing is that before & after clean-up I could debug & program via DAPLink without problems, only before driver cleanup something interfered with your device/drive letter discovery code.

    Seemed to be an example of the so-called Windows "driver/registry hell" ;)
    Might be of interest for any Windows users encountering the same problems in the future.

    Thanks for your help !
  • @svenk ;

    ahah, good to know, I can stop scratching my head!  :D

    Giacomo Baldi
    Zerynth Head of Software Development
Sign In or Register to comment.

ZERYNTH Community

@ 2016 Zerynth.com, all rights reserved.