Jump to content

doozer

EstablishedMember
  • Content Count

    29
  • Joined

  • Last visited

Everything posted by doozer

  1. Where do you get ICD2Prog.exe ? http://piklab.sourceforge.net/download.php libusb (needed) http://sourceforge.net/projects/libusb-win32/
  2. Thanks for the info. For the moment i've compressed 2 functions into 1 which got rid of the warnings. Matt.
  3. Hi All, Got the following warning whilst compiling this morning: Building CASM file Serious Warning: Call stack usage exceeds:8! Call Stack Usage Report ======================= main and Task(s): hw used:7, exceeded by:0 interrupt: hw used:2, exceeded by:0 My question - Given 7 < 8 is this something I need to be worried about? Or is the issue that 7 + 2 > 8 ? ie. Does BoostC add an extra stack call (or two) and thus cause problems, or is it just warning me i've hit the maximum, or have I already exceeded the limit? Boring stuff: SourceBoost 6.91, 16F876A 20MHz.
  4. I'll admit this is small and petty, but it catches me out every time... I often use the Browse function feature under the Workspace tab to quickly jump to a function in the source code (very cool feature btw). However it does two things which seem a little counter-intuitive: 1) Double clicking on a function name in the tree opens the file and most of the time (but not always) scrolls the first line of the function to the BOTTOM of the screen. Is it possible for this to scroll to the top so I can see the whole function rather than just its definition? 2) I use a intelli-mouse thin
  5. This feature exists for a while already. From user's manual "Sometimes it's useful to rebuild the whole project even if some project files don't need to be processed. To force a full project build use the hot keys Ctrl+F7 or Ctrl+build command". Regards, Pavel <{POST_SNAPBACK}> Ah a good old case of RTFM. My appologies
  6. Would it be possible in a future build of the SourceBoost IDE to get either a "Rebuild All" or a "Clean" compile/build option? All this needs to do is delete the intermediate files (*.obj) and all would be good. Also, when hitting build, if all files except one are up to date, why does the IDE need to recompile the untouched files? Thanks, Matt.
  7. I have just upgraded to v6.38 under MPLAB. When I build after only changing a single source file it still rebuilds all. Is this expected under MPLAB? Cheers, Matt.
  8. Many thanks Pavel. It seems when I said the latest I hadn't noticed the new build. Thanks
  9. Hi All, I'm using the SourceBoost IDE with the latest BoostC compiler. My target is a PIC 16F876A and i'm trying to read from the flash memory using Boost's built in flash routines. My very simple code is: #include <system.h> #include <flash.h> void main() { short x; x = flash_read(0x2000); while (1); } This compiles fine, but won't link (yes I added the flash.pic16.lib) to my project. I get the following errors: Failure Error: Duplicate global var:cmcon Error: Duplicate global var:eedata Error: Duplicate global var:eeadr Error: Duplicate global var:eeco
  10. I noticed the following in the help file: Do you have an ETA of when rom char * will be available? Cheers, Matt. <{POST_SNAPBACK}> Anyone ??
  11. Hi, I've been trying to define an array of strings in ROM such as: rom char *str_array[] = { "abc", "def", "hijklmnop" }; It gives the compile error: I noticed the following in the help file: Do you have an ETA of when rom char * will be available? Cheers, Matt.
  12. Hi Danmc77, Thanks for the reply. At least I know it should be possible. Did you do anything other than include icd2.h? I'm currently using a 16F876A, but have also had no luck with a 16F877A. My code is less than 2k as well. Cheers, Matt.
  13. Anybody else using ICD2 to debug? If so how did you get it to work? I still get the errors above.
  14. When I try this, it compiles and links, but after programming I get the following errors (i'm using a 16F876A): MPLAB ICD 2 Ready Programming Target... ...Validating configuration fields ...Erasing Part ...Programming Program Memory (0x0 - 0xFFF) ...Loading DebugExecutive ...Programming DebugExecutive ...Programming Debug Vector Verifying... ...Program Memory ...Debug Executive ...Debug Vector ...Verify Succeeded Programming Configuration Bits .. Config Memory Verifying configuration memory... ...Verify Succeeded Connecting to debug executive ...Programming succeeded MPLAB ICD 2 Ready Re
  15. Thanks Pavel. I read over the MPLAB integration quickly and missed that step. A simple case of RTFM... thanks again.
  16. Ok the plot thickens. I was trying to create a simple hello world project in SourceBoost that i could send in to show the problem - and of course couldn't get it to happen. So i then created a project in SourceBoost exactly as I have in MPLAB and hit build. It builds fine. Why do i get link errors in MPLAB, but it links fine inside SourceBoost? I'd love to use SourceBoost but i can't program using the ICD2 from it, and for some reason I can't import the .hex to MPLAB to get it to program it... but that's a discussion for another post
  17. Hi, When I compile i get no errors, yet at link time it seems to be having trouble with multiply and remainder functions. Do i need to manually add these libs? Cheers, Matt. PS. The problem seems to be caused by performing reads/writes to a structure defined as: typedef struct { unsigned char preset_on; unsigned char preset_off; unsigned char repeat; unsigned char channel; unsigned char state; unsigned char packet_sent; } SWITCH; static SWITCH switches[MAX_SWITCHES]; switches is a global, and i'm assuming its not acceptable to access the struct from multiple functio
  18. Hi, I'm having a similar problem. When I include the ICD2.h file it compiles fine and seems to program ok, however when the ICD2 resets and attempts to enter the debug executive it throws an error indicating it couldn't write to memory. I'm guessing this has to do with the ROM top mentioned above. How do you calculate what the ROM top value should be? Thanks, Matt.
  19. Thank you both for your quick replies. I'll give the software bit bashing a go. Cheers, Matt.
  20. Hi All, I am currently writing some control software using a 16F628. It needs to communicate with a display module that expects TTL (0/5v) serial at 4800 baud, 8 data bits, 1 stop bit, inverted data - as can be seen here: icurcuits website For testing purposes I use the Olimex range of prototyping boards that have a MAX232 chip onboard. Originall I used code such as this: void SetupUSART(void) { // rs232 communications setup txsta=0; // Transmit Status Register - init everything to 0 rcsta=0; // Receive Status Register - init everything to 0 #ifdef CLOCK_4_MHZ set_bi
  21. I had a similar problem with the RB0 interrupt triggering during initialisation. Do what I did, and simply not enable interrupts until you've given all external devices to settle down. In my code all do all my housekeeping first (rest the LCD, clear buffers etc) then enable the interrupts. Hope this helps. Matt.
  22. Thank you all for your prompt replies. I'll post back when i get this sorted Matt.
  23. Hi, Two questions: 1) When using the INTF pin (B0) on the 16f877a device, is a pullup (or down?) resistor necessary when triggering on TTL (5v) serial data? The serial data appears to be inverted (ie. 5v is logic 0). If a pullup is needed, what value? 2) Since the serial data is inverted, I need to trigger when it drops to 0v (start bit). Can i effectively do this by triggering on a falling edge rather than the default of a rising edge? Thanks, Matt.
  24. After trying several el-cheapo do it yourself PIC programmer kits the one i've had most joy with is K144. It seems to be able to program everything under the sun and comes with a license for PICALL (from www.picallw.com). The kit is on sale at the moment here in Australia. http://www.ozitronics.com/progs.html#k144 And no i don't work for ozitronics Hope this helps, Matt.
  25. Hi, When using the wizard to generate code for the 16f628 PIC i selected the "Use RS232" option under communications. Doing so produces the following code in on_init() // rs232 communications setup trisc |= 0xC0; spbrg = 0x06; txsta = 0x22; rcsta = 0x90; b_on_command = 0; i8_RS232Index = 0; set_bit( pie1, RCIE ); It won't compile as the 16f628 does not have a PORTC. Cheers, Matt.
×
×
  • Create New...