Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TimC

  • Rank

Profile Information

  • Gender
  • Location
    Boston MA
  1. Sourceboost is a great product. I just think the 8-bit micro's are not as interesting as they used to be but I still like them because they are easy to work with. Take a look at Google trends and you will see a downward slope for search terms such as Microchip, Atmel, mplab and so forth.
  2. Hi all, Here is a batch file I have been using to program my pic chips within the IDE. Before I was not able to program using the ICD3 because of the character space between the parm "F" and the hex file name. The ICD3 command line software would report back saying "enter hex file name". A separate batch file seems like a lot of work to just get rid of a single space so I added some functionality to make it more worthwhile. Enjoy Tim C =================== Batch file follows ======================== @echo off @setlocal ::Version 0.9 Boost Programmer assistant ::This bat file si
  3. Ted, You have done an amazing job recreating the old 1802. It really shows your talents! Also your work with the 1802 C compiler probably got me more interested in that chip than anything. Yup call me an old fart. Tim
  4. What is going on here?? origional post I feel very weird. I don't power up my PC quite so early in the morning. Still TimC I think
  5. Hi, Is there a way to stop the new V7.0 IDE from bringing up my external editor when I click on a file in the workspace view? The V6.97 IDE does not do this. I have *.c and *.h files associated with ultraedit for many years and has not caused problems with my other IDE/compilers. Thanks TimC
  6. Thank you Pavel for answering my question. This really is a huge advancement for small memory devices! Lots of examples will help your users understand how to use this feature and give you a competitive advantage. I have already rewritten the LCD template so that the control pins can all be on different ports but I have much more to learn.
  7. Thank You It's a start. I am looking for a software based SPI, but I could back step a little more and try this on hardware SPI platform then modify to software bit bang. One question I have yet to figure out. How do I use the templates to define more than one? For example what does code look like for using 2 LCD's (lcd_driver.h) or 2 Serial ports (rs232_driver.h) or two I2C devices (i2c_driver.h) TimC
  8. I have 3 SPI devices on an X1 micro Engineering board, DS1620 Temp, DS1302 clock and a 25LS640 EEProm. Being used for a Temperature recording project. My problem is how to reuse a software SPI.h and SPI.c files which contain all the shift in and shift out calls. Currently the calls are designed so the header file points to one device at a time. ------------------------------------------------ //#define CS_TRIS TRISA // ds1302, spi eeprom //#define CS_PORT PORTA // ds1302, spi eeprom #define CS_TRIS TRISC // ds1620 #define CS_PORT PORTC // ds1620 //#define CS_PIN 2 //d
  9. The mikroelectronika dev boards are great and getting better. I have the EasyPic4 here. Sad to say you are going to have to change your .H files. One idea is to make a multi-board header file like this: Regards Tim C // Define the LCD connections for the EasyPic4 board here // these names are defined using the Settings-->options-->compiler // and then adding the compiler option -d boardname #ifdef EASYPIC4 #define LCD_LOW_SPEED 1 // 1 if not using RW and input in data pin 7 #define LCD_E_PORT PORTD #define LCD_RS_PORT PORTD #define LCD_RW_PORT PORTD #define
  10. The SPI interface can be handled using software or hardware and by interrupts as well. Mikrobasic as I recall does not have all the options one might need. Since I am not sure what you want, here is some software bit bang driven SPI code that will work in the most situations. Also see the bottom for a link to some One Wire code. Also look for Lieven Hollevoet's code at http://boostc.lika.be Regards Tim FIRST THE H FILE #ifndef _SOFTSPI_H_ #define _SOFTSPI_H_ #include <system.h> #define INPUT 1 #define OUTPUT 0 #define SET 1 #define CLEAR 0 #define
  11. Pic to Pic one wire would be a real challenge. however you could take a look at this code: One Wire Regards Tim
  12. Hi, I have always had to go through several of the settings when changing a chip or starting a new test project. Problem is I can never remember where everything is. Like I think the menu item should say chip or uCPU but it says target, Toolsuite to me should say Compiler, Options Tools sounds like Toolsuite but means something different. Renaming some of these items might cause an uproar I think it might be much better to bring them together on one or two screens so you can see if your project is set up right, mainly if something is not working and you need to check more than your code.
  13. Pavel, Your new version 6.91 works perfectly. I do not see any of the problems I was having before. I have about 50 more bytes to play with inside the class now. I am so pleased thank you for your work Regards Tim
  14. Hi All, I have been working on a general utility that would help me with many of the one wire devices. This routine is a start and it should work with any speed uP but I have only been testing it with 20mhz devices. When using the routines with just ground and data connected I am getting about 80% success rate with crc. When using the routines with 3 wires it's 100% no bad packets for days. A simple test harness would go sort of like this: oo_tx(0xcc,0x44); delay_s(1); // give time to make temperature oo_tx(0xcc,0xbe); for(x=0; x<8; x++) { ow_temp_reading[x] = oo_r
  • Create New...