-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firmware, hardware, core versions #16
Comments
@bruno-f-cruz suggested testing the latest ones in release first. Given the detected hw versions in bonsai or cmd window cannot be trusted, we just need to trust the physical print on the board? (or is there a function like "factory reset"?) |
Hi, Please use the attached firmware for the devices. This release will be a major one and will fix known issues and add funtionalities. Replying to your questions:
Cheers, |
Thanks @filcarv . We will try them for now.
Great. Will it be appearing in "release"? Once public, tagging this thread would be great (and then can be closed). |
Hi @filcarv , We have tested the firmwares received. In a nutshell, some success, some errors. 1.Most of the hw=v2.2 board worked with 2.How exactly are we supposed to bootload PIC32 firmware? As the soundcard (not the main micro-controller that has a corresponding COM port) is recognised as an USB device not a COM device, it's impossible to use the CSVconverter for targeted uploading...? Thanks. |
Hi @hagikent Replying 2 for now. |
Hi @filcarv Thanks. That's what we have been doing, good to confirm. Last Oct, Helio and I contacted you claiming that SoundcardGUI basically doesn't work in our new experimental PCs with tons of .vi error messages. This has not been solved but I switched to using Bonsai to upload sound waveforms, practically, circumvented. I found that firmware updating doesn't works in those PCs that cannot run SoundcardGUI too. We are in touch with our IT to check if this labview incompatibility may be due to their security policy. Thanks, |
Hi @filcarv Our IT (@dorkfest1 @rachelmizuta) spent some time investigating this issue and concluded that Intel i9 CPU would be the cause. We AIND-behavior team have purchased >30PCs with i9 for behavior experiments and all of them cannot run those labview-based software.
any update on this? Best, |
Hi @hagikent , That can be a good explanation for the issue. The software was compiled some years ago with an old LabVIEW version (v 2010, I believe) and it may not be compatible with recent processors. Can you try to run it in Compatibility mode with a previous Windows version? Can you also check if the next folders exist on your computer? Best, |
@glopesdev @artursilva0 @filcarv
Hi Neurogear/OEPS team,
We AIND behavior team received several different versions of soundcards - 1.1, 2.1, 2.2, and wondering if which Firmware version we should use. We need to make them identically work in our dynamic-foraging task. (https://github.com/AllenNeuralDynamics/dynamic-foraging-task)
Earlier, we (@XX-Yin ) seems to have received only the one for v2.2 (
SoundCard-fw2.2-harp1.13-hw2.2-ass0.hex
), and thus, not sure what firmware we should use for others (v1.1, 2.1).We have tested
SoundCard-fw2.0-harp1.4-hw1.0-ass1
andSoundCard-fw2.0-harp1.4-hw1.1-ass0.hex
which come with CSVconverter software, but this software seems to be buggy. We encountered that this operation changes hardware version as well, which I assume a fixed parameter.To summarize:
Tagging some relevant colleagues here:
@jsiegle @ZhixiaoSu @HeRodrgues @bruno-f-cruz
Thanks,
Kenta
The text was updated successfully, but these errors were encountered: