Jump to content

Dave

Administrators
  • Content Count

    2,046
  • Joined

  • Last visited

Everything posted by Dave

  1. Paul, Yes it's not nice. The problem is converting the asm into a form that has the right structure. The asm code can't be simply converted into a .lib file. Regards Dave
  2. TimC, When I see vague posting or clone posting it makes me suspect this is being done by some kind of spambot trying to become an established member who can post unmoderated. I therefore raise this users warning level as a flag for next time he posts. Regards Dave
  3. Peter, No thats a worst case scenario in case things delayed with the payment clearance (imagine a customer uses the bank of Outer Mongolia). Most users receive their license keys withing a few hours. Looking at the records it looks like you should have yours by now.Make sure to check any spam filters as this mail comes from sales@sourceboost.com, so the mail frequently goes their. Regards Dave
  4. This will be a problem. A separate asm file can't be included in the project. The options: 1) Use inline asm within a C function. 2) Build the code using MPASM (or another assembler), Cut and paste the resulting op-code data into one of the projects source files. Edit it around and use #pragma DATA to make it part of project code. Use "asm call 0x0123" (or what ever the address the code is at to call the function. Regards Dave
  5. Paul, The best option here is to wrap the asm code in a C function, ie use the inline assembler. Regards Dave
  6. Fixed in latest target files, look here:http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  7. TomF, You can find details of some of the significant changes here:http://forum.sourceboost.com/index.php?s=&...ost&p=17538 Regards Dave
  8. TomF, Why not try the installation supplied sample program ?You can find it in "C:\Program Files\SourceBoost\Samples\C\BoostC\lcd.__c" if you install the SourceBoost package with the default path. Regards Dave
  9. peter s, Yes it was quite a bit of work. Fortunately this work was almost complete when you asked for it. Regards Dave
  10. Corrected header now available with other new targets files. Look here: http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  11. Zoom, Thanks Dave. Proper release files now available.Please take a look here: http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  12. So how did you get around it? This issue is caused by an error in the .tdf file (Target Descriptor File), this is now fixed the latest release files for the PIC16F1823.Please take a look here: http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  13. Zoom, Please take a look here: http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  14. Peter, Please take a look here: http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  15. Nima, Please take a look here: http://forum.sourceboost.com/index.php?s=&...ost&p=17634 Regards Dave
  16. Hi all, BoostC/BoostC++ V7 compiler now supports the following additional 35 target devices: PIC12F1822, PIC12LF1822, PIC12F1840, PIC12LF1840, PIC12F617, PIC16F1823, PIC16LF1823, PIC16F1824, PIC16LF1824, PIC16F1825, PIC16LF1825, PIC16F1826, PIC16LF1826, PIC16F1828, PIC16LF1828, PIC16F1829, PIC16LF1829, PIC16F1847, PIC16LF1847, PIC16LF1902, PIC16LF1903, PIC16F1938, PIC16LF1938, PIC16F1939, PIC16LF1939, PIC16F1946, PIC16LF1946, PIC16F1947, PIC16LF1947, PIC16F707, PIC16LF707, PIC16LF720, PIC16LF721, PIC16LF722A, PIC16LF723A You can download the required updated files from here: http://www.sourceboost.com/CommonDownload/..._04-11-2010.zip The files will need to be manually copied to the appropriate destinations. Regards Dave
  17. Zoom, This looks to be related to the .tdf file you are using (PIC12F1822) which is not a proper release version yet. The var not found is actually the FSR register, there may be an error in the TDF in that respect.I'm still investigating the problem along with working on support for some new target devices. Regards Dave
  18. Zoom, A more complete program example would help. Regards Dave
  19. TomF, You are entitled for a free upgrade to version 7 if you purchased your BoostC 6.x license after February 1st 2010 (email us your current license info and we'll send you your new 7.x key). Upgrades of Pro licenses also include free Novo (Goodies) upgrade. If you purchased your 6.x license before February 2010 you'll need to buy an upgrade license, you can find details here: http://www.sourceboost.com/Products/BoostC/Upgrades.html Regards Dave
  20. iank, Thanks for the update. Now we can correct the header file. Regards Dave
  21. Attached are pre-release versions of the header and tdf files. You will need to add the fragments of map.txt and BoostCPic.h to your existing files. I already notice a few tweaks required, 16F1823: 1) Delete duplicate W and F register value definitions 2) Delete eedata register definition You will see these errors when you try to compile, do that to make them easy to find. Regards Dave PIC16F1823.zip
  22. babos, 1) Please try building the project under SourceBoost IDE. 2)Try copying the .obj files from you laptop to your desktop and then just try linking them there (can only be done from with Sourceboost IDE or a command prompt). This will indicate whether it is the building the .obj files on your laptop that is causing the issue. Regards Dave
  23. John, To use V7.0 you may need a new license, it depends when it was issued.If you purchase your license from May 2010 you are entitled to a free upgrade to V7.0 Regards Dave
  24. There are some supplied project files to build all the supplied novo RTOS libraries. They have a .c file that contains the following // build novo library with appropriate configuration #include "novocfg_pic16t3e1ts2.h" #include "novo.c" The novocfg_pic16t3e1ts2.h file contains the configuration information for the build, in this case it is for a PIC16 library with 3 tasks, 1 event and timer size of 2 bytes. If both high and low priority interrupts are using Novo RTOS functions (macros or true functions) then to protect from corruption the high priority and low priority interrupts will both need to be disabled. Critical Sections will needed in the low priority interrupt routine around any Novo RTOS functions calls (or macro invocation) to prevent corruption by the high priority routine. I hope that helps. Regards Dave
×
×
  • Create New...