Jump to content

ddr

EstablishedMember
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ddr

  • Rank
    Newbrie
  1. I recently upgraded to 7.2 from 6.95. I needed to support several new PIC controllers and had to upgrade. After I upgraded none of new projects will link including my old 6.95 projects. I never had a problem linking with 6.95. It appears that the linker does not like spaces in files names. I suspect its a simple fix. Enclosed below is the link log. Notice there are no double quotes around the Debug\16F1825 IO v1.obj parameter Can anyone help me to resolve this problem? Thanks. Building... "C:\Program Files\SourceBoost\boostlink_picmicro.exe" -idx 1 /ld "C:\Program F
  2. If you (or anyone) figures this out let me know MLAB has the programming features available within the MLAB GUI. However, MLAB may simply have a version of the PICKit programming applicaiton embedded in it.
  3. It was the 2nd config word which was not defined. Sloppy coding!! After defining both config words it worked like a charm. Interesting that it worked with the previous version of Pickit - the strict check must also alter the way it programmes the device as compared to the older version of PicKit software. Thanks for your assistance.
  4. Anyone having problems programming with latest software version of PICkit 2 (v2.55.01). I have been using PicKit v2.40 with BoostC 6.90 to program PIC 16 and 18 devices without problem. I recently upgraded to v2.55.01 and programming fails. I get the following warning in the PICKit 2 application when programming a PIC 16 device (16F88): Warning: Some configuration words not in hex file. Ensure default values above right are acceptable. Any thoughts or ideas?
  5. I suspected this had something to do with BoostC. Thanks to all for their input & assistance!!
  6. Disabling LVP has no affect. I'm using PICKit2 to program with ICSP as per PICKit 2 documentation. I'll check out the PICKit forum to see if others have had similar problems with programming devices. I tool a look at the asm from pic18 and from pic16 generated code and I noticed that the code is quite different for both devices. I'm no asm guru (this is why I'm using C). I recall seeing something about legacy mode and I found a config parameter (XINST) for legacy mode. When I disabled extended instruction set, it works perfectly!! Do you know why this should make a difference?
  7. Sorry I don't know how to add to your source code or how to check it via simulator. Code enclosed below. Hardware config was my first thought. The 18F2620 uses EUSART instead of AUSART but I was told (from Micorchip forum) its bascially the same. The difference is 16 bit baud generator and autobaud (both disabled in my configuration - see below). I will also post init code on Microchip Forum to verify. Thanks!! #pragma CLOCK_FREQ 20000000 // 20 Mhz #pragma DATA _CONFIG1H, _OSC_HS_1H & _IESO_OFF_1H & _FCMEN_OFF_1H #pragma DATA _CONFIG2L, _BOREN_OFF_2L #prag
  8. Thank you for pointing that out. Typo in post. No typo in code. I don't think the linker would like that Its supposed to be sendString and sendChar. Sorry bout the confusion. Any help or suggestions would be greatly appreciated.
  9. Thanks. Funny thing is that sendChar in a loop works fine. For example: for (i=0; i<5; i++) putChar ('A'); // Works fine every time!! where as printString does not work printString ("AAAAA"); // Does not work I thought of timing so I put a delay (200 ms) in the while loop within printString and it does not work. i.e. void sendString(const char* text) { char i = 0; while(text != 0) { sendChar(text[i++]); // Does not work delay_ms (200); } } Next, I tried Windmill (thnks for tip) and it rece
  10. Help. I am lost and at end of my rope. I'm trying to print stings from 18F2620 using library SUART function thats on the l i k a . b e web site (link found on sourceboost.com). I've been using the same code sucessfully with PIC16 (16f88, 16f777, etc) without any problems!!!! I am NOW trying to get the routines to work on 18F2620 and it won't work. I can send a character ok, I can receive a character ok (i.e. serial link is alive and well). However when I try to print a string I get gibberish (like baud rate is incorrect - but its not since I can send/receive characters). Is this
×
×
  • Create New...