chiplist 24EP.. and 33EP

[saschech@gmx.de]

Hello

To day i become newsletter from elektor, (Flowcode 5 ab sofort auch für dsPIC/PIC24 verfügbar! )
what chiplist is legally?

Regards Wolfgang

[saschech@gmx.de]

Hello

With other word`s; in the pro version flowcode ds-pic and pic24 for the big EPchip`s no support?

Regards Wolfgang

[kersing]

Does the picture below (from the release version of FC5 for PIC24 and dsPIC) answer the question?

cutting.JPG (47.96 KiB) Viewed 9105 times

[saschech@gmx.de]

Hello kersing

No! because: I have diverse probleme with the "big chips"

In the new literatur (news from elektor for dspicv5),there are these chips not in the chip-list.......

http://www.elektor.de/Uploads/Files/Pro ... ooklet.pdf

So I think it is important for me because I want use these cips!!!!!!!!!!

I learn intensive c with microc for have a comparison and have not these problems....code is running on my hardware ok.

The c code inside mplab with c30 compiler >>>> I have also probleme with the "big 24 and 33EP chips"

Regards Wolfgang

[kersing]

Wolfgang,

If the chips would not be supported you would not be able to select them (imho). However, there might be issues with the chips that need resolving.

It is not clear to me what you want to tell us with the screen shot. Perhaps you could clarify?

Best regards,

Jac

[Benj]

Hello,

There seems to be a few kinks with the EP range of devices though they do look fantastic, I have done my best to support them thoroughly for the dsPIC release. They are supported by the release version of Flowcode 5 for dsPICs and I have been able to get one fired up and running using a PICkit and the Microchip explorer board. We are about to do some extensive development using one of the EP chips so hopefully we can use this to try to iron out any outstanding bugs. Wolfgang, if you keep reporting bugs as you find them then I will try and sort them out for you. Is the config still not working correctly using the release version of Flowcode? As you were in the Beta it might be worth while uninstalling and ensuring you delete the entire Flowcode dsPIC folder from your program files before reinstalling to ensure all the latest files get installed correctly.

PS. I'm going to be in Dortmund in Germany for Elektor live on Saturday if that's anywhere near to where you are.

[saschech@gmx.de]

Hello Benj

Thanks for the open words.
The "config problem" is the thame as in the beta (only the big case 24EPxx810 and 33EPxx814).
The ADC dont work on hardware.

Go to dortmund is to expensive for me......münchen or stuttgart is mutch better....

Thanks and regards Wolfgang

[Benj]

Hi Wolfgang,

Ok its a shame I don't get to see you and have a chat but Germany is a big country and you'll probably also have to pay to get in so I understand. The chip I have chosen for our design is the 24EP512GU810 device so hopefully this should be good enough to eliminate all of the problems.

I will have a look into the config and ADC issues this afternoon and see if I can get anywhere with them.

[saschech@gmx.de]

Hi,Benj

Any news about my "config problems with big EP chips"?


regards Wolfgang

[Benj]

Hi Wolfgang,

I have a 24EP256GU810 device soldered onto a prototype PCB now (24EP512GU810 devices are on back order). I'm currently having issues getting the PICkit3 to see it but hopefully I can resolve this.

Once I have this up and running it should be a good test bed to try and work out the config issues. I'll have a play this weekend and see if I can make any progress.

[Benj]

Hello,

I think this has now been resolved. Looking at the problem it seems that some of the config settings were phrased in a misleading way. Therefore I have been through and given clearer explanation and the device is now running correctly from the Flowcode config settings. There was also a config bit which is marked as don't care in the datasheet but it seems like it does actually care so I have changed this to match the way MPLAB does things.

I still have to unplug my PICkit 3 when programming via Flowcode to allow the program to run so I will be looking into this issue next.

[Benj]

Removing the -E -M from the PICkit command line parameters allows the device to run with te PICkit connected but the PICkit no longer erases and reprograms.

Therefore I think I will just have to keep plugging and unplugging the PICkit for now.

Edit I fixed it but it took a bit of digging.

Programmer Location: C:\Program Files (x86)\Flowcode(dsPIC)\v5\Tools\PICkit3\pk3cmd.exe
Parameters: -P%p -F%f.hex -E -M -L

[saschech@gmx.de]

Hello Benj

I test to morrow .

for start after programming I found:
http://www.matrixmultimedia.com/mmforum ... 471#p41649

Regards Wolfgang

[Benj]

Hi Wolfgang,

Aha, ok yes that solves the problem thanks.

I think you have already done this but here are my PLL settings for getting the device to run at 70MIPs using a 4MHz crystal and the XT + PLL config setting.

Code: Select all

CLKDIV = 0x3000;
PLLFBD = 138;

[saschech@gmx.de]

Hello Benj

Unfortunately the "config" dos not work on my 24ep512gu814 board.
I test 24ep512gu810 later....

(If i sent 1-time "my config.hex to the ship" all is ok )

Regards Wolfgang

[Benj]

Hi Wolfgang,

I think I found the issue. One of the config settings in PPP was worded very strangly and I think both me and you must have been setting it to the wrong value which was disabling the output oscillator pin and stopping the oscillator from running. I have been through and re-worded the configs and hopefully the Flowcode config settings will now behave correctly.

Config setting - OSC2 Pin Function bit

I was using Enabled but the correct setting to get the crystal to work is Disabled.

I have reworded Disabled to this - ClockOut Enabled I/O Disabled
and Enabled to this - ClockOut Disabled I/O Enabled

[saschech@gmx.de]

Hello Benj

I think,in my case these is not important,because i work without a quartz; I use the internal hs with pll mode at beginning work with the ep chip`s..

Regards wolfgang