Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PIC24F

  • Rank
  1. A friend also did the same but his did not show the Source Boost Compilers in the Select Language Tools option in MPLAB, Even though he used the Integrate into Windows button. This was solved by saving the HKEY entries from the registery files from Legacy Language Suites entry on my computer, then importing them it into his Registery data and it worked fine. Seem there are a few issue with the instalation program.
  2. I over installed 6.55 ontop of 6.40 on a HP Laptop running XP with all latest updates and service packs. It would not compile 16 or 18 version PIC's It took a few days to work out the problem What it had done was to set the SourceBoostCCompiler EXE files to boostbasic.pic18.exe in stead of boostc.pic18.exe Fixed it in the end.
  3. Any one familiar with the Dallas 1 Wire knows theres a 256 byte character array used for looking up the 8bit CRC. on the 18 series this is no problem but on the low end pics it fails to compile. There is a simple piece of ASM code to acheive this, so why cant the compiler work around it. It could at least use 2 tables or use one table with one byte missing. and hard code the 1 missing byte. for now I have to use ASM inserted code. Mick
  4. Thanks for the response (and the code). My rationale for sprintf is that it could be used in lieu of specialized printf-esque functions. A perfect example is the lprintf function in the lcd driver header included with SourceBoost. If there were a generic sprintf function, all that would be needed to output nicely formatted strings on any interface (serial, LCD, LED matrix, or a laser beam on the moon's surface) would be a puts function, which would be much simpler to code. I realize that the PIC is, by nature, a device with limited resources, but if your particular application is consuming
  • Create New...