Cannot uplink to Hexiwear


#1

Greetings,

I am trying to upload a simple blinker program to my Hexiwear + docking station and failed. See below the output on Zeryth studio’s console. You don"t see the creation of the VM because it was already created, successfully. The final error is “No answer to probe”.

What is happening? Please advise, thanks in advance!
JP

/// Clicked the "Register" button

Checking for updates...
[info] Starting device registration
[info] Burning bootloader...
[info] Burning bin
Does D:\hexiwear.bin specify a file name
or directory name on the target
(F = file, D = directory)? f
C:\Users\(username)\zerynth2\tmp\tmpuzbqmzj1\tmp.bin -> D:\hexiwear.bin
1 File(s) copied
[info] Please reset the device!

/// Reset the device (pushing the left reset button on the docking station)

[info] Chip id retrieved: 92007005501354e4ffffffffffff9100
[info] Device Hexiwear (Docking Station) registered with uid: Ybh7MjQjRimxVblZJBE04g
Registration successful! Now you can virtualize your hexiwear
Checking for updates...

/// Clicked the "Virtualize" button - window closed, nothing new appeared on the console

Checking for updates...
Checking for updates...
Checking for updates...

/// Uplinked a simple led blinking example (main.py)

[info] Searching for C:\Users\(username)\hexiwear_example\__builtins__.py
[info] Searching for C:\Users\(username)\zerynth2\dist\r2.3.0\stdlib\__builtins__.py
[info] ########## STEP 0 - first pass
[info] Compiling module: __main__ @ C:\Users\(username)\hexiwear_example\main.py
[info] Searching for C:\Users\(username)\hexiwear_example\__builtins__.py
[info] Searching for C:\Users\(username)\zerynth2\dist\r2.3.0\stdlib\__builtins__.py
[info] Compiling module: __builtins__ @ C:\Users\(username)\zerynth2\dist\r2.3.0\stdlib\__builtins__.py
[info] ########## STEP 0 - second pass
[info] Compiling module: __main__ @ C:\Users\(username)\hexiwear_example\main.py
[info] Searching for C:\Users\(username)\hexiwear_example\__builtins__.py
[info] Searching for C:\Users\(username)\zerynth2\dist\r2.3.0\stdlib\__builtins__.py
[info] Compiling module: __builtins__ @ C:\Users\(username)\zerynth2\dist\r2.3.0\stdlib\__builtins__.py
[info] ########## STEP 4 - generate binary
[info] Resource table at 864 0x360
[info] Saving to C:\Users\(username)\zerynth2\tmp\zstudio.vbo
[info] Compilation Ok
[info] Searching for device d15d9bbc8b17b9a79e7c2fda6500dd1a94fba624 with alias zs:hexiwear:d15d9bbc8b17b9a79e7c2fda6500dd1a94fba624
[info] Please reset the device!
[info] Searching for device d15d9bbc8b17b9a79e7c2fda6500dd1a94fba624 again
[info] Checking layout...
[info] No active layout found
[info] Got header: 92007005501354e4ffffffffffff9100
........ (this is repeated several times)
[info] Got header: 92007005501354e4ffffffffffff9100
[info] Got header: 92007005501354e4ffffffffffff9100
[error] No answer to probe

#2

Could you try resetting the device when the log says : Please reset the device!
Let me know if how it goes :slight_smile:


#3

Hello @jbuusao,

it looks you registered and created the VM, but did not virtualize the board.
Have you clicked on “virtualize”?
Let me know :slight_smile:


#4

Yes I have reset (twice) the device . Just forgot to insert the comment. Nothing happens, the problem seems to be on falure to virtualize


#5

LorenzoR, what I did this morning was to start over: 1) register again, 2) reset, and 3) virtualize. But virtualize does nothing

Loading settings...
Switched to auto mode
Ready!
Ok
Checking for updates...

// Re-register the device

[info] Starting device registration
[info] Burning bootloader...
[info] Burning bin
Does D:\hexiwear.bin specify a file name
or directory name on the target
(F = file, D = directory)? f
C:\Users\(username)\zerynth2\tmp\tmprf55cq3l\tmp.bin -> D:\hexiwear.bin
1 File(s) copied
[info] Please reset the device!

// Reset the device

[info] Chip id retrieved: 92007005501354e4ffffffffffff9100
[info] Device Hexiwear (Docking Station) registered with uid: Ybh7MjQjRimxVblZJBE04g
Registration successful! Now you can virtualize your hexiwear

// Virtualize:nothing more displayed after this

Also note that the console repeatively emits the following:

92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100
92007005501354e4ffffffffffff9100

Why does virtualization fail?
Thanks for your support!

JP


#6

Case closed. I could virtualize (and then uplink to the device) after re-creating the VM.

Thanks,
JP