-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
But that is not free.
One step at a time. The configs seem to be the thing that give most folks the most trouble, then ADC, then timers. PicMultiCalc has the timer part covered.cncmachineguy
Wow! lots of intrest. I would like to point out while all the solutions presented seem to be great ideas for tending to the config bits, the goal is a total configuration tool.
Dave
Always wear safety glasses while programming.
Interesting thread. My 2c worth:
Looking back at a lot of posts from people starting with PICs the most common stumbling block is the port settings, especially with chips like the 12F675 which requires the ports to be set to digital rather than have them digital as standard. It would be useful to simply select the chip, select if you want ADC, etc and then click on the "copy code to clipboard" button like mr-e's pic calc.
Like I said, just suggestions... I'f what ever you guys come up with, if it makes getting started with a new chip easier I'm all for it
malc-c
Have you ever used this?
http://www.picbasic.co.uk/forum/showthread.php?t=11100
Dave
Always wear safety glasses while programming.
Dave, to be honest no !
I know DT has some useful utils / included files, but I've not used that one.
Often, where I gets stumped is when you want a selection of multiplexed pins on one port, you know, the first 4 pins analogue, the next two digital and the remaining something else
Those are the tricky onesand the remaining something else
I understand exactly,
To ANSEL or not to ANSEL...
Dave
Always wear safety glasses while programming.
Hi, Guys
has someone tried CCS, Flowcode, WIZ-C or The Cypress Psoc Express ???
Worth the look ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Hi, Dave
Those 4 "C" PIC compilers have really really nice advanced config Wizards ... BTW ... I forgave CodeWarrior " Processor Expert " for Moto ... euhhh Freescale processors.
May be CCS is the " Weakest " of all ( but one can add custom peripheral drivers ... shhhht ! ) ... and it's not so bad !!!
WIZ-C is really astonishing ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Alain,
Do any of them save the configs to code or do they modify the hex at program time?
Dave
Always wear safety glasses while programming.
Dave,
I don't know about the different software packages that Alain is talking about. But, in case that you might want to know the MELAB programmer software modifies the code at programming time. It does not include the PIC configs in the code that you are writting.
I downloaded the MPLAB C18 demo version and I will be playing with it pretty soon. I will let you if this "C" software has any tools to help you set the PIC configs.
Robert
"No one is completely worthless. They can always serve as a bad example."
Anonymous
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
A very small start.
http://wiz.mackrackit.cambs.net/
I will post a project log and any code used at the above address if anyone want to work on it.
If you have suggestion or code lets play. I will work on it as time permits.
Dave
Always wear safety glasses while programming.
Dave, you are awesome! I see you must be working from an older copy of mplab? I had to update in order to have support for 16f1946. If you want, I can send you my *.inc files.
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Ioannis sent the incs from version 8.5 .
I just have not moved them into the project directory yet, ooppss.
Thanks for the reminder.
Dave
Always wear safety glasses while programming.
i have 8.53. dont know if there is any difference
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Seems like I am always slow to upgrade. I will install 8.53 .
And I need to get one of those 18FxxJxx chips...
Dave
Always wear safety glasses while programming.
The Proton guys had developed something that did all the above and more. Unfortunately, I cant seem to find the installable anymore on the net.
And it could do only 16Fxxx.
The developed header was of course for the Proton, but could easily be adapted for PBP.
Regards,
Anand.
Seems that program has disappeared. I only found one thread mentioning it on the Proton forum. Looked like it was from the writer but the link was broken.
Dave
Always wear safety glasses while programming.
Yes, I noticed that.
I have it installed on my system, but dont seem to have the original installable. However, it does seem to be a portable app, as it works on any PC I copy that folder to.
It was a free utility, so I can mail it to anyone who is interested; its about 3 MB in size.
Regards,
Anand
Hi, Anand
may be one can find it here :
http://depositfiles.com/files/urjh2so1w
...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Not so nice.
Looks like a pay thingy just to download.
Dave
Always wear safety glasses while programming.
The Proton Header Maker looks close to what I think we are after. Thanks for the screen shot, looks like a nice layout to shoot for.
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Last edited by Acetronics2; - 8th September 2010 at 12:18.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Well, if I get a program to write my code then I would be very very lazy. ( And I would like it very much!).
But only for the borring job of setting fuses and searching those *.inc files for settings, if I get the nick name lazy then ... be it.
I preffer to do my job than the above little stupid things.... Especially whenever a chip is changed.
So, who else feels lazy? Join the club.
Ioannis
Last edited by Ioannis; - 8th September 2010 at 12:45. Reason: always typos. Dyslectic the guy is...
@Dave, It is in fact free to download, you do have to wait for the timer to run out.
I have downloaded it and it is in fact pretty much just what I am wishing for. I think its a great example! Doesn't seem to support all the chips, but the layout is pretty nice. Well and of course it is for proton not PBP!
Count me in for Lazy!! I love coding, but HATE housekeeping!
Last edited by cncmachineguy; - 8th September 2010 at 12:49.
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Yess ...
as long as the wizard does not forget little details ... or solve uncompatibilities ...
you can rely on it.
lazy programmers ... yes, nice. But animators won't have to be lazy ...Hi, dear Mackrackit
...
I did everyting right, simulation in Proteus works fine, but on board, it doesn't work.
So, I do not understand.
HEEEELP !!!
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
I've started working on a stand-alone PBP header-wizard program and it's bringing some questions to light...
Right now it parses the .inc files for the selected PIC (if they're not in the default locations on you computer you have to set the paths). From the MPASM files it parses out all of the provided configuration settings, and from the PBP folder it parses out the current default configuration settings.
In thinking about where to go from here, there are at least a couple of chips that do not appear support any sort of _CONFIG. __config, or whatever statements. A prime example is the 18F67J50. You're forced to use something like, for example "CONFIG FOSC = HSPLL".
Now putting the line "@ CONFIG FOSC = HSPLL" in a blank program compiles just fine so long as the the CONFIG lines are remmed in the PBP include file. However, when it gets put at the top of a working program it causes all sorts of warnings and errors to appear and the configuration settings do not get transferred to the programmer.
So, is it even possible to put in-line config settings in this class of device? Is the only option to edit the PBP include file?
Thanks for your time...
Best Regards,
Paul
That sounds great!
I can get it to compile using something like this at the front of a large program, even with some includes thrown in for the PIC18F67J50. And I see the change in my PicKit2 programmer. (Doing so with PBP inc files configs remmed out).
Code:asm CONFIG XINST = OFF CONFIG PLLDIV = 5 CONFIG WDTPS = 512 CONFIG CPUDIV = OSC1 CONFIG FOSC = HSPLL endasm or: @ CONFIG XINST = OFF, PLLDIV = 5, WDTPS = 512, CPUDIV = OSC1, FOSC = HSPLL
See Bruce's post here: http://www.picbasic.co.uk/forum/show...3087#post13087
There are some issues with other newer chips though. For instance the PIC26J50 uses OSC instead of FOSC, which really throws a wrench in the works. (See semi work around here: http://www.picbasic.co.uk/forum/show...0854#post90854 ) If anyone wanted to get fancy: If it was one of the chips that required a change to the pbp .inc file .... It could ask you "would you like me to edit your 18F26j50.inc file?" That would be so much nicer than looking through the list of chips, finding it, commenting other stuff out, and entering new settings, then hitting save. Don't know how many other chips we are talking about here though.
I am not sure if it helps, but here is a PDF with a lot of chip's configs:
http://ww1.microchip.com/downloads/e...ngs_51537f.pdf
http://www.scalerobotics.com
Hi Paul,
Just curious. Do you plan on having your program open source?
Dave
Always wear safety glasses while programming.
Hello scalerobotics,
Whoa. Thanks for that great info! I've mostly been using the wiki article as a reference.
When I copy just your code,it compiles just fine. When I add the single line "PORTB.0 = 0" it gives me two warnings and an error:Code:asm CONFIG XINST = OFF CONFIG PLLDIV = 5 CONFIG WDTPS = 512 CONFIG CPUDIV = OSC1 CONFIG FOSC = HSPLL endasm
Warning[220] c:\pbp\pbppic18.lib 958 : Address exceeds maximum range for this processor.
Error[118] c:\pbp\pbppic18.lib 958 : Overwriting previous address contents (FFF9)
Error[118] c:\pbp\pbppic18.lib 958 : Overwriting previous address contents (FFFA)
So, did you have to do the "replace OSC with XTAL in PBPPIC18.LIB" thing to get it to work?
Best Regards,
Paul
Hello Dave,
I certainly have no objections to sharing the code for this but I haven't a clue about how to explicitly "open source" a project. I'm open to suggestions.
I'm writing the application in Delphi v4, mostly because I've been writing in various flavors of C/C++ for the past several months and I wanted (needed!) a change...8^)
Best Regards,
Paul
Something is fishy here. I can add the line without errors. I am using MPASM 5.35, and PBP 2.60A.
Yes, I did have to for the 18F26j50. Not the best solution. As it might break any include file that tried to look at the osc speed. But I still like it better than editing the .inc file by hand each time I try something different. I'll be keeping my eyes peeled to see if MeLabs can make a proper fix. Microchip has thrown the curveball, making changes that affect their 3rd party development tools.So, did you have to do the "replace OSC with XTAL in PBPPIC18.LIB" thing to get it to work?
If yours or Dave's header program could do it and relieve some of the configuritis pain I feel each time I go to a new chip, (or one I forgot), that sure would be great.
Thanks you guys for giving it a go.
http://www.scalerobotics.com
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Not sure how the big open projects work...
I guess to do it right a license needs to be decided on, GNU?
Other than that jut make the code available someplace for folks to play with. If someone adds a function/fix then they let you know. You then work their code into a version if possible then release the updated version.
If you do not want to incorporate code from others just make yours available someplace.
If we can find others using Delphi or Python that want to help with this we could give out parts that need worked on. The "J" chip problem comes to mind.
Dave
Always wear safety glasses while programming.
Bookmarks