Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Dave

  1. Good question. If more than one task or thread of execution wants to share a resource then semaphores are a much better fit. If only two tasks or threads want to share a resource, and one of them wants to do the foreground processing, then waking and sleeping is probably much neater. Regards Dave
  2. Taga1, Sorry by the PIC10F200 has a 12bit instruction core and so cannot be readily supported by the BoostC compiler which only supports targets with 14bit and 16bit instructions. Regards Dave
  3. hyperion007, I don't believe that fround() is a standard 'C' function, is it? Regards Dave
  4. Kenn, There are no virus's in there, it is a false detection. We recommend pushing any such files through www.virustotal.com virus checker, which uses a number of antivirus programs, for you own peace of mind. Regards Dave
  5. Chen, This is an Internal Error, ie something gone wrong between compiler and linker - which may or may not be a problem in your code. To reproduce this problem we could really do with a simplified project that builds and demonstrates the problem. Please send to support@sourceboost.com Regards Dave
  6. Remi, Your problems are unexpected. Please provide a small but complete program demonstrating the issue then we can take a look. Regards Dave
  7. Mike, If you need a specific version we can make it temporarily available. Regards Dave
  8. Dimitris , I have never heard of this problem - no one else complains. So I can only imagine that it is a function of you system or installation. Let us know if you find the cause. Regards Dave
  9. Mike, The url format is (example of V7.10): "http://www.sourceboost.com/CommonDownload/Binaries/SourceBoostV7.10/sourceboostv710.exe" There is no guarantee that older version will be there as the server space is reclaimed. Regards Dave
  10. TomF, This does seem to be a problem. The work around for now is to move these variable declarations outside the function body. Regards Dave
  11. We don't seem to have the project, please re-send to support@sourceboost.com Regards Dave
  12. erikhaverkamp, Remember that setting single bits directly on a port cause a Read Modify Write process. The read process reading what is actually on the port, rather than what was last written. When the port is read as part of setting bit 5 bit 4 must be read as being low, hence low is written back to it. Typical cause of such a problem is capacitive loading of the port, causing the voltage on the actual pin to take time to rise. On some devices LAT registers exist which don't suffer from this problem as reading them give the last written value rather than the actually pin value. Ano
  13. Dave

    Simulator Speed

    TomF Not a bug :-) The simulator always runs as fast as it can. Telling the simulation environment a different clock rate tells the plugins what the clock speed is. This enables the stopwatch plugin (for example) to report times in standard units rather than just ticks, or the LCD plugin to determine how many clock ticks for it's fixed time delays. Regards Dave
  14. Micmar, Yes it is compatible with Poteus, but I will admit I haven't tried it lately. Regards Dave
  15. Micmar, A COF file is produced during the linking process. What else are you wanting? Regards Dave
  16. Coder, The reason to use unsigned data types where possible is because extra work has to be done with signed data types such as sign extension. One thing that might give what you describe is aliasing. What is the sample rate of your Oscilloscope (needs to be at least 2x the frequency you try to measure), if its too low then you get beating effects that make frequencies appear much lower than they are. Maybe the signed code was so much slower that the frequency produced did not then suffer from aliasing issues. Regards Dave
  17. John P, I'm not seeing the problem. Can you provide a complete compilable piece of code for a specific target device that can be compiled to demonstrate the problem? Regards Dave
  18. Jac, Please try it, but I suspect that it wont work as you would expect it to. Regards Dave
  19. Marco, What facility is it you are asking for ? Regards Dave
  20. Jac, I though this problem was going to be an entry missing from the target descriptor file (TDF) that describes many of the attributes, including memory mapping, but the required data appears to already be there to indicate the overlap. So it must be something else wrong with the linker. Regards Dave
  21. JorgeF, It sounds like you may have had some issues with your web browser and the page being refreshed. What was going to be a release candidate has accidentally been published as a release. It actually should be a good stable version so probably wont be changed back to a release candidate. Regards Dave
  22. ajbeavan, By mistake we added this to our web site as a full release, will be corrected later. Regards Dave
  23. How about this: #define get_byte_3_of_long(long_value) ((unsigned char)(long_value >> 24)) #define get_byte_2_of_long(long_value) ((unsigned char)(long_value >> 16)) #define get_byte_1_of_long(long_value) ((unsigned char)(long_value >> 8)) #define get_byte_0_of_long(long_value) ((unsigned char)(long_value)) long mylong = 0x12345678; unsigned char byte0 1 = get_byte_1_of_long( mylong ); Regards Dave
  24. davidb, It would be good if you could post a small program that demonstrates what you describe. Regards Dave
  25. What is in this library and where did it come from? To build a custom library you need to have all the Novo the source code - do you have it?Included with it are some stand alone projects that do different Novo builds. I would copy one of those and make the required changes. Regards Dave
  • Create New...