Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by medelec35

  1. When running the Button Test tutorial: http://forum.sourceboost.com/index.php?showtopic=2399 I get following issue when running a simulation: I can only guess that any defined variable will cause the watch window to show ERROR because they are skipped by the simulator? Is this me being a noob (I am with this really) or is it a bug? I must say the more I use the simulator, the more I like the functionality. If developers of Flowcode decide to stay with boostC rather than move to a different compiler due to some missing functions e.g: cos, tan atan. Also change the way floats work so they don't use non standard functions. Then I would happily purchase the full version. I'm just interested in learning on the complier that's under the hood of Flowcode.
  2. Thanks Pavel. This would also apply to: if(duration==1000) // if duration equals 1000ms, { duration=990; // make it 990ms. } // this will limit the max delay. } if(button3) // if button3 is pressed, execute { // the following statements. duration-=10; // reduce delay by 10ms. if(duration==10) // if delay equals 10ms, { duration=20; // make it 20ms. } // this will limit the min delay. } if(button1==0) // if button1 pin is not pressed, { // execute the statements below check1(); // call routine check1. portb <<= 1; // shift bits in portb to its left, ones. delay_ms(duration); // pause for the value of duration. Further down. Unless it does not apply to this since: int duration; so ms is no longer a char but integer? But if : Then I can't see it being the case.
  3. Forgot to mention: The tutorial is from these forums: it was from a tutorial called 'pic Micro Programming In Boostc For Beginners' http://forum.sourceboost.com/index.php?showtopic=2399 Apart for that, it's a great tutorial and I plan to finish it. So my thanks goes out to the author
  4. Thanks for your reply Reynard, much appreciated. ‚ÄčI did not realise delays are char only since I was using a tutorial called WINK LED. one of the lines stated: delay_ms(500) // pause 0.5 seconds Since it's my first bit of coding was following it to the letter & blindly as the author new much more than I do. Shame delays can be initialised as unsigned int. All the best.
  5. I have an issue with my first sourceboost C code: #include <pic16f877a.h> #include <system.h> #pragma CLOCK_FREQ 4000000 //Set clock frequency #pragma DATA _CONFIG, _PWRTE_OFF & _WDT_OFF & _HS_OSC & _CP_OFF //Target PIC16F877A configuration word void main() { trisb=0; while(1) { portb.0=1; delay_ms(500); portb=0x0; delay_ms(500); } } The issues are. The timing are suppose to be 500ms but stop watch and a different simulator are both showing the delay as 244ms: Also the green simulation step line is going below the last brace for some reason? Since this since my first attempt, it's more than likely I'm doing something daft. I'm grateful for any advice with what is going wrong please. Thank you.
  6. Thanks for your reply AlexR, I was looking at the wrong part of the datasheet, I totally agree with what you say. Therefore the Bug is in my brain, not BoostC So I will take that back. Flowcode only complies as I made it do that with myself looking at the wrong data. So will not be an issue to any one else.
  7. Source Boost 7.04 is currently used with Flowcode, and Flowcode failed to compile with Timer4 or Timer6 I have corrected this so Flowcode now compiles. Also 16F1826.TDF requires updating. I thought I would post this for your reference. Hope it's helpful. Merry Christmas.
  8. I do hope this problem gets resolved! I would like to use 18f2450 for a usb application ,but until this issue is resolved I will have to wait. Does anyone who works for sourceboost give support for people who use there products? It seems a waste to buy a competitor's product, when sourceboost works for all of my applications except one!
  • Create New...