jsobell 0 Posted July 2, 2005 Report Share Posted July 2, 2005 Hi, I'm struggling to work out how I can program my in-circuit PIC18 from the command line via the Olimex ICD2 compatible board. It works fine with MPLAB, but is there any info around on integration with SourceBoost IDE? Am I missing something in the RTFM department? Cheers, Jason Quote Link to post Share on other sites
MadsenCircuits 0 Posted May 8, 2007 Report Share Posted May 8, 2007 I am having the same problem. I would like to use SourceBoost instead of MPLab to program my PIC devices however I cannot find a stand-alone program to point to in the "Settings->Options...->Tools->Programmer" setting. Did you ever find a solution? Quote Link to post Share on other sites
emte 0 Posted May 8, 2007 Report Share Posted May 8, 2007 (edited) Use MPLAB and Import the Hex file when you program with the ICD or ICD2 is what i do. There is also ICDPROG which i have been meaning to try in windows, but i have my doubts as it is VERY OLD. ... hmm maybe i'll give it a spin right now and see... if it does work it will be trivial to add programming support for it in SourceBoost. Edited May 8, 2007 by emte Quote Link to post Share on other sites
emte 0 Posted May 9, 2007 Report Share Posted May 9, 2007 Well ICDPROG does work ... just not with a plain hex generated by SourceBoost+BoostC. The hex file generated is missing the config word, this means you need to use an extra flag and manually set the config word for your device. So it is user beware, i will play around with it a bit more now and see what i can do. Quote Link to post Share on other sites
Dave 0 Posted May 9, 2007 Report Share Posted May 9, 2007 emte, The hex file generated is missing the config word, this means you need to use an extra flag and manually set the config word for your device. <{POST_SNAPBACK}> Add #pragma DATA _CONFIG, xxx to the source code. Regards Dave Quote Link to post Share on other sites
emte 0 Posted May 9, 2007 Report Share Posted May 9, 2007 Yeah, i was looking at that and trying to determine the effect of distilling #pragma DATA _CONFIG1H, xxx . . . #pragma DATA _CONFIG7H, xxx into the single one. i am suspecting i will have to remove the large block... emte,The hex file generated is missing the config word, this means you need to use an extra flag and manually set the config word for your device. <{POST_SNAPBACK}> Add #pragma DATA _CONFIG, xxx to the source code. Regards Dave <{POST_SNAPBACK}> Quote Link to post Share on other sites
emte 0 Posted May 10, 2007 Report Share Posted May 10, 2007 Well i have hit a snag ... i am not sure what ICDPROG is looking for ... AKA i have yet to figure out why it is complaining about a missing config word. I am trying to compile something in MPLAB for the 18F4620 and see what it generates for the ICD config word. Quote Link to post Share on other sites
emte 0 Posted May 10, 2007 Report Share Posted May 10, 2007 (edited) AHA ... i need to read more next time ... as it stands ICDPROG only works for 16F series devices. i am going to see if i can figure out how to modify it for 18f ... as soon as i get some time. The changes look trivial to add more chip support, but it is based on series/families ... If i can figure out how to make mingw32 behave ... Edited May 11, 2007 by emte Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.