Joe,

I actually posted about this matter in the Microchip forums, and someone th=
ere told me he finds the datasheets to be more accurate and reliable than t=
he MPLAB Code Configurator (C code) output.  I also opened a case with Micr=
ochip support, but so far I've not heard a reply from them. =20

I'd also like to add that I found a glaring error on Microchip's YouTube Tr=
aining channel.  The following video is talking about the NCO, but at 14:43=
 & 15:46 it talks about NxPOL, saying just the opposite of what the datashe=
et says.

https://www.youtube.com/watch?v=3DbWHe_PBEPdU

That's why I've been searching online for days, trying to find at least a s=
nippet of known-good Assembly code that shows the NCO and CWG setup.  That =
would make me rest easier about my own code, which again you can see here:

https://cl.ly/0i091i3W2V3d

And a screenshot of the CWG Setup in the 16F1508/9 Datasheet is here:

https://cl.ly/38450I0z2r1N

Thanks,

James Wages



7/23/16, 1:00 AM, IVP <joecolquitt@clear.net.nz>:

    >Is it not important to follow the datasheet sequence for CWG setup?
   =20
    Generally modules or functions don't work if the d/s example isn't
    followed. I'm sure the C compiler knows what it's doing. I've tried
    to figure out C-produced hex files and rarely do they resemble how
    it would have been written in assembly


--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.