Jump to content

reality

EstablishedMember
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About reality

  • Rank
    Newbrie
  1. Oh, Look! A manual! Yeah well -- I admit I didn't open the manual, I ran a search on google and didn't found much -- I knew itoa but since it didn't seemed to work first time I abandoned the concept thinking it was an unimplemented one. Sorry And thanks alot for your help (Well... Next time some1 googles this out, they might find THIS answer so I don't feel that useless in the end hehe)
  2. Well I know this seems like a newbie question but I can't find my solution to it ... What is the magic trick to convert an int to a char*? All of the good ol' tricks used in C doesn't seem to help here. Any advice?
  3. Hi, (again) Here is my first project under BoostC, which I'm giving away for you to use as you want. This GLCD library is originally made for the 18F* series but could easily be used on a 16F one - it doesn't do more than the others out there but it's free, and I found nothing that would work the way I wanted and that would be compilable under BoostC. There are still some 'todos' but so far so good, it works, compiles, and do what I needed it to do -- If you're enhancing it, you're welcome to share your codes lcd.zip
  4. I posted that on another thread previously, but keeping things in order doesn't hurt. Here comes the wish list; - ICD / ICD2 integration to the IDE - Generally, better error reporting (the odds of "missing semicolon at line 251" while there was something completely unrelated on line 5 instead) - More chips support for the boost wizard (especially for the more complex fuses of the 18 series) - Some embed gadgets like a binary <> hex converter would really save us hours -- eg. select binary from code, right click, pick "convert to hex". That's it for now ... Oh, wait; PLEASE, make some better icons for the build/compile etc things So far so good, I'm with 6.81 and the IDE as well as the compiler are awesome pieces of software for the buck. For all the peoples out there who are shy of pushing the purchase button, I'm telling you you're doing the right thing
  5. Whew! Well thanks, I did it that way and that's 6 arrays... I'm not especially proud of doing it "the patch way" but what can we do eh! That said, nice library you've got there
  6. M'kay so after reading that; http://forum.sourceboost.com/index.php?sho...32&hl=0x100 and after a couple compile errors (arrays can't exceed 0x100), I'm wondering how you guys deal with arrays that -needs- to be bigger than that? I'm actually writing a glcd library and I need to store my font(s) somewhere ... Any clue?
  7. Hi Paolo First: You're awesome I performed the tests on this connection (and I did it twice with the multimeter before I posted so I don't look like an idiot) and again I had good readings. I kinda got tired of trying to keep up with the results holding the test leads, compiling, looking at the display clicking anywhere and I wanted a full trace of what happened on that port from time zero so I decided to hook it up to the oscilloscope and log the activity; At the led (after the resistor), I had an oscillating ~1.2 > 3v at about 30 hertz, before the resistor, a steady ~+5V. So... I invented the oscillating resistor, and you where absolutely right: a component that is worth 1 penny ruined 4 hours worth of brain-time trying to figure this out, and I DO look like an idjot! Thanks a lot.
  8. Hey, thanks for the re. I actually had pbaden configured to be set as IO on reset, etc. Actually a few minutes after I posted, I managed to progress and all of the leds are going on but one, I've searched the specs up and down at least 3 times but I still can't figure it out. Here is the code; #pragma DATA _CONFIG1L, 00000100b #pragma DATA _CONFIG1H, 00001110b #pragma DATA _CONFIG2L, 00111110b #pragma DATA _CONFIG2H, 00011110b #pragma DATA _CONFIG3H, 10000001b #pragma DATA _CONFIG4L, 10000001b #pragma DATA _CONFIG5L, 00001111b #pragma DATA _CONFIG6L, 00001111b #pragma DATA _CONFIG6H, 11100000b #pragma DATA _CONFIG7L, 00001111b #pragma DATA _CONFIG7H, 01000000b #pragma CLOCK_FREQ 4800000 void main() { adcon0 = 0B00000000; adcon1 = 0B00001111; adcon2 = 0B00000000; trisa = 0B00000000; trisb = 0B00000000; trisc = 0B00000000; porta = 0B11111111; portb = 0B11111111; portc = 0B11111111; - I have a led connected at; RA0 to RA5, RB0 to RB7, RC0 to RC2 They will all go on and do what they should BUT the one connected at RB4 which just refuse to shine. Specs states something multiplexed there on that serie but not on the 18f2550, nothing else that I can see from the documentation. Tried another chip; Check Tested the connections; Check Tried some other leds; Check Pulled hairs off my head; Check I'm going to go all over the doc once again and check with the errata papers as well - but if anybody has the solution on the top of their head, that would be awesome! - One line about the software; I used it for less than a week, purchased it yesterday and I'm a happy guy for now. Odds; lack of examples, libraries, documentation in general; and those 4 compile/build buttons looks really bad - Integration with ICD/ICD2 in the future would be great - I know it's MC's protocols and a heck to deal with but I would rather use the SB IDE as MP's GUI is more "tv repair guy" friendly, not programmer friendly :/ Since I'm going to try and stick to this software I might code some libraries based on it. If I would like to share my work and help this community, where should I post?
  9. Hi there New customer, new to BoostC and new to this forum; don't be too rude Ok so here is my first question, concerning a 18F2550; I've been trying to code a library for one full day and started over twice; desperate, I made myself a "debug board" by putting leds on all the ports I was using to discover half of my ports where not initialized (and/or set) correctly; now I thought this was some progress but I'm quite lost on what is the right way to deal with TRIS, ADC and PORTs registers. I have actually tried the hex method; trisa = 0x0F; porta = 1; I have tried the binary one; trisa = 00000000b; porta = 11111111b; I have tried the one-by-one way; trisa.0 = 0; trisa.1 = 0; ... porta.0 = 1; porta.1 = 1; ... nothing seems to completely do the job, I have different sequences of leds that will go on but no method so far managed to do it right and turn them all on. I've played with adconX and cmcon to turn all ports to IO mode and it doesnt seem to help much. If someone could provide me with the right method to do it under boostc, that would be great. Details: "absolutely required ports to be in IO output mode": A3, A4, A5, B0 to B7, C0, C1, C2. PIC 18F2550, HS clock at 20mhz Thanks
×
×
  • Create New...