Matrix user forums

Hi MM Team,

Does Flowkit work with:

1) ECIO-40P

2) ECIO-ARM40P

3)dsPIC/PIC24 via EB-064

Is there any other way of using ICD mode and Flowcode without flowkit?

many thanks

best regards,

Pete

FlowKit works with all those devices.

The only other way to use Flowcode's ICD feature is to use the EB006 (v7 or later) which has this built in.

Hi Steve,

thanks for the fast response.

This brilliant news as I have both EB-006v7 and flowkit...

I'm a very happy man...

Thanks

Best regards

Pete

Hello,

The EB064 has the ICD built in too

Hi Ben,

I am currently using an EB – 064 working with dsPIC 30F3012, using the latest version of dsPIC flow code software.

I was attempting to do some debugging on the hardware around the EEPROM, read/write function and I don't seem to be able to write to the EEPROM i.e. the value does not get stored and is lost on powerdown. Not sure if there any known issues here?

My question is around ICD mode with EB 064. I have selected ICD mode and have successfully compiled to the chip using the default settings. When I run the program I get the error message back that the target device cannot be found, 1st line of code should be etc etc etc . Are there any special tricks required to make ICD mode work on an EB 064?

Best regards

Pete

Hello Pete.

Have you tried an EEPROM address other then 0 I seem to remember there was a problem with storing data at address 0 on some devices.

Also with your ICD problem the main reasons this is not working are:

a) you are using the ICD pins somewhere in your program.

b) the clock speed setting in the project options window is not right for your hardware. Can you do a 1 second LED flasher test with ICD switched off to confirm that this is set up correctly.

Thanks Ben,

Your guess was correct, I'm using address location zero.. The code appears to be ok as it simulates fine.....will try an alternate location.

As with ICD, thanks for the clues, Will investigate further and come back to you...

Best regards

Pete

Thanks Ben,

You where spot on with the clue on the EEPROM location, ADDR 0 does not store data in my example, disPIC30F3012. Moved to ADDR location 1 and problem solved. Is this a bug, do you know what the cause of this behaviour?

As for the ICD, pins (all of port B) are used by the hardware application. Attempted to move to port C, RC 13 thru RC15. Tried the 'Over-ride ICD pin' option and can only select 5,6,7 - not 13, 14,15... appreciate your thoughts on this..

Thanks again for your assistance,

all the best

Pete

Hi Pete,

I seem to remember first coming across the EEPROM bug on the Microchip forum. I believe it is a bug in the EEPROM silicone but I could be wrong on this.

When you are selecting the port is it PORTC_H because if it is then pins 5, 6 and 7 should actually refer to the PORTC pins 13, 14 and 15 you are expecting.