RedBear BLE Nano v2 - fatal: bad revision 'HEAD'


#1

Hello, I have problem with my first uploading program to RedBear BLE nano v2. I just want to blink LED on port D0. If I compile the program I get:

[info] Compilation Ok

But if I try to upload I get this result and not working BLE:

[info] Compilation Ok
fatal: bad revision ‘HEAD’
[info] Searching for device 5f98e140c533039f0a3550111b1233afb7ab7bd6 with alias zs:redbear_nano2:5f98e140c533039f0a3550111b1233afb7ab7bd6
[info] Please reset the device!
[info] Searching for device 5f98e140c533039f0a3550111b1233afb7ab7bd6 again
[info] Probe sent
[error] No answer to probe

I removed the device and try to get registratian and virtualization again and I get this info:

[info] Starting device registration
[info] Burning bootloader…
Does F:\redbear.bin specify a file name
or directory name on the target
(F = file, D = directory)? f
C:\Users\pavel.janecek\zerynth2\tmp\tmpp4vi240z\tmp.bin -> F:\redbear.bin
1 File(s) copied
[info] Chip id retrieved: 0a3780df1a8d0cca
[info] Device RedBear Nano 2 registered with uid: 1iNY5BjXSN-VevKDuClp2g
Registration successful! Now you can virtualize your redbear_nano2
fatal: bad revision ‘HEAD’
fatal: bad revision ‘HEAD’
fatal: bad revision ‘HEAD’
[info] Starting Virtualization…
Does F:\redbear.bin specify a file name
or directory name on the target
(F = file, D = directory)? f
C:\Users\pavel.janecek\zerynth2\tmp\tmp5zsbl2qc\tmp.bin -> F:\redbear.bin
1 File(s) copied
[info] Virtualization Ok
Device Virtualized
fatal: bad revision ‘HEAD’
fatal: bad revision ‘HEAD’

If I manually check the F:\ directory, there is no such redbear.bin file.
Thanks for any ideas.


#2

Hi @pavel.janecek,

have you correctly reset the device when asked during uplink?
Have you tried again to register and virtualize?


#3

Sure I did. But the I figured out, it is not connected with the device and I get the message “:fatal: bad revision ‘HEAD’” even after startup of the program.
Is it possible, there is conflict with our company GIT settings?


#4

Hi @pavel.janecek,

the fatal: bad revision ‘HEAD’ is definitely a git error message which may be caused by nested git repos, anyway it should not compromise the correct execution of the project.

The device seems to be correctly registered, since the device uid is retrieved, and virtualized.
The redbear.bin file is not present because the it gets written to the flash of the device and then deleted.

The strange fact is that when uplinking the studio is not receiving any response from the device.
When asked for reset a single click on the reset button should be enough and you should see the LED blink a few times to signal VM reset. Do you at least see the LED blink?