Device Editor Question

Al-- · Joined: 11 Jul 2005 Posts: 2

Using the device editor there are several fields that have to be filled in....
Such as Memory, Where is the Flash Type stated in the device data sheet?? Eg:
62x Style, Normal, 4 Bytes style, What impact will this have on compiled code?
The device Identification, where is this information available?

Any help would be greatly appriciated

Al.

valemike · Guest

Trying to edit a new device in would be very painful than just upgrading your compiler.

An alternative to the costlier PCW or PCWH is to get the non-GUI based compiler, i.e. PCB, PCM or PCH, and just integrating that with the MPLAB IDE that Microchip supplies for free.

This topic has an all too familiar tone. Cool

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

Part of the problem is that CCS supplies no help file or tutorial
on how to use the Device Editor.

I mean, Mike, if they supply it, they ought to tell people how to use it.

valemike · Guest

You're right. Last time I used PCWH in my former consulting position, I always kept upgrading the versions. Even then, I always used it like PCH, i.e. integrated it with MPLAB and just use Microchip's ICD-2. I never really looked into the Device Editor.

Now that i'm part of a smaller cash-strapped partnership, i just renewed my personal PCH subscription for half the price.

If in fact the Device Editor appears to be an invitation to configure parts that are not supported by the older version of PCW, I could see why someone would rather just edit that part in himself than renewing the subscription.

(I'm not pointing fingers at this original poster, but the past two weeks, we've had someone first complain it's not worth it to renew the compiler, then goes around practically phishing us for the current .h files. To post such requests for copyrighted source code is bad enough, but to post it on CCS's own website, that's a bit irritating.)

Al-- · Joined: 11 Jul 2005 Posts: 2

Hi Guys,

Thanks for all the comments good and bad! You all got back very quick to this!

I've found a really simple work around, my device is now supported.

I'll let you know if this really worked (dont want to give away my secrets {untill I've verifed them atleast.}) when the code is running on my target hardware.

Cheers

Al--