Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About JorgeF

  • Rank
    Super Enthusiast

Profile Information

  • Gender
  • Location
    ES @ Europe, third rock from the Sun
  1. Hi Yep. Its not the first time that an anti-virus triggers a false positive. Surprisingly it rarely happens as all it takes is a shared sequence of code with a known virus. With the millions of programs out there in the world, it could happen a lot more. Good you have your problem sorted out. Best reagrds Jorge
  2. Hi That's strange. Might it be that you are working with a very old project, created under a previous version? How does it behave with a brand new project? In my installation (7.43), all the compilers have the underscore in the name, also the linker. BTW, don't forget to do a good virus/malware scan on your PC. Best regards Jorge
  3. HI Have you looked in the manual?
  4. Hi I might be wrong, but. I have a faint memory of such a change somewhere along the V7.xx versions. At the time the subject was discussed/explained in the forum, maybe you should take a look at it. What is the exact version you are using?
  5. Hi That is strange, I installed the Sourceboost IDE with Boost C and goodies licences in a new laptop (3 weeks ago) running Win 10 64bit up to date without any issues. Best regards Jorge
  6. Hi Pavel Thank you for the quick reply. Good to know. Its been a long time since I looked at the NOVO source, so my memory tricked me on remembering "...this only works because of linker magic...". Anyhow I wasn't aware that the linker was the same for both compilers, kind of assumed it was 2 completelly separated toolchains. Best regards Jorge
  7. Hi I was wondering. Does the Chameleon compiler support the NOVO RTOS. AFAIK the BoostC compiler does generate a piece of special to code to execute the task switching on the NOVO scheduler. It would be nice if Chameleon had the same feature. Best regards Jorge
  8. Hi Good you found it. But its a fact that the BoostC compiler is quite weak in terms of error reporting. I've seen that error, "failure", for all kinds of errors. In fact its quite rare to see other error messages. Best regards Jorge
  9. Hi Usualy the forums are more targeted at experience exchange between users than to technical support. Same happens with the Microchip forum and a few others I know. Best regards Jorge
  10. Hi Confirmed, both for C++ and C. Did you try to send an email to support@sourceboost.com ? Best regards Jorge
  11. Hi I missed this topic in due time,so I don't know if this repply is usefull, but here it goes. That is a nice ASM trick, but I think its uneeded in 'C' and also undesired. Its not a good idea to directly manipulate the stack when using a compiled language, because you don't control how the compiler handles the stack. Also bear in mind that due to the limited stack size and specific stack access instructions of the 8 bit PICs, BoostC and other compilers implement a so called "software stack" to handle parameters and automatica variables. The hardware stack is used only for return addresses. To store strings in the program memory you can use the "rom" qualifier (page 47 of the Boost C manual) and then the usual 'C' tools to work with them. HIH Best regards Jorge
  12. Hi I've confirmed the Bug, both for C and C++. But as I can't solve it, I would suggest 2 alternatives that generate correct code: while(c--) or while(c = c -1) HIH Best regards Jorge
  13. Hi Check the figure 14-3 and 14-4 @ page 136 of the datasheet and cross-reference it with figure 12-1 @ page 126. The TMR2/PR2 match signal that sets the PWM output to 1 also sets the TMR2IF interrupt flag to 1 via the TMR2 post-scaller. HIH Best regards Jorge
  14. Hi I think you are wrong here. The beginning of the PWM cycle happens when TIMER2 is reseted due to a match with PR2. When Timer2 = PR2 a match interrupt is generated (TMR2IF). If you set the Timer2 postscaller to a 1:1 ratio, you will have this interrupt generated at the beginning of every PWM cycle. HIH Best regards Jorge
  15. Hi You already have a timer associated with the PWM signal. Why don't you use it?. The period signal is defined by a timer, things start when yes start the timer. Use the comparator to stop it and read the value. Another thing I'm not sure the PWM is the better tool for the job, because the becessary duty cycle to charge the capacitor is unknown. HIH Best regards Jorge
  • Create New...