Jump to content

jartim

EstablishedMember
  • Content count

    31
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jartim

  • Rank
    Regular
  1. Unrecognised type ID

    Hi guys, I'm getting this message when I build my project - Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F Coff generation: Internal Warning: Member Var:currentCrcRomPtr Unrecognised type id:0xF000000F It doesn't appear to be causing any issues, however the compiler reports a warning so I expect there is something odd going on. Any ideas? (Compiler = BoostC++ V7.42) Regards Tim Jarrett
  2. Thanks Jorge, pretty much what I had decided to do as well. It just would be easier to have the compiler and linker do all the work for me, rather than have to build the code twice. Regards Tim
  3. Hi Jorge All I'm trying to do is calculate a CRC checksum for the ROM, starting at 0x0000 and ending at the last used address of my program, hence I need to know the last address used. I can't CRC the entire ROM because I will be using the top end for non-volatile storage, and for that I also need to know the last used address. Normally I would edit the linker control file and add a label after the used code section, but this compiler doesn't appear to use a control file, I guess it has the parameters hard-coded in. All I can do at the moment is build the code with a 0x0000 address coded in as a rom char* pair, look at the code statistics after the build process, copy the size of the code in to the rom char* and then re-build. It would be safer and easier to have the compiler and linker do it automatically. Regards Tim
  4. Hi guys, Is there any easy way of identifying the last used address in rom using BoostC or BoostC++ compilers? I cannot find a linker control file to add a label, is there any way to guarantee that a label defined in the source code ends up as the last addressed object? Thanks Tim
  5. Another request, not much luck with enhancements so far but worth a punt... Please can you add support for friend functions for classes? Thanks.
  6. A long shot I know, but what are the chances of the source code being moved to an open-source licence? That way maybe there could be more third-party improvements and bug fixes etc. Just a thought. (I would certainly be interested in adding new features, i.e. 12-bit support, true template support, overloaded constructor support etc.) Regards Tim
  7. Please can you add support for the 12-bit baseline devices to BoostC and BoostC++? Some of these have relatively large FLASH and register memories but have a 12-bit instruction-width core, which the current compiler doesn't support! Regards Tim Jarrett
  8. Pavel, I don't think this is correct? I'm using MPLAB-X and I've added a new header for a PIC16F570 device and modified the MPLAB jar files to allow me to use SourceBoost with that device (it doesn't by default). I haven't created a .tdf file for the same device because I don't use the SourceBoost IDE, but when I try to build under MPLAB-X, I get this message - main.cpp error: could not open input file 'C:\Program Files (x86)\SourceBoost\config\PIC16F570.tdf' So it appears as though the build process needs the .tdf file as part of the build as well (this is using the C++ compiler under MPLAB-X). I will have a go at creating one for my new device. If it's successful, is there somewhere I can post it on the forum to make it available to other users? [EDIT] Pavel, is there a full list of the options that can be used in the .tdf file entries? I found a .txt file in the config folder that partly explains the .tdf file format, but it does not give a complete list of all the possible options? Rgds Tim
  9. Thanks Pavel. Will you be doing a similar exercise with an alternative to the BoostC++ compiler as well, or does Chameleon already support C++? Thanks Rgds. Tim
  10. Guys, No disrespect, but why would I want to use the Chameleon compiler instead of the BoostC compiler, especially as it is only 95% back-compatible? Does the Chameleon compiler give any better performance, smaller object code, better optimisation etc? Many thanks. Tim Jarrett
  11. Ok, found the problem. I had a member function and a member variable in one class, both with the same name, and that caused the compiler to fall over. Changed one of them and everything is compiling again.
  12. My build keeps crashing with the following error code, any ideas what this code means, please? make[2]: [build/default/production/PortClass.o] Error -1073740777 (ignored) Windows reports that the program has stopped responding when this happens, so my guess is that this is an internal compiler error?
  13. Can't register the licence?

    Hey Chris - I purchased the BoostC++ compiler a couple of months ago, and received the licence information from SWReg as you did. But, before I had chance to enter the licence, I received an email from Pavel with a different licence key to use instead. I got the impression from other posts on the forum that they had had problems with the licence server and were emailing the keys out manually. Not sure if this still applies or applies in your case, but worth an email to "support" ? Rgds Tim
  14. Hi Jorge I agree, the coding looks a bit odd as it stands; it wasn't meant to be an example of how to do it, rather an example of a possible way the compiler could implement a solution. The syntax looks strange, but it's not breaking any of the compiler's rules or the C++ language rules. Having two structure members at non-consecutive addresses is quite acceptable, in fact many C-compilers do just by adding padding bytes between members when the target processor requires each member to be aligned on 16 or 32-bit boundaries. My suggestion just tries to force the alignment rather than assume that the compiler will do it (it probably won't). As for the compiler not accepting a variable as a bit index, you're correct, but as you said - so I cannot see any reason why the compiler could not be modified to do this. Rgds Tim
  15. Hi, not really a request for an enhancement to the compiler, but it would be really nice if you would occasionally post on the forum what developments / improvements / bug fixes etc you are currently planning and/or working on for the Boost compilers. IMHO the forum is pretty quiet and it's not filling me with confidence that this product is being actively developed or supported. I'm having a difficult time convincing my client that this is the compiler for their project development, any information posted would help give your current and potential future users and customers a bit of a moral boost (no pun intended ).
×