Hi Seb,
On 2013/08/16 10:42, Sebastien Lelong wrote:
Here my confirmed test results:
- 2.4o + latest device: same behavior (not working, as explained
before). But as you said, this may not be a valid combination.
- 2.4q + latest device: same behavior
- 2.4q + latest *test* device (from MPLAB-X), with minimal pragmas
changed:
pragma target SOSCSEL HS_CP
becomes:
Compilation gives strange warnings:
projects/jaluino_bee_powermeter.jal:319: warning: data error at 0x0000000a
projects/jaluino_bee_powermeter.jal:319: warning: data error at 0x0000000e
Line 319 is the end of the program.
Please report to Kyle (directly or in Jallist).
I have also had a similar message ('branch error'), with one of the ADC
samples when the device file contained (erroneously) ADC_ADCS_BITS = 0.
The msg went away with ADC_ADCS_BITS = 3, but the message is still
strange and I don't believe the 2.4q-beta is working properly in all
situations.
Results: nothing, PIC gets stuck, I don't even have my welcome I'm alive
message.
Sounds more like a compiler issue than a device file issue.
BTW I'm currently looking at the default fuse settings and stumbled once
again on contradictions in the Microchip docs. The datasheet of the
10f200 says
> bit 11-5 Unimplemented: Read as ‘0’
but the programming specification of the 10F200 says:
> bit 11-5 Unimplemented: Read as ‘1’
Both docs have been revised several times! How can one ever get proper
default settings in the Jallib device files?
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/groups/opt_out.
