Jump to content

diaz

EstablishedMember
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About diaz

  • Rank
    Newbrie
  1. Bit late but have a look at: http://sites.google.com/site/shaoziyang/Ho...sal-bootloadere It's for AVR's but it supports AES and PC1 encryption and these parts look fairly portable. It also has a PC app for flashing and encrypting the hex, which also has source available. I think it could be added to an existing bootloader without too much bother. It's on my todo list but it's only just been added and the list is long !
  2. Hi, Does any code exist for a bootloader on a 12F617, 12F1822, or 12F1840 device ? Thanks.
  3. Has anybody got the LCD code example by Victor Golutvin on http://www.picant.com/c2c/examples.html to work. I have tried it on a proven hardware setup, but try as I might I can't get it to work. I am using V5.0.5 of C2CPlus. Cheers
  4. I find some of the compiler warnings a little annoying. In particular Warning: Built-in variables are obsolete. Use variables defined inside the system header file This seems to be generated for every compilation regardless of whether I have actually used built-in variables or not. If I do use built-in variables then the number of the offending line would be nice. Warning: Parameter value of delay_us must be between 16 and 255 Again it would be nice to have a line number, and really I would never like to see this again as a Warning:, it should only appear as an Error: if I pick a us value outside the bounds given. At the minute this warning seems to appear whenever my code has delay_us() function in. Warning: Can't map context saving variables into mapped ram area. Check if the piccont4.pat or piccont2.pat script is used (in the 'Scripts' directory) I understand the need for this Warning but again it appears needlessly. It appears in code for which I have no interrupt() function, and if I have no interrupt function then why would I care about context saving. It's appearance seems totally unaffected by the options "Insert default interrupt handler" and "Context saving during interrupt". At least it does disappear when you pick a target that has RAM locations that are accessible from all banks. I did also manage to get the warning to disappear in a couple of my test programs that were targeted at processors without RAM locations that are accessible from all banks but I am not sure how, the warnings appearance must be dependent on another factor. I would also like the following registry entry added via the installer, so I can just double click on my project files to open them: REGEDIT4 [HKEY_CLASSES_ROOT\.c\shell] [HKEY_CLASSES_ROOT\.c\shell\open\command] @="\"C:\\Program Files\\PicAnt\\PicAntIDE.exe\" \"%1\"" [HKEY_CLASSES_ROOT\.__c\DefaultIcon] @="C:\\Program Files\\PicAnt\\PicAntIDE.exe,0"
  5. Hello, I believe I have found a rather serious error in the compiler. Bug Description --------------- Basically it is performing logical OR's before logical AND's and as I understand C's order of precedence it should happen the other way round. Steps to reproduce ------------------ It was drawn to my attention by some code posted on your examples page: http://www.picant.com/c2c/examples.html The code is listed as: This LCD sample application shows how to control HD44780-based character LCD ( by Victor Golutvin): The function LCD_icmd in the file lcdfunc.c contains the line LCD = data | LCD&0x0F (Similar lines also exist in the function LCD_cmd) This compiles to: (BTW previously in the main.h file LCD is #defined as equal to "porta") ;;;;;;;; porta = data | porta&0x0F ; bcf STATUS, RP0 bcf STATUS, RP1 movf param00_LCD_icmd, W iorwf _porta, W andlw D'15' movwf _porta Expected behaviour ------------------ Quite obviously this is doing ((data | LCD) & 0x0F) and not (data | (LCD&0x0F)) as it should be. Is the problem 100% reproduceable --------------------------------- Yes Comments -------- Fortunately the compiler does take good note of parenthesis so you can force the correct order of precedence. However in the example in question as it stands this problem stops the program from outputting anything to porta, so I am presuming the author of the program compiled it on another version of C2C. P.S. Even after forcing the correct precedence on the problematical lines I still can't get the program to work. My hardware works fine with another program. I would be very interested in hearing from anyone that has made Victor Golutvin's code work. Version Info ------------ PicAntIDE version: V5.0.5 Compiler: C2C-plus Compiler version: V5.0.5e OS: Windows 98 SE 4.10.2222 A Regards.
×
×
  • Create New...