Jump to content

Thack

EstablishedMember
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Thack

  • Rank
    Regular
  1. Why use a third party editor? I ask only because I think the editor in MPLAB has greatly improved in recent releases, and in particular like the code-folding; keyword recognition and highlighting; auto-indenting and out-denting; bracket matching; etc. What extras do Textpad and UltraEdit bring to the party? SteveT
  2. If you could be specific about what the correct information should be for the items you list above, I'd be very happy to get in touch with CCS and try to persuade them to update their table. Let's be honest: ALL of those tables will gradually get out of date as the various manufacturers develop and upgrade their products, so they must be used to amending them. And I agree completely - without the source code the benchmarks are pretty meaningless, but I think most people will realise that. Pavel - please publish the correct information for your list of items in this thread, and I'll do my best to get the information to CCS. Steve
  3. OK, every aspect of PICkit2 seems to work perfectly from inside an XP Virtual Machine. To summarise: I've set up an XP virtual machine in "Windows Virtual PC"*, hosted by Windows 7, for my PIC programming activities. The SourceBoost IDE, MPLAB and the PICKit2 applications all run nicely in the virtual XP machine. The PICStart Plus and PICKit2 programmers both work fine (serial port and USB respectively). The following PICKit2 functions have been tested and work fine: * In-circuit programming * In-circuit debugging * Programming-To-Go mode In my experience MPLAB and the SB IDE are much happier in XP, so the use of a virtual machine is a good way to have the best of both worlds. I recommend it. Steve * This is NOT the same as "Virtual PC 2007", which doesn't support USB port capture and thus won't work with PICKit2.
  4. Further to our discusion about using PICKit 2 from within an XP virtual machine...... I can confirm that the Programmer-To-Go feature works OK, too.* The only thing left to check is the ICD function. I'll report back. Steve *I must say, Programmer-To-Go is a fabulous feature! The ability to "fill up" the PICkit with the code, take it out to the target hardware, and "empty" it into the target is just brilliant.
  5. Well, come on then, tell us which facts are wrong! Obviously the table will get out of date as all the products get developed. But it would great to hear which bits you know to be wrong - please tell us. Perhaps we could compile a list and get CCS to update the table. That would be an enormous benefit for SourceBoost. Steve
  6. Remember, so far I've worked only with PICStart Plus and I can say for sure it's fine in a Virtual Machine. It's only a serial port, after all. However, these past couple of days I've been playing with the PICKit2, also in the VM. I thought it might be trickier, as it's a USB device, but Windows Virtual PC lets the VM capture the USB port with no problems. I've programmed the PIC on the demo board a few times , but I haven't yet tried any in-circuit debugging. I can control the the PICKit2 (programming, and switching the VDD and MCLR lines) from the PICKit software and also from within MPLAB. It seems to work perfectly in both cases. As the VM is able to "see" the PICkit2 for programming purposes, I'm pretty confident it'll see it just the same for in-circuit debugging. Oh, I should point out that I'm using the new "Windows Virtual PC", NOT "Virtual PC 2007". The latter doesn't support the capture of USB ports. The former is still in beta (I think) and is used in the soon-to-be-released Windows 7. I realise you might not be in a position to go this route yourself, Ian, but for anyone else who might be watching this thread, I can honestly say that a virtual XP machine hosted in Windows 7 (or Windows Vista, maybe) is great for PIC development. Apps like PICKit2, MPLAB and SB IDE play much more nicely in XP than in Windows 7 or Vista. Finally, I will experiment with some in-circuit debugging from within a virtual XP machine, and report back to this thread. Steve
  7. I totally agree with you about the lousy stability of MPLAB. I think it's a weird mix - buggy and fragile, and with a Windows 95 look-and-feel, but with some great modern features like code folding, etc. However, I've found it works much better if I run it in a Virtual XP machine (I'm running Windows 7 here) with nothing else competing with it. I open all my reference documents, websites, etc from Windows 7. If you don't do this already, I would strongly recommend you set up a Virtual XP machine dedicated solely to PIC programming. It seems much better that way. Steve
  8. Ah, sorry, I've found it. In case anyone else is interested, there is a pretty good comparison page here: http://www.ccsinfo.com/content.php?page=newcompilercomp Obviously it's trying to sell the CCS compiler, but it looks like a useful, detailed and fair comparison of seven different PIC 'C' compilers. Steve FORUM OWNER: Please feel free to close this topic. I'm sorry to have opened it in error.
  9. Sorry for the one-man flood at the moment! You can tell I'm rather enthusiastic! When I first looked into BoostC (a year or two ago), I remember reading something about how it compared with Hi-Tech 'C'. I've searched this site, and Googled, and can find no useful information. It seems to have gone. I would like find out what benefits BoostC has over the ubiquitous Hi-Tech 'C', especially now that Hi-Tech 'C' has been taken over by Microchip and will no doubt get a pretty serious level of support. Is there a feature comparison list somewhere? If not, your own opinions on the strengths and weaknesses of the two products would be great. Thanks again for tolerating all this traffic! Steve
  10. (Not sure if this is the right forum; please move it if you wish) I am a complete newbie to SourceBoost products, although I've been programming PICs using MPLAB and the PICStart Plus for several years, now. My requirements are that I want to be able to write my code in 'C', program a range of PICs, and experiment with in-circuit debugging (I've never done this before). I'll be using the PICkit2 for in-circuit programming, and the PICStart Plus for programming uninstalled PICs. What benefits does the SourceBoost IDE have over MPLAB? In your experience, what are the strengths, weaknesses and unique features of both? Which would you recommend? Obviously I'm trying to decide whether to migrate over to the SourceBoost IDE, or stick with MPLAB. Any thoughts or reactions would be gratefully received. Thanks, Steve
  11. Fantastic! Thank you, IanM, I really appreciate you going to this trouble. I'll give it a try. Thanks again for all your help. Steve
  12. ChipGuy: nope, it definitely wasn't me! I haven't been near the Hi-Tech forums for as long as I can remember. I've decided to stick with BoostC for now (while I'm learning the ropes), although I ought to take a look at Hi-Tech C some time. However, I have asked a related question in the Microchip forum, although it wasn't in the context of using it with BoostC. Anyway, ChipGuy and kenn, thank you both very much for such encouraging words about the PICkit 2. You've encouraged me to look at it again, and I think you are right - I should build ICSP into my circuits from now on, and make proper use of it, instead of messing about taking the PIC in and out all the time. According to the manual, the SourceBoost IDE doesn't have built-in support for any programmer. Is there an on-line guide somewhere saying how to use PICkit 2 with the SourceBoost IDE? Many thanks again, Steve
  13. Don't be so rude. I was trying to help. Your question was incredibly unclear. Here's how your question looks in REAL English: "I have performed an A/D conversion in the PIC. I now want to display the results of the conversion in the SourceBoost IDE Terminal Page. I am using an RS232 link from the PIC and can send letters, numbers and strings to the Terminal Page successfully. How do I convert the binary data from the A/D conversion into human-readable numbers for display in the Terminal Page?" THAT is English. Young man, you need to learn some manners. Steve
  14. I still don't understand. Do you mean you've done the A/D conversion in the PIC, and want to send the result of the A/D conversion up the RS232 link into the computer, and display it there? Or do you mean you want to receive some A/D data via the RS232 link and display it using your PIC and some sort of LCD display? Or is the RS232 stuff nothing to do with the A/D stuff? It's just that A/D conversion and serial comms aren't obviously related, so we're having to guess what you are trying to do. SteveT
  15. I don't think I really understand the question. Do you mean you want to know how to perform an A/D conversion and then display the result? If so, are you planning to use the internal A/D, or an external A/D chip? Or do you mean the A/D conversion has already been done and this is what is coming in via your RS232 link, and you want to display the incoming numbers? Perhaps you could explain more fully exactly what you are trying to do. Steve
×
×
  • Create New...