Matrix user forums

The suggestion from an earlier topic posted on the Forum (Flowcode8 and E-Blocks2) was that with a certain Version and Build level of a Windows 10 computer, the mLoader software does not recognise the BL0080 Multi-programmer board and thereby ruling out the E-Blocks2 facility as a means of programming PICs. If that is the case, is there an alternative to using the BL0080 board for programming purposes with Flowcode8 or is it an incompatibility consigning the E-Blocks2 boards to the bin? It seems to me that if that is the case a 'health warning' might have been useful before spending the cash in the first place! Any one else had a similar problem?
Robert

Hi.
Many users use the PicKit 3/4 with FLowcode and as you will see on your BL0080 board it has ICSP6 pin connector to which the PicKit3/4 connects.
https://www.microchipdirect.com/product ... oaded=true

Hi Robert,

We should be able to solve the issue as Flowcode seems able to detect and communicate with the boards.

I'll see if I can raise the priority for this to be looked into. I'm guessing it is a dependancy or library that Flowcode provides but mLoader does not.

We can also likely offer a return and refund if you would rather not wait for a fix.

A PICkit 3 or 4 is another option but of course requires more expense and so is not ideal.

Hello,

We've had a go at the mLoader executable and hopefully got somewhere. Unfortunatley we don't have a PC with the issue to test on.

Please can you replace the mLoader.exe file in the "Flowcode 8/tools/mLoader" folder with the attached executable and see how you get on. Hopefully running the executable should now see the board.

Benj,
Thanks for investing some time in trying to resolve this mLoader issue. I reinstalled mLoader as you suggested. I tried it (EB0080 connected and recognised in Device Manager: USB). I tried clicking om mLoader but the 'red' logo appeared not the one populated with the chip details.
Running a Flowcode8 program (program to chip) resulted in the attached screen.
Robert

Hi Robert,

Thanks for your patience in helping us solve this problem.

Can you please download and unzip the following file into the "Flowcode 8/tools/mLoader" folder and run the mLoader_dbg.exe file: This exe should display a debug message when running when it is looking for the BL0080 and BL0011 E-blocks boards. Please let me know what the messages are when your E-blocks board is connected to the PC.

Regards,
Steve.

Steve,
Very grateful for your effort. I downloaded the mLoader file as you requested, put the Mloader_dbg into Tools then double clicked. The screenshots are what then followed. The third screenshot was the 'red' MATRIX MLOADER screen (unpopulated) and not reproduced here.
Are these the debug details you are seeking?
Robert

Thanks for the screenshots, Robert. I'll let you know when I think of the next step...

Hi Robert.

Please try the attached file and let me know what message you get. Plug your E-blocks board in first before running mLoader. Also, can you please upload a screenshot of mLoader once it has run and you have dismissed the debug message.
Thanks,
Steve.

Steve,
As requested, E-Blocks2 connected, mLoader_dbg2 installed and ran. One diagnostic captured (Diag3) then the final MLoader screenshot on completion (Diag6). Note: a second run resulted in a different end screen (Diag5). Can't explain that one!
Robert

Hi Robert,

I think I have a fix for you. Please try the attached file and let me know how you get on.
Regards,
Steve.

Steve,
I did as you requested. D-click on the mLoader (2) in 'tools' this time brought no subsequent MATRIX LOADER image. Nothing.
I then ran the Flowcode8, 'compile to chip' but this failed exactly as before with no path found.
Robert

Since I am affected by the same problem, I also carried out these tests on my computer.
I got the same bad results. An idea from a colleague was that maybe the cause could be the Intel 10TH Gen processors?

I'll have another look at this problem this morning and will get back to you both later today.

Hi all,

Here's another file to try, if you have the time...
Regards,
Steve.

Hello Steve,
Thanks for your perseverance and continuing support. This version of mLoader successfully on activation brought up the screen showing the 0080. I think that is success!
Launching Flowcode8 with a programme to use the 'combi' results in the earlier mLoader being accessed. How do I install mLoaderA to replace mLoader in the 'build programmer'?
Robert

Sorry Steve, I forgot to add the evidence of success!
Robert

Hi Robert,

Thanks for getting back to me.

You should be able to rename the existing mLoader.exe file (e.g. to mLoader_original.exe) and then rename the mLoaderA.exe to mLoader.exe, and then it should work fine through Flowcode as well.

Even if this all works fine for you, I would like to investigate a bit further so i can pinpoint the exact problem (as long as that's ok with you). Bear with me and I'll post another test application soon...

Regards,
Steve.

Hello Steve,
Over optimistic I am afraid. I have renamed mLoaderA as the new mLoader (as you suggested) but the Flowcode8 program continues to fail to find the path!
I am more than happy for your assistance to try to get to the bottom of this. Just very grateful.
Robert

Hi Robert,

I think the problem regarding the path is something to do with there being no 8.3 filename support on your PC. I will try to find the instructions to fix this shortly.

In the meantime, could you please download and run this file with no Matrix board plugged in and let me know what messages you see.
Thanks,
Steve.

Hi Robert,

Here is a link which will hopefully solve the 8.3 filename issue:
viewtopic.php?f=76&t=20336&p=89900&hili ... ame#p89900

Before you try this, you can check to see if this is the problem by downloading and running the attached zip file. Unzip it and run it with admin privileges (right click and select "run as administrator").
You should see something like the image below.

If you don't have text similar to that shown in the red boxes, then you need to follow the instructions in the link above.

Regards,
Steve.

Hello Steve,

I also tried the last version and it works. Both solo and with Flowcode8 together. Thanks for this solution. The test of the file mLoader_dbg3 without board resulted in the following message: Thanks again
Greetings from the EU and Lusatia

Steve,
The first exercise (dbg3.zip) resulted in 9 messages which I captured but got overtaken by your subsequent suggestion.
The second (8_3check.zip) led to the same text as you outlined in red.
Where do you want me to proceed from there?
Robert

Thanks @PHolz. I'm glad the new mLoader is working for you.

And that debug message is very interesting. I'll investigate further tomorrow...

Hi Robert,

Did you get a similar debug message to @PHolz? Specifically, the "vid_8087&pid_0ac2" part?

Regarding the problem with Flowcode, it looks like Flowcode can see the mLoader.exe file, but mLoader cannot see your HEX file. To easily fix this, you could make a new folder for your Flowcode programs near the root of the C: drive (e.g. "C:\MyProgs") and save your Flowcode project there before compiling.

Please let me know how you get on.