Jump to content

Search the Community

Showing results for tags 'simulator'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • PIC Embedded Programming
    • BoostC and Chameleon compilers programming
    • BoostC porting source code
    • BoostC++ compiler programming
    • BoostBasic compiler programming
    • Assembler programming PIC
    • Novo RTOS Programming
    • Hardware PIC
    • Enhancement Requests
    • Bug Reports

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. Would be nice if in a future sourceboost version, if your team give to the watch window the ability to show struct members values as it happens with normal variables, instead of showing "error". Well.. i know we can see it through the memory bar, but when we have large apps with a lots of data structures with changing data between them, the debugging process, becomes painfull. It happens in all versions of © sourceboost as you can see by simulating the snipet below ty, br //////////////////////////////////////////////////////////////////////////////// // This is a small example with minimal settings just for demo purposes // It is intended to write struct data items to see watch window behaviour //////////////////////////////////////////////////////////////////////////////// #include <system.h> // F U S E S C O N F I G U R A T I O N #pragma config OSC = INTOSCPLL // Internal osc PLL can be enable/disable #pragma config CP0 = OFF // Program memory unprotected #pragma config FCMEN = ON // Enable osc monitor #pragma config WDTEN = OFF // Watchdog disabled, could be enable by soft #pragma config WDTPS = 512 // 1:512 #pragma config XINST = OFF // Disable extended instruction set #pragma config IOL1WAY = OFF // works either way ///////////////////////////////////////////////////////////////////////////////// // T Y P E D E F U N I O N //------------------------------------------------------------------------------- // ///////////////////////////////////////////////////////////////////////////////// #define BUFFER_SIZE 4 // buffer size typedef union { unsigned char ubuffer[BUFFER_SIZE]; // array struct { unsigned char sitem1; // same as ubuffer[0] unsigned char sitem2; // same as ubuffer[1] unsigned char sitem3; // same as ubuffer[1] unsigned char sitem4; // same as ubuffer[1] }sbuf; }UBUF; UBUF ubuf; #define buffer ubuf.ubuffer #define item1 ubuf.sbuf.sitem1 #define item2 ubuf.sbuf.sitem2 #define item3 ubuf.sbuf.sitem3 #define item4 ubuf.sbuf.sitem4 //////////////////////////////////////////////////////////////////////////////// // M A I N //////////////////////////////////////////////////////////////////////////////// void main( void ) { item1 = 10; // << moving it to watch window, it shows error, not val item2 = 20; // << moving it to watch window, it shows error, not val item3 = 30; // << moving it to watch window, it shows error, not val item4 = 40; // << moving it to watch window, it shows error, not val while( 1 ) { } }
  2. 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.
  3. 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.
  4. Hi, I'm trying to recompile a custom plug-in for the new v7, using the v7 template. Apparently this template is a VC++ 6 project, and contains non-standard C++, and this 13-year-old compiler is no longer readily available. Would it be possible for someone to update the plugin template project and code to a VC 2010 project? Or maybe wxWidgets, gcc and Code::Blocks? Thanks.
  • Create New...