High byte port manipulation in CCS for a dspic

AlPicCss73 · Joined: 20 May 2015 Posts: 18

Hi all!

I'm all new to the CCS. Previously, I was on MikroC pro but because all of its bugs and errors that arise from nowhere, I decided to test another compiler. But CCS is is not a compiler as neat as Mikroc. Overall now I'm trying to deal with it.
The serious problem for me now, is that the function "output_x" just gives one byte of data but I/O ports are 16-bit and I couldn't find it out how can i change the high byte of the ports. I appreciate anyone who can help me on this.

Bests.

Ttelmah · Joined: 11 Mar 2010 Posts: 19499

Output_x, outputs the whole _word_ on DSPIC's, not just a byte.

Remember though that you need to give it a word.

If you look at the manual:

AlPicCss73 · Joined: 20 May 2015 Posts: 18

Thanks for your reply. Maybe I'm in a big mistake but in my CCS PCWHD 5.007 the output defining in the help comes as follow :

Ttelmah · Joined: 11 Mar 2010 Posts: 19499

Get a later compiler....

5.007, was before V5, started working properly. It was still beta at that point.

However do be sure you are giving it a 16bit value. Be explicit, and use an int16 (don't assume the defaults are right on such an early version) Seriously, 'no wonder' you are having trouble.

However, that being said, just tested on 5.009, which was the oldest version I have kept, and:

Ttelmah · Joined: 11 Mar 2010 Posts: 19499

A quick comment. You are sure you are running PCD?.

If you have (for instance) PCWHD (the IDE plus all the compiler versions), and you 'wake up' in PCH, the PCH manual gets displayed. Even if you then switch to PCD, it'll keep on displaying the PCH manual, though you are now using PCD. You have to select the larger chip, save, exit the compiler, and load it again, and then the correct manual gets selected.

I suspect you are looking at the PCM/PCH manual, where the size for I/O is 8bit. Reason is that even the 4.112 PCD manual refers to 16bit for the I/O....

The PDF manual does not though.

AlPicCss73 · Joined: 20 May 2015 Posts: 18

Yes! You were right. It was because of PCM instead of PCD, Thanks alot.

Ttelmah · Joined: 11 Mar 2010 Posts: 19499

and (of course), using the wrong manual version, won't have helped you get going with CCS!....

The way that manual switching "doesn't occur", is a 'pet peeve' about the IDE. It is really annoying if you are working on several chips one after the other, to suddenly find you have the wrong manual for the chip you are using.... :(

jeremiah · Joined: 20 Jul 2010 Posts: 1345

Moreover, at least with PCD, the online manual and the IDE manual do not always match (not typically conflicting info, but more so that one has functions/descriptions not found in the other).

Another tip is there are items in the IDE manual that are somewhat hidden (at least as of 5.044...haven't checked more recent). For example, #use pwm is an available directive but typing it in the index filter doesn't bring it up while doing a search for it does cause it to show up. There are other things like that that are found in search but not in the index, but that is the first one off the top of my head.

One of CCS's main weaknesses for me is the inconsistency in documentation (even the lack of detailed revision notes), but I will say I find the way it handles built in functions to be rather invaluable. My work likes to swap chips a lot, so cutting back development type on rewriting code for a new chip has been invaluable. Additionally, we have multiple coworkers who really aren't programmers (but are learning) who can dive right into some small projects because setup_timer1() is much easier to handle than trying to do all the corresponding bit/byte settings by hand.