This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Issue with using MSP GANG programmer and dedicated .dll

I'm using 4 programmers to flash 12 sets of two types of MCUs operated by .NET application. I encountered software freeze on this method:
Set_MCU_Name(String name).

To my understanding, if I choose incorrect MCU model, i should get error code back;

Had anyone similiar problem, when dll method froze on execution, instead of sending out error? 

Also, programmers have firmware up-to-date and I'm using latest release of DLL.

  • Hi Eryk,

    I am taking your post and forwarding your issue to the MSP-GANG tools team to see if I can get more information about this problem you are experiencing. Thank you for your patience and please keep us posted if anything in this post changes or you acquire additional insight into your issue.

    Best regards,

    Matt Calvo
  • Hello,

    In order to recreate the issue you are seeing, could you post a stripped down version of your application and workspace so that I can run it on my version of Visual Studio to see if I can recreate the hang-up on my MSP-GANG?

    Best regards,

    Matt Calvo
  • Hi Eryk,

    Thank you for using the MSP-GANG. First - the firmware version inside the MSP-GANG must be always the same as the DLL version. If it is not the same then some problems can be observed. Please run the full package (GUI and DLL) and if the versions are not the same, then the pop-up message will be displayed prompting you for upgrading the firmware inside the MSP-GANG.
    When you have the same versions of the DLL and firmware, then now you can run the dll and MSP-GANG. By default the software we provide is prepared for one MSP-GANG. If you would like to control more than one programmer from one PC, you should create the new entry for USB driver. In the Device Manager you must see e.g. 4 programmers in your case. By default - you will see only one programmer (the first plug-in MSP-GANG to PC). That will not allow you to control more that one programmer. You should run GUI one by one with all MSP-GANG you have and in Setup->Preferences modify the default USB ID (USB-ID number) and set different ID for each MSP-GANG. If it is done, then plug-in again all MSP-GANG to PC, then you will see e.g 4 MSP-GANGs under Device Manager. Now you can get access to all MSP-GANG separately. Then you should create your software for getting access to all MSP-GANG separately. You should create 4 independent instances - one for each MSP-GANG. Then your top level software should use separate threads to control each MSP-GANG separately. If all done, then you can do your task you asked for.

    Let me know if you have any questions,

    Best regards,
    Gregory Czajkowski
    Elprotronic Inc.

  • Hello,

    If Gregory's post helped you to solve your issue please go ahead and select "Resolved" so we can close this thread out.

    Thanks and best regards,

    Matt Calvo
  • Hi Gregory,

    to be honest, that was already my approach- I am using .net Tasks to achieve concurrency (like starting programming at the same time). I choose not to use SetConfig to set type of MCU.

    So far I encountered one more problem;  when trying to get result array after programming from programmers and using tasks for that, in compilied version of my app I got empty array, but when running it from IDE debug mode, I could collect it; maybe it is some timing issue, collecting these arrays one by one solved the problem. 

  • Eryk,

    Gregory may be able comment on the difference in performance between running the application in debug mode versus the compiled normal version but that is good to hear that collecting the arrays one at a time was able to solve the problem!

    -Matt

**Attention** This is a public forum