Jump to content

Dave

Administrators
  • Content Count

    2,046
  • Joined

  • Last visited

Everything posted by Dave

  1. Hi all, V7.04 of the SourceBoost Package is now available: Key changes: 1) Novo RTOS Bug - Sleeping task sleeps much longer than expected when two tasks awake at the same time. 2) IDE - Fixed multiple workspace and project handling issues introduced in V7.03 http://www.sourceboost.com/CommonDownload.html Regards Dave
  2. Panvadee, Select target device PIC16F648a instead. Regards Dave
  3. TomF, We need more information in order to help. 1) What version of the SourceBoost package youy are using? 2) Does the problem occur with just one project or any project you try to build? 3) Was it working once but now has stopped? Regards Dave
  4. Yes, as long as you are not more than 512 instructions over on a PIC16 and 2048 instructions over on a PIC18. Regards Dave
  5. Not quite true. Some dummy target memory is used in linker so that a program that exceeds the target devices memory will still generate the memory info even if the actual target memory is all used. Max overusage is 512 instructions on PIC16 and 2048 instructions on PIC18 devices. Above this level no memory report is generated. Regards Dave
  6. Bryan, This is indeed an issue, and your fix can still fail if a task wake up time occurs at just the wrong moment. I have some modified Novo RTOS code that I want to send to you. Please send a mail to support@sourceboost.com and I will send you the code. Regards Dave
  7. In case you don't know where to find it (once I spent a long time looking in the devices data sheet and it's not in there) , you can find the address that needs to used when programming the target device and wanting to write to EEPROM as part of this process in the devices "Memory Programming Specification" data sheet from Microchip. BTW: I know this doesn't help with the 0xf000 address question. Regards Dave
  8. Bryan, I'm off on vacation, so can't look at this issue until I return (1 week). What you could do to help is come up with code that demonstrates the issue and can be run under the SourceBoost simulator/Debugger. Regards Dave
  9. rbairos, Native support for floating point is not yet supported. You need to use the appropriate floating point library function and add the floating point library to your project. Please read the Floating point library manual. Regards Dave
  10. Bryan, This should not be necessary, Sys_Sleep() does the required yielding. It would be good to see your example. Regards Dave
  11. TomF The logic levels present on the pins are actually read, so an excessive load on a pin can drag it down to zero even though the data last written set the output on. I hope that helps make it a little clearer. Regards Dave
  12. TomF, If you include a file it is the same as all that code in the included file being in that file. This: #ifndef __COMMS_H__ #define __COMMS_H__ only prevent multiple inclusions in the same source file (can happen when some source include files include other files), each source file is handled individually, they have no knowledge of what other source files have included. Regards Dave
  13. TomF, The variable is no random at all.Each time you include your "comms.h" file in another source file you get another private instance of the static variable declare in the header file. This is all perfectly valid and works just like other C compilers. Regards Dave
  14. TomF, Using the static keyword in a variable declaration makes that declaration private to the source code file code in which it appears. For what you want to do: 1) declare you global var in once of your source files without the static keyword. 2) declare the variable again in the header file with the prefix "extern". Then it should work as you want. Regards Dave
  15. Mark, When I remove the option, it compiles fine again. When -idx 2 option is used the compiler uses a different build of library code that is build also with the -idx 2 option.Both library builds are contain in the same libray file, so it sounds like your library file has only the -idx 1 build in it. What is your exact version of SB are you using? Regards Dave
  16. TomF, 1) Please try BoostC V7.032) Try changing the project name so it doesn't have spaces in it. Regards Dave
  17. TomF, No it does not optimise such code. Declare the function as inline if you want that to happen. Regards Dave
  18. charbel, This is an internal error, not a fault of your code. Please send a project demonstrating the issue to support@sourceboost.com so we can take a look. Regards Dave
  19. You can find the version log just off the download page:http://www.sourceboost.com/CommonDownload/VersionLog.html Regards Dave
  20. McNerdius, There should be two options in there, Debug and Release.The function of these modes is two fold: 1) Debug or Release are defined so code can be conditionally compiler, by using #ifdef, for debug or release builds of a project. 2) The files created during a built, ie .obj, .asm, .casm, .hex etc are placed in either a debug folder or release folder. Debug and release does not change the setting of processor debug mode configuration flag. It appears we have missed out the debug configuration flag on some targets.You can add it in by modifying the Target Configuration section of the TDF file. In the case of PIC18F26J11 this needs adding: TargetConfig DEBUG { // Background Debugger Enable: ConfigRegAddr = 0x0000FFF8; ConfigBitMask = 0b10000000; ConfigSettings = 0b00000000, "ON","Enabled", 0b10000000, "OFF","Disabled"; } Regards Dave
  21. Yong, The MPLAB integration does not replace the SourceBoost IDE, but allow use of the BoostC compiler in MPLAB. If you want to be able to use MPSIM and ICD3 then you have to do that from within MPLAB. Regards Dave
  22. Yong, You need to:1) Install the SourceBoost package, selecting integrate into MPLAB during the installation. 2) Create a project in MPLAB. 3) Select BoostC compiler as the toolsuite. 4) Set the paths for the .exe files for the compiler and linker in MPLAB. 5) Add the source files and libraries to the project. 6) Add #include <icd3.h> to one of the source files. 7) Set ICD3 as the debugging tool. 8) Compile the project. 9) Down load the project to ICD3 and debug. I hope that helps. Regards Dave
  23. Yong, In SourceBoost IDE turn on Menu View->CodeBar. Here under assembly you will find the the .casm file text. Regards Dave
  24. yong, If your are using a PIC18 target you can used -idx 2 command line option to make all array indexes 16 bit. Regards Dave
×
×
  • Create New...