Jump to content

rlang

EstablishedMember
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rlang

  • Rank
    Regular
  1. The types of changes that I had to make included were: 1. How fixed memory is allocated. 2. How binary constants are defined. 3. How bit variables are defined. I did not know there were any options to turn on/off optimization in BOOSTC. Could you tell me what they are? I noticed that you did not have any USB examples in BOOSTC examples. Feel free to use the source I sent you on 2/13 (usbtestcc.c) as a working example.
  2. I have finished debugging my USB to MIDI interface for the PIC18F2455 chip with BOOSTC. I decided to recompile using the C18 compiler from Microchip. Converting the source to C18 reqired a lot of changes. I had the following results: PROGRAM SPACE USED (OUT OF 24K) BOOSTC 9445 C18 7616
  3. I'm sorry, I condensed too much of the program. The actual problem is shown below. Note that byte2 is never set. // microprocessor is 18F2455 #include "system.h" //pic definition files required by boostc typedef struct { unsigned char cable; unsigned char byte0; unsigned char byte1; unsigned char byte2; unsigned char running_status; unsigned char expected_bytes; unsigned char wait_bytes; unsigned char sysex_ctr; }midi_rec; midi_rec mymidi; void itsasub(midi_rec *midi) { // when this program is executed midi->byte2 is never set equal to 'A' // even though midi->wait_bytes is equ
  4. Bug description: Structure variable testing produces incorrect results. Program compiled and executed with IDE 5.9 and BOOSTC 2.0.1 Steps to reproduce: 1 Compile the following program and execute in debug mode watching variables midi->wait_bytes and midi->byte2. // microprocessor is 18F2455 #include "system.h" //pic definition files required by boostc typedef struct { unsigned char cable; unsigned char byte0; unsigned char byte1; unsigned char byte2; unsigned char running_status; unsigned char expected_bytes; unsigned char wait_bytes; unsigned char sysex_ctr; }midi_rec;
  5. Memory allocation I have used the following statements unsigned char * tobuffer; tobuffer = (unsigned char *) (0x550); in a subroutine to to allocate a buffer at 0x550 in General Purpose Register/USB Ram for use by USB. I would like to globally allocate a buffer at 0x600 to be used as a serial buffer by all the subroutines in a program. Do I have to allocate the same buffer and address in every subroutine that uses it? A more general question is if I just allocate a global buffer with unsigned char * mybuffer; at the beginning of the program what prevents m
  6. Internal Error: Unable to resolve label ID:0x100002F6 Failed Exit code was -1. [No error.] Through trial and error I determined what was causing the above linkage error. I had incorrectly used a logical AND when I should have used a bitwise AND. if (portc && 0x01) {} instead of if (portc & 0x01) {} Maybe a better error message could be developed. Thanks for your help. Rob
  7. I installed the missing TDF file you sent however I still get the error above during link and do not know what it is telling me.
  8. I changed two lines that were causing all the constant errors. I changed while (!btxif); // wait until tx register is empty to while (btxif == 0); // wait until tx register is empty (note that line is in your serial driver example) I now get the following error during link BoostLink Optimizing Linker Version 2.0 Beta Reading:C:\SBOOST\config\PIC18F2455.TDF failed Failed I noticed that the PIC18F2455.TDF was missing from the 5.9 IDE release, so I made a copy of PIC18F4455.TDF and renamed it PIC18F2455.TDF. Now I get some sort of internal linker error BoostLink Optimi
  9. Bug description: Program that compiled and executed with IDE 5.8 and BOOSTC 1.9.3 will not compile with IDE 5.9 and BOOSTC 2.0 Steps to reproduce: 1 Program that previously generated on compile time errors now generates the following: BoostC Optimizing C Compiler Version 2.0 Beta (for PIC18 architecture) usbtest.c(233:10): warning: '!' operation has no effect usbtest.c(885:12): error: l-value specifies const object usbtest.c(885:12): error: failed to generate expression usbtest.c(886:10): error: l-value specifies const object usbtest.c(886:10): error: failed to generate expres
  10. rlang

    Boost 1.92

    The fix implemented by Pavel in BOOSTC 19.3 for the array bug worked like a charm. Thank you for your quick response. The PIC18F2455 USB mouse example now works with BOOSTC. I can send if to you to use as an example if you wish. Rob
  11. rlang

    Boost 1.92

    I need code where I can reproduce the problem. Yous code looks too big and I assume it includes ather stuff as well. Will I be able to see the problem running it under simulator? Regards, Pavel <{POST_SNAPBACK}> I sent a short version of the project files called bug6 to the support email address as a zip file. Rob
  12. Since only strings are supported in rom in BOOSTC, I was wondering if there a way to put hex data into a string? I don't want to translate to decimal. unsigned char * mystring="\15\16\17"; works but unsigned char *mystring="\xF\x10\x12"; does not
  13. rlang

    Boost 1.92

    It is about 24 pages of code but I can send it to you at the support email address if you wish. Rob
  14. rlang

    Boost 1.92

    Bug description: BOOSTC 1.92 array data not recoverable Steps to reproduce: 1.) I create a 50 byte array with the following lst file 1A78 0E05 MOVLW 0x05 1A7A 6E3A MOVWF gbl_ReportDescriptor1 1A7C 0E01 MOVLW 0x01 1A7E 6E3B MOVWF gbl_ReportDescriptor1+D'1' 1A80 0E09 MOVLW 0x09 1A82 6E3C MOVWF gbl_ReportDescriptor1+D'2' … 1B00 0E30 MOVLW 0x30 1B02 6E5D MOVWF gbl_ReportDescriptor1+D'35' 1B04 0E09 MOVLW 0x09 1B06 6E5E MOVWF gbl_ReportDescriptor1+D'36' 1B08 0E31 MOVLW 0x31 1B0A 6F5F MOVWF gbl_R
  15. Bug description: BOOSTC 1.8 defines unimplemented configuration memory Steps to reproduce: 1.) Compile program for PIC18F2455 #include <system.h> #pragma DATA _CONFIG1L, 00100100b #pragma DATA _CONFIG1H, 00001111b #pragma DATA _CONFIG2L, 00111111b #pragma DATA _CONFIG2H, 00011110b
×
×
  • Create New...