Ian Harris

How about multiplying by 100, rounding that result, then dividing by 100?

Very happy to play with a beta stack. - Ian.

Jorge, Good find. I removed the files one by one until I found which one made it crash. I was fooled since I didn't think SourceBoost looked in the source files as it started, but it must do to read the "todo" list. volatile unsigned long ulSmartConfigFinished, ulCC3000Connected,ulCC3000DHCP, OkToDoShutDown, ulCC3000DHCP_configured; and OkToDoShutDown = 1; were the lines in the source files to cause the IDE to crash on startup. Changing them to "OkToShutDown" allows the IDE to startup okay. cheers Ian.

Hi all, Running 7.11 and it has an annoying habit of crashing on loading certain project files - even one I have just created. Once it does this, of course, then next time it starts up it tries to reload the project and crash again. Here's a project file that crashes every time. Tried uploading but the forum says I'm not allowed to upload that sort of file. [settings] Target=PIC18F26K22 Active Compiler=BoostC Active Directory=D:\TI\CC3000BasicWiFiApplication\Basic WiFi App Sourceboost Source\ Active Config=Debug Last Ext=h Type=0 Warnings=2 Model=0 [Files] Count=24 F

Hi Jorge, The PIC18F8X20 range of devices do have an external memory interface - but they only run at 10MIPS, which is not quite enough for our applications.</p> It's the RAM that's really the problem, I would swap half the flash for more than 4k of RAM. Still, getting more than 16MIPS of performance would certainly help too. cheers Ian

So having finally got to the point now where we need to do projects with the PIC32 (actually, the problem is RAM, not processing power, but you might as well make the step to 32 bits) and start the process of porting things to the Microchip compilers. It reminds me what a joy it is to work in the clean, straightforward world of Sourceboost. Let's ignore the fact that MPLAB is extremely unfriendly and confusing, or the fact that you can easily (accidentally) spend ages reading help files only to realise that the help is for the HITECH C compiler and not the C18 compiler (or the XC8 compile

Prompted by a comment made by Dave Jones on the EEVBlog we are looking at producing an "Arduino" compatible hardware platform based on a PIC microcontroller (and sourceboost, naturally). I confess to not knowing a great deal about this platform other than the fact that it's everywhere, and it is based on AVRs. This would allow BoostC / Microchip users to play with the same "shields" (daughter boards) that are prevalent in the Arduino community while maintaining your existing code base and development environment. There may even be some interest in porting the "sketch" platform as well

I'm not sure if this has already been mentioned (the thread is quite long), but a complete USB CDC and HID implementation is available in the PicPack library (clean room USB implementation using SourceBoost). Complete source, examples etc. It's under active development, in fact, within a few days we should have it working with the fantastic 18f14k50 chip, meaning you can do your own USB serial port with a completely customisable PIC chip for less cost than a SiLabs or FDDI chip. We'll have some hardware supporting all this available shortly. Suggestions, problems, ideas, bug (fixes),

PicPack 3.0 has been released - a bunch of source code designed to help make your life easier programming the Microchip PIC, using SourceBoost. Please see www.embeddedadventures.com Enjoy! Supported devices FM Radio: AR1000 Temperature sensors: DS1631, TMP75, LM75 Real Time Clock (RTC): DS1307, M41T81S LED display (4 digit): HC4 Digital compass: HMC6352 IEEE 802.15.4 transceivers: MRF24J40 Propriatry transceivers: NRF2401A LCD display Pressure sensors: MS5540 Humidity sensors: SHT15, SHT11 Audio player: SOMO-14D Functionality Software i2c Audio queue Deb

Raghunathan, I would be very happy to work with you on integrating HID maker, at least, if what you mean by that is producing SourceBoost C as opposed to Microchip C code. It looks like a very neat tool. We have a USB stack up and running in SourceBoost C and will be doing some development work on that over the next few weeks. cheers Ian. Hi, for all those who find USB difficult can try a simpler way of implimenting USB in ur PIC projects. http://tracesystemsinc.com/all-usb-product...ucts-alias.html Dave & Pavel, it will be nice if BoostC can be integrated in H

Just load the .hex file in mplab (File | Import) and program it by choosing a programmer (eg PicKit2). Quick and harmless. Alternatively, you can use the pickit2 utility itself (if you have a pickit2), or for more fun and easier debugging, use a bootloader (there are stacks around). cheers Ian.

Just a note for the others, thanks to the excellent Sourceboost support, the problem turned out to be: #ifdef _PIC18F26K20 #define turn_analog_inputs_off() clear_bit(adcon0, ADON); #endif #ifndef turn_analog_inputs_off() #define turn_analog_inputs_off() \ #warning "!!! - See pic_utils.h for turning off analog inputs on your pic" #endif Since I was using a new PIC, the code was designed to alert me that there was no turn_analog_inputs_off() routine by issuing a warning if it was used. Turns out that creating a #define using the #warning (which is a preprocessor function) withi

Let me know how you go. It's a great compiler, with great support. cheers Ian.

Thanks Pavel, project sent. kind regards Ian.

Hi guys, Having some fun with the new 18f14k50 chip - when compiling to this target, the compiler fails to compile, despite compiling fine for another target (eg 18f26k20). The failure lines don't appear to make much sense, sometimes it's a pragma line (as in this bootloader): Building... BoostC Optimizing C Compiler Version 6.97 (for PIC18 architecture) http://www.sourceboost.com Copyright(C) 2004-2010 Pavel Baranov Copyright(C) 2004-2010 David Hobday Licensed to Ian Harris under Single user Pro License for 1 node(s) Limitations: PIC18 max code size:Unlimited, max RAM banks:Unlimi

Panvadee, The LF and F devices are identical from a code perspective - they only differ in that the LF devices can typically handle lower voltages and/or higher clock speeds at lower voltages. As far as sourceboost is concerned, pick the pic16f648a and you'll be fine. cheers Ian.

Are you running your PIC with an external crystal or using the internal rc oscillator? Obviously the crystal is going to give you better results. cheers Ian.

Hi Darshan, How are you going now? Can you post the debug output from the pic? regards Ian.

Tim, Count me in. I have produced my own simple wireless mesh solution, but would also be happy to see if we can produce a full zigbee stack just for the fun of it as well. kind regards Ian.

:-) Okay to be clear: if you don't explicitly initialise a variable, eg, int my_variable; it *will* be initialised to 0 unless you use the command line switch. In a lot of cases it really doesn't matter what the initial value is, you can save memory by not forcing everything to zero. cheers Ian.

No, it's the other way around. SourceBoost will initialise your variables to 0 unless you have -Su ( disable initialization of uninitialized static variables) on the BoostC command line.

Hi Tim, I've got a couple of those - actually the version "B" now - but it's the same base chip from what I recall. I've been planning to get those going under sourceboost for a while, so now might be a good time. cheers Ian.

You can located functions at particular addresses now, the syntax is void foo1() @ 0x100 { // do something } If you want all functions located in an area of ram, use -rb or -rt in linker options. Unfortunately there is no pragma for this yet.

Any idea when version 7 will be out? I check the web site every day in eager anticipation...Hoping perhaps that it supports 16bit PICs... kind regards Ian.

Nice work, some great projects there!