Open ArefUni opened 3 years ago
Since you previously indicated that Pixelpulse2 works I'm not sure what could be causing this. I obviously can't reproduce this error on any of my systems (nor have we had other users report the same symptoms). This may well be something very specific to your system.
By the way it would have been helpful if you had scrolled up (or expanded) the command prompt window to show the first part of of the messages the software printed to the screen. There is some important stuff that was cut off.
Can you look in the Windows Control Panel under (Un)Installing Programs at the list of installed Analog Devices software to see if you have installed the Libsmu package, specifically the X86 version 1.0.3 as I show below:
If you do have this installed can you open a Windows Control Terminal console screen and with the board attached to a USB port type:
smu -l
If the smu command line utility was installed along with the Libsmu package you should see something like this:
In my case it listed the information for the Hardware revision F board and firmware version 2.17.
If you don't have Libsmu X86 package installed could you please to that using this download link:
https://github.com/analogdevicesinc/libsmu/releases/download/v1.0.3/libsmu-1.0.3-setup-x86.exe
Do not check the option box to load the 32 bit USB drivers (not necessary since you probably already have the proper 64 bit one). Do check the option box to add smu to the environment variable. If you have a copy of Python (32 bit) installed you might want to add those bindings as well for future reference.
Perhaps this test will shed some more light on what your system is missing.
I have the same problem. I did the smu -l test and the response is no device connected. At the same time the windows tray shows a usb icon identified as " ADALM1000 SAM_BA Winusb driver". When I unplug the ADALM1000 that icon goes away. My issue started when I updated firmware from ALICE. Lights went off and have not come back on. Pixelpulse says the 'device is in programming mode' and does not list any details on what it is connected to. Assistance appreciated.
If the board shows up as ADALM1000 SAM-BA in the device manager then use the smu utility to flash the firmware by first downloading the binary file from: https://github.com/analogdevicesinc/m1k-fw/blob/master/m1000.bin
Open the Windows prompt and navigate to where you copied the m1000.bin file.
Type:
smu -f m1000.bin
That should work. I have seen it fail on one Win 10 computer back when Win 10 first came out but as of today the problem went away with Windows 10 2004 and the current libsmu release.
Doug
Hi Doug, I did that. No joy. Attached is a document with screen shots of pixelpulse and the windows tray. I think the board is dead. Can I trade it in on a new one? Thanks, Marty
On 12/18/20, Doug Mercer notifications@github.com wrote:
If the board shows up as ADALM1000 SAM-BA in the device manager then use the smu utility to flash the firmware by first downloading the binary file from: https://github.com/analogdevicesinc/m1k-fw/blob/master/m1000.bin
Open the Windows prompt and navigate to where you copied the m1000.bin file.
Type:
smu -f m1000.bin
That should work. I have seen it fail on one Win 10 computer back when Win 10 first came out but as of today the problem went away with Windows 10 2004 and the current libsmu release.
Doug
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/analogdevicesinc/alice/issues/15#issuecomment-748109745
-- Martin O. Patton 7038 Lear Nagle Road North RIdgeville, Ohio 44039
I see no document? Just to be clear in Pixelpulse you have the Update Firmware button and clicking on that did not flash the firmware onto the board. Second the smu -f command failed saying it found no devices attached.
I've seen the latter on one of the four Win 10 computers I have access to but on that one Pixelpulse does work.
Since this seem to be a Pixelpulse / Libsmu issue can you post as an issue over where the programmers that support those packages will see it:
https://github.com/analogdevicesinc/libsmu/issues
And
https://github.com/analogdevicesinc/Pixelpulse2/issues
As to returning the board. That you would have to take up with the supplier / distributor you purchased it from.
I failed to attach the document. Here it is.
On 12/19/20, Doug Mercer notifications@github.com wrote:
I see no document? Just to be clear in Pixelpulse you have the Update Firmware button and clicking on that did not flash the firmware onto the board. Second the smu -f command failed saying it found no devices attached.
I've seen the latter on one of the four Win 10 computers I have access to but on that one Pixelpulse does work.
Since this seem to be a Pixelpulse / Libsmu issue can you post as an issue over where the programmers that support those packages will see it:
https://github.com/analogdevicesinc/libsmu/issues
And
https://github.com/analogdevicesinc/Pixelpulse2/issues
As to returning the board. That you would have to take up with the supplier / distributor you purchased it from.
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/analogdevicesinc/alice/issues/15#issuecomment-748479267
-- Martin O. Patton 7038 Lear Nagle Road North RIdgeville, Ohio 44039
Sorry, still not seeing any attached doc.
Hi, Future to our communication in EngineerZone in the matter of ALICE Deck Top 1.3 , which from your advise to sing up here to resolve the problem with Alice Deskt op 1.3.
However, I have attached more Screenshot from ALICE Deck Top 1.3 , which is showing errors (no device Plugged in).
look forward to hear from you.
regards
Aref