Bossa Program Port?

[Eje_G]

Hmm wonder if I did something wrong somewhere...


Had some issues getting the new DigiX board recognized at first, had downloaded the 1.5.4beta and couldn't get the board recognized until I installed the DigiX USB drivers. Tried to program a simple example sent it to the unit and got a error message (of course didn't save it). Tried again just to get msg that the device wasn't there. Power cycled , unrecognized and so it went a few times all sudden I got "Bossa Program Port" detected and it installs fine as com5. But can't send program to this port "no device on com5".


Downloaded 1.5.3beta and installed it instead after it did a re-install of the DigiX USB drivers. Well the port I get is still Bossa Program Port. Did my unit somehow lose it's bootloader? Or is it just somewhere the wrong driver is still being pulled in from old install or something?


Was so excited to try a simple WiFi web server. But can't even load on the simplest program at this point. Sure I screwed something up but not sure what or how to fix it. Never had anything like this with my Digispark units, sure occasional issues programming them but nothing that a usb unplug/re-plug wouldn't fix.


Windows 7 Pro 64bit, 8GB ram, plenty of HD space.


Going to try a different machine but probably will not be until way later tonight or tomorrow at the earliest.

[digistump]

First it is showing up as the Bossa Program Port because it has reverted (for some reason - possibly the error, which can be caused by a bad cable or other things) to the built in bootloader - which isn't a problem - make sure you have Boards->DigiX selected and then make sure you have selected the com port from Tools->Serial Port


If that doesn't work and if you ever get stuck where you can't program it/it won't show up it is because something has killed the software bootloader (usually code that crashes the DigiX or error uploading) - there is a fail safe built in by Atmel for this - while the DIgiX is powered on (over usb is fine) press and hold the Erase button for a few seconds, then press the reset button - the go reselect the port from the serial port list (sometimes this makes it change its port) and if it doesn't appear at all in that list try disconnecting and reconnecting - the erase reset procedure, though rarely needed puts it into the hardware factory bootloader (Bossa Programming Port) so that code can be uploaded even if the soft bootloader was broken. This is very different then the AVR chips like regular Arduinos, but a saving feature with these chips (Arduino implements it as well on the Due).
 
If you want to buy another beta/beta bonus shoot me an email, I have a few extras - support @ digistump . com

[Eje_G]

Alright I probably did unwittingly do the erase button/reset steps, one my machine at home the unit came up as Bossa Program port but I could load a program onto it.
Than after reset it would come up as unknow device. But the program would be running. So I hard set the driver for the port to "Arduino USB serial light adapter" and monitor serial and flashing works very nicely now without doing erase reset steps.


Phew.... alright time to start playing.


Tomorrow I will try the same thing on my computer at the office to see if I can't get it to behave.


BTW. The DigiX USB driver for windows, the 32bit bat file points to same file as the 64bit and when you run it on a WinXP machine you get a error that it's not a valid 32 bit app. The x86.exe file either ran as stand alone or through bat file with /se fails to install the driver. Tried it on a test laptop I had handy at the office before I left and couldn't get your usb driver installed on this old WinXP 32bit machine.


will be sending an e-mail in a little bit, dinner time..

[RicM]

I saw something like that pop up from my system tray during my many attempts to get the board recognized. I didn't think anything of it. Now I wonder. I received mine on Saturday and the internal antistat bag was beat to &%$# inside and the the single row headers are loose. I wonder if something was damaged in shipping. I am hoping to get a hand getting this up and running and am excited about it. I am glad posted that message as it reminded me of something I just didn't pay attention to.

[digistump]

@RicM - the Bossa port coming up would not be any indication it is damaged - that said if it is damaged to the point you'd like a replacement please do let us know ASAP (support @ digistump dot com)


@Eje_G - I'll try to get the 32 bit driver fixed (obviously I'm on 64 bit) - thanks!

[Eje_G]

@digistump my main systems are all 64bit as well but since I didn't get it working on my main machine in the office I gave it a try on that old beat up 32bit machine. Otherwise I wouldn't have discovered the issue.


@RicM try to follow the erase / reset steps outlined by digistump here then load on say example sketch 01 Basic -> Bare minimum which should get your board in order. Once it been programmed and you to get a "unknown device"  after the unit gotten reset go into the device manager locate the unknown device Universal Serial Bus controller. Right click -> properties, go to driver tab click update driver -> browse my computer for driver software -> Let me pick from list of device drivers -> uncheck show compatible hardware -> locate Arduino  in the list and select the "Arduino USB serial light adapter"   (or you might have a Digistump if so select it instead)
[/size]
[/size]Still having problem, try a different usb cable, seems that my main problem at my office might be related to my usb cable, because it wouldn't start working right even after I done the above (couldn't write to the board) until after I swapped the cable, the original cable I used seems to work perfectly fine with my Android phone (not using external power but rather USB power, but not sure if that have anything to do with it) .

[RicM]

Thanks - I think I'm good now.  The headers are still loose.  It is most likely just the plastic bits wiggling, and not the pins themselves - just that other boards don't have that.  And since it looks like USPS beat the snot out of it, I was a bit concerned.  But I think it's OK.
Thanks!

[emcniece]

FWIW, I *just* ran into this problem after months of flawless operation. The DigiX had been sitting in a box for a week or so, I guess it felt unappreciated

The erase/reset/driver update worked fine.

[defragster]

My Digix New and installed software (1.5.5, \hardware copied, x64 drivers) after I plugged it in to my Win 7 x64 machine.

Seemed like it was going to work - midboard LED stuck on like loading failed.  Port then came up undefined/unknown as in this thread - repeatedly.

I did Erase/Reset and then hit Program with no driver re-install - it seemed to find it's own. As com12 first upload then dropped on reset to com13 then stayed at com13 [Digistump DigiX] and uploaded two variants okay so far without dropping again.

[defragster]

I take it the Atmel bootloader reversion is undone on the next upload and no functionality changes from DigiX features after that?

I noted in another USB Port thread that I made a 'fast loop' the programmer couldn't interupt - unless is was 'out to lunch' from the hyperactivity - this erase/reset looks to be a very handy thing to know.

[TimO]

I hadn't even realised that it came up as "Digistump DigiX", although having just checked it, that's what it displays now.

The first (and only previous) time I looked at Device Manager, was when I was having problems with gaining access to the board, and it said "Bossa" at that time.  I'd guess this was just after I'd hit the Erase button, in a failed attempt to get the WiFi settings back to the Factory configuration.

Interesting to see that there's this degree of failure recovery.