Jump to content

Reynard

EstablishedMember
  • Content Count

    687
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Reynard

  • Rank
    Maniac
  • Birthday 11/26/1953

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Scotland
  • Interests
    Archery - target and field
  1. Hi Manfred, You are absolutely correct, the compile button or drop down menu compile does not work. The source file is saved, the object file seems to get deleted and that's it. Not a user of the compile button myself, always the F7 (build). It may get fixed one day in the far future. Cheers Reynard
  2. Hi Manfred, As far as I know spaces in file names have never worked as spaces are command line delimiters. Spaces are allowed in directory names. I am not sure what you are saying in your first post. You only have one file in your project and you got the response "Done" after the compile. What were you expecting to see ? Cheers Reynard
  3. Hi Manfred and welcome to the SourceBoost forum. If the project was created using 7.3 before you upgraded to 7.43 then you should clean the project using Build-> Clean All to remove all the previous make files etc. Other than that there should not be any problems if you are using the F7 key to compile and link. If you are using Novo libraries (or any of your own libraries) then you should rebuild them with the newest compiler or the linker may complain. Good luck with your project. Looks like it may be a Nixie tube clock. Cheers Reynard
  4. I have been using SourceBoost with Win 10 for several years now without problems. Works the same as it did on XP. Currently V7.43. Register the program as administrator or it won't work. Cheers Reynard
  5. Go to the Microchip web site. Select the page for your chip (PIC16F1788). Select the documentation tab and it's under Programming Specifications.
  6. Hi mityeltu, The programming manual page 35 suggests the base address for EEPROM is at 1E00h. Cheers Reynard
  7. Go to Settings menu and select Toolsuite… There you will find Chameleon. Cheers Reynard
  8. I have been using SourceBoost for 10 years now and never knew it put all that extra code into the startup section for rom arrays. I suppose that is because the IDE shows the .casm file which doesn't show all this extra stuff. We will just have to make sure to write code that doesn't crash and test it well. Function pointers taking arguments usually causes me problems. Can't seem to use the arguments unless I copy them into a local first variable. Maybe it's just me. But as you say a great little compiler. Novo is usually in every project I do. Cheers Reynard
  9. Hi DTPIC, That's handy. My current project uses a 40 pin PIC18F46K22. Thanks for the info and I will have a look into it. Cheers Reynard
  10. Are you using a PIC 16 or PIC 18 ? My current project is for PIC 18 and I have 70+ rom char arrays both string and byte arrays. All the arrays are stored consecutively in program memory. Accessing the arrays is through an index which is a constant. If my arrays are each occupying 256 bytes I would know about it. Can you supply Dave and Pavel with code showing what you believe to be experiencing. Cheers Reynard
  11. Hi Jorge, Maybe borrow is better. I did say or other similar compiler. The MikroC PRO for PIC or ARV stdint.h files are very nice for SourceBoost use. But if you want to do your own typdedef and use float.h you could try this: #ifndef _FLOAT_H_ typedef unsigned char uint8; #endif Cheers Reynard
  12. So it's a bug then ? The current version of SB 7.42 doesn't ship with a copy of stdint.h. Not all novices know to steal a copy of stdint.h from gcc avr (or other similar compiler) and use that. Cheers Reynard
  13. In the header file <float.h> there is the following code. // define types #ifndef uint8 typedef unsigned char uint8; #endif According to the manual an identifier can only be defined using the #define directive. The #ifndef in this case is worthless and not doing the expected job. When I do this, // define types #ifndef uint8 typedef unsigned char uint8; #endif // define types #ifndef uint8 typedef unsigned char uint8; #endif the compiler complains as I am redefining uint8. The second typedef is not being blocked. So what is the #ifndef suppose to do here ? Cheers Reynard
  14. Hi Jorge, I did my own implementation to get what I needed. The sprint does do negative numbers as well but sign is still in the wrong place (0-1 for -1). As you say it is a bit of a heavyweight. I am running at 64MHz with 64k rom PIC18 so not much of a problem. Cheers Reynard
  15. Hi Jorge, It is confusing to the reader when the prototype says unsigned int but I suppose they had to say something as the function is non standard to normal C. The output is still incorrect whether you specify +1 or -1 as the value. Cheers Reynard
×
×
  • Create New...