I've tried windows and installed the 3.4.3 upgrade for the C18 compiler (only available for win) and it is working with the PIC18F25K50 (but the dot is yellow and not green, dunno what this means)
I've received a few PIC18F25K50 samples and wanted to play around with them. I must say, i'm bloody new to PIC MCU's.
I'm running archlinux and installed the following software:
- MPLAB X 1.4 - XC8 1.1.0 - C18 3.4.0
So, everything is running fine till here (except some path problems with this "plib", but i have solved them already), But the trouble starts when it i want to start a project for the PIC18F25K50. I can't choose the C18 compiler (i believe my version doesn't support it yet). But i can choose the XC8. It creates the project and i can use the needed headers.
Now things went strange:
there is a common library and a huge set of headers for i2c,spi,pwn and so on that is namend "plib". But it seems that it also doesn't support my chip. the lib for it is missing and i can't even set the essential config (FOSC etc.) because it wasn't found.
i tested all with the PIC18F2550 and everything is working there, so my basic setup should be ok.
Does anyone of you has experiences with that chip? and more general: is MPLAB and the compilers from microchip the way i should go or is there any secret jedipath for PIC developement?
Oh, and there is a new version of the C18 (3.4.3) but the upgrade is only available for windows :-/
Please throw every tiny tip in here, i'm sure i can need it ^^
i've started the howto series about avr-cdc and begun to make a seperate post for each chip variant (attiny45/85,attiny2313 and atmega8). There is currently only the attiny45/85 post finished.
Now my question for you: would it be nicer to put all the chips in one post or is it ok to have three different posts for each chip?
i have also decided to don't put work into the attiny2313, because you can simply use the 16 and 20 mhz version from the original firmware, this gives you cts, rts and dtr. dtr is on pin5.
iam currently writing a detailed tutorial for using avr-cdc with several chips. yo can find all my veryfied .hex files on my blog and github repo in the next days (when my tut is also finished).
I want to reuse my attiny85 running the avr-cdc firmware for my next DIY Arduino, but this time it would be nice to have the autoreset feature onboard (pressing reset for uploading sketches sucks sometimes). So i've started to hack the DTR signal into the avr-cdc firmware for the tiny chips. It's currently working for the tiny85. in the next few days, i will upload the missing bins for tiny45 and tiny2313...
I've also made a walkthrought for all the code changes i've made.
oh, since iam the only person so far that have tested my code, it would be great to get some feedback if someone discovers a problem ;-)
------------------------- Edit ------------------------- You can find the tiny2313 code in my github repo, it provides you the DTR signal when you run this chip @12Mhz
@vimark: i have tried this already, but when i have the component in position, it realigns back on the new position.
@markus: the smallest Trace i`m using is 0,3mm, i can`t get it thicker because of the LQFP pads (0,3 matches perfectly for them) for the other ones i use 0.4mm and 0.6mm for VCC. I think i can make these 0.4mm a bit thicker.
you are rigth, i have placed a few components and then started routing :-) i tried to avoid traces on the bottom as much as i can.
The alignment is a strange problem atm. it seems that some components dont`t want to match the grid ö.Ö. But i will research that in the Eaglecad documentation.
