Page 1 of 1
Compiling for 16F505
Posted: Sun Jul 16, 2017 5:35 pm
by lgdruyte
Hello,
I have problems with compiling for the 16F505.
I'm not able to compile even an empty program.
- Error message
- Knipsel.JPG (20 KiB) Viewed 4945 times
- Program
- Knipsezefazefazefazefazefql.JPG (9.88 KiB) Viewed 4945 times
I use the default compiler settings.
- Compiler settings
- zezsel.JPG (47.91 KiB) Viewed 4945 times
i have no problems with other microchips.
Does anyone know what's going wrong.
Thanks in advance,
Lucas
Re: Compiling for 16F505
Posted: Sun Jul 16, 2017 7:51 pm
by EtsDriver
Hi!
Could you try these files and see does it help? I put the backup files there too, if it doesnt help.
Changelog:
Code: Select all
CAL\internals.c: line 71, see comment on line 70.
FCD \PIC\16F505.fcdx: line 70, see comment on line 69.
Flowcode will still give you a reminder about the low ram mode:
Code: Select all
C:\Program Files (x86)\Flowcode 7\CAL\internals.c:
75: #warning "String temporary variables not defined to save on limited RAM space on your current target device"
(162) #warning: "String temporary variables not defined to save on limited RAM space on your current target device" ^ (warning)
I cant say its bug free. I think the Port definitions need some work too...
Code: Select all
82: FCV_TEST = (FC_CAL_Port_In_DDR__x((&PORTC), (&TRISC), (0xFF), (0)));
^ (1418) attempt to read "control" qualified object which is Write-Only
(908) exit status = 1
(908) exit status = 1
Re: Compiling for 16F505
Posted: Sun Jul 16, 2017 9:38 pm
by Benj
Hello,
I think I fixed this problem a few weeks back but haven't posted it yet. I'll get it up on the forums for you tomorrow.
The device has very limited resources so no string manipulation using the current buffer. The io is also more like a 10f than a 16f with a command for the tris rather than a register.
Re: Compiling for 16F505
Posted: Mon Jul 17, 2017 10:35 am
by Benj
Hello,
I've now posted all the latest updates here which should solve the problem for you.
viewtopic.php?f=63&t=18760
Let me know how you get on.