Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About kenn

  • Rank

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Location
    Toronto, ON
  1. Same problem Win 10 boost 7.30 Steps to reproduce: start a new workspace Workspace -> Add Project to Workspace -> Project Wizard ...all you get is a small alert box that says "failed to parse wizard script"
  2. Thanks Ted. Your PIC projects and libraries have been helpful and inspirational.
  3. Plugins V7.22 Infected ?

    Today I tried to download the v7.22 of the plugins, and my AV (Avaast) claims the stopwatch plugin contains a virus: Infekce zablokována URL hxxp://sourceboost.com/CommonDownload/Binaries/Plugins/pluginsv722.zip|plugins.exe|{app}\StopWatch.dll|[Armadillo] Infection Win32:Evo-gen [susp] Could you folks please confirm that the current plugin downloads are virus-free? Thanks.
  4. Jorge nailed it. As soon as I built your sample, and examined the list... there was nothing built for your isr() handler. Second clue: when trying to simulate, it was impossible to place a breakpoint inside isr(). I'm not so good at interrupts, but I used the sourceboost project wizard to produce a starting point with all the correctly named functions and setups, then studied that. I also use the simulator and breakpoints as much as possible to confirm the operation of my code.
  5. Hi, This is a small issue - it would be nice if the project or workspace would remember open files, and when the same project/workspace is opened again, you also get the same files opened. Most IDE's seem to do this. A related request - have the project remember the last-used simulator plugins and their configuration. Currently, it seems that if you build and simulate project 'A' with plugins, then close it and open project 'B' (right away, or days later), you will see the plugins from project A again when you go to simulate B. If you select different plugins for project B, then quit it and re-open A, now you have the plugins from B when you start the simulator for A. And so on. Small things, but they slow me up a bit if I'm playing with a few different projects at the same time. Thanks. ken
  6. What microcontroller(s) are you using?
  7. oops - this might be the answer: http://forum.sourceboost.com/index.php?showtopic=4964
  8. Hi, I'm interested in developing small applications for PIC models that are supported in the BoostCcompiler, but are not part of the small group of PICs supported by the sourceboost simulator. To date I've been developing in the simulated target then hand-editing the source file for the final target and switching the target selection. It's a pain if I have to go back to simulation to make more changes, then back to the real target, and so on. It would be cool if I could just keep working with one sourcefile, that automatically chooses definitions based on the target. Is it possible to put conditional definition blocks for the different PIC models (containing the different configs, and defining aliases for port names, etc) into one source file, and have the compiler select the right block depending on the target device selected in the IDE? In other words, is some form of the following (pseudocode) possible: if (target==PIC16F877) #pragma DATA _CONFIG, ... #define INPORT portb #define OUTPORT portd ... endif if (target==PIC16F684) #pragma DATA _CONFIG, ... #define INPORT porta #define OUTPORT portc ... endif [application] ... I know a bit about conditional declarations in C... I'm just wondering if the IDE compiler target can be used as the test at compile/build time. Thanks for any suggestions.
  9. Hi Dave, Thanks for the fix. I only had time tonight for a quick test, but yes the ADC simulation now works.
  10. 16f688 For Newbie

    Hi Murray, (So, you can't just drop another meter movement into this broken instrument?) Like you, my path is littered with microcontrollers learned, used briefly, then forgotten... yes 68HC05, also 8051... I decided to take up PICs a little over 2 years ago, I've stuck with it, and even built a few things. I've invested modestly in some MicroChip dev boards and tools. And I'm reasonably happy with the sourceboost tools and C compiler. Before going further, there's a bit more to your choice than just a microcontroller... you really are choosing an ecosystem. Are you going to become a microcontroller whiz, or are you just seeking a microcontroller platform to solve some problems, like your instrumentation example? PIC is a good choice because of its popularity, hence many tools and applications already developed and available. Rather than just a part number, perhaps you should seek out a board or prototyping system that is closest to meeting your requirement, to speed up your delivery. AVR is also a good choice, particularly as used in the open-source Arduino platform. Just some stuff to consider. Hands-down, the PICkit2 or PICkit3 programmers. Either will program your 16F688. I have a PICKit2.They support ICSP programming of just about all the popular PICs, they are USB, great supporting applications, real easy to use. They are available as clones (ebay), but the brand-name MicroChip ones aren't that much to begin with, and MicroChip has a pretty good replacement warranty (not that you'll need it).
  11. Hi Pavel, Thanks for the feedback. I can confirm that I'm using v7.05 of the IDE, I downloaded and installed the v7 plugins (... and of course I bought the licence, on 17 Dec, 2011) NOTE that your auto-response to the licence purchase mentioned that the licence is for 6.x plugins... I am assuming that you haven't yet changed the message Last night I tried a few things: - retried Variable PSU - same result: "Abort Building..." - removed Variable PSU dll, restarted IDE, tried to select last plugin - Stopwatch - got message "Abort Compilation..." - removed Stopwatch dll, restarted, tried to select last plugin - Speed Tester - comes up OK - returned Variable PSU dll, restarted IDE, tried to select Variable PSU - got message "Abort Compilation..." To recap, both variable PSU and Stopwatch plugins seem broken. Can any other users confirm whether all the v7 plugins work for them? I'm doing more with ADC these days, it would be a great help if the Variable PSU or the Function Generator were working as DC sources. Thanks, ken
  12. Update: So, I wrote a minimalist "dimmer" app, where the ADC value is used to control a PWM LED dimmer, built it, and programmed it into a '877A... and it worked fine on the hardware - 10k pot across Vdd and Vss, wiper into PORTA.0... pot controls brightness. I went back to the IDE, tried to simulate it using the Function Generator as source of DC input, and LED plugin, and 'watched' adcvalue... and it stayed at zero, apparently no adc happening, or simulated voltage isn't being applied. If anyone tries this also, please post your results. The code is below. PORTA.0 is the ADC input, and PORTD.0 is the LED anode. (Thanks again, Ted. You helped me convince myself that I hadn't lost my mojo ) #include <system.h> /*********************************************** Doubting Thomas' 1-ADC, 1-LED test RC osc kn Jan 2012 ************************************************/ //Target PIC16F877A configuration word #pragma DATA _CONFIG, _PWRTE_OFF & _BODEN_OFF & _WDT_OFF & _LVP_ON & _CPD_OFF & _DEBUG_OFF & _RC_OSC & _CP_OFF //Set clock frequency - #pragma CLOCK_FREQ 4000000 // "header" void adc(); unsigned char adcvalue; void main( void ) { // 877 ports - all out, RA0 ADC //Configure port A trisa = 0x01; //Configure port B trisb = 0x00; //Configure port C trisc = 0x00; //Configure port D trisd = 0x00; //Configure port E trise = 0x00; //Initialize port A porta = 0x00; //Initialize port B portb = 0x00; //Initialize port C portc = 0x00; //Initialize port D portd = 0x00; //Initialize port E porte = 0x00; trisa = 0x01; // Port A[0] is input for A/D adcon1 = 0x0e; // (left justified) 1 A/D channel adcon0 = 0x81; // FOSC/32, channel=0, ADON=1 //Endless loop while( 1 ) { adc(); set_bit(portd,0); delay_us(adcvalue); clear_bit(portd,0); delay_us(256-adcvalue); } } void adc() { set_bit(adcon0, GO);// Start conversion while(test_bit(adcon0,GO)); adcvalue=adresh;// Fetch high 8 bits of result }
  13. Thanks alot, Ted. I'll give that a whirl ASAP. I'm also going to try the compiled apps on simple hardware, just in case the simulator is misbehaving on ADC. Assuming you also have the v7 plugins, does the Variable PSU work for you?
  14. Thanks. I think it would help draw more interest to your products, too. Cheers, ken
  15. Hi guys, In December I downloaded the installer (and purchased the licence) for the extra plugins pack for v7.05. Plugins appear to have installed without error, registered as expected, and most seem to function correctly. The Variable PSU simulator shows up at the bottom of the plugin list, but when I attempt to select it, nothing happens except for the following message in the Build pane of the Output window: Abort building... This happens every time I try to select Variable PSU, regardless of what project is loaded, or whether other plugins are already in use, or whether I'm in simulation mode or not. * * * As a side note - I wanted to use the Variable PSU as a voltage source for simulating input in a short PIC16F877A A/D program. Because the variable PSU isn't available, I brought up the Signal Generator plugin, and attempted to use it as a source of DC voltage on RA0. The plugin itself seemed ok, and when I connected the Digital Voltmeter plugin to the same pin and started the simulator, the voltmeter indicated the correct voltage set on the Signal Generator... but I never saw a non-zero value on the A/D registers. This is most likely a problem with my code, but I can't find a known-good, simple, single input A/D program written in sourceboost. I haven't given up looking, but if someone could share a very short test program just using RA0 of the '877 or '877A, I'd be grateful. Thanks.