Jump to content

InLondon

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About InLondon

  • Rank
    Newbrie
  1. Hi dgille. Instead of the Microchip USB demo board, I was using a similar DIY board as described in USB demo board My goal was to get the pic to communicate with my PC software using the CDC library of Microchip and the Microchip USB bootloader. Actually, I would have been quite happy, if I was able to get the PIC to communicate with my PC software in HID or any other way. The USB bootloader worked fine, however, I didn't know how to combine the microchip CDC firmware (written in C18) with my BoostC programs. Anyway, after a day or so, I simply gave up, and now I am using the UART por
  2. Not a bug, but just a missing definition. In the include file PIC18F4550.H, we see the following declaration at the top of the file: #define ADRESL 0x00000FC3 #define ADRESH 0x00000FC4 and at the direct access definitions section at the end, we see: volatile char adresh @ADRESH; but adresl is not declared, which means we simply have to add volatile char adresl @ADRESL; to the include file. I have not checked the other include files, but the same is also missing is PIC18F2550.H Fixing this in
  3. I think I might have found the answer, by putting -rb 0x800 as a linker option. If anybody knows of better ideas or alternatives, please share... Many thanks.
  4. Hello all, Using PIC18F4550 connected via USB to laptop, and BoostC 6.15 I have the Microchip USB bootloader installed, which is working fine. This bootloader is installed in the upper memory block, and it is expecting my programs to start at memory location 0x800. If the bootloader is not activated, then it will simply jump to memory location 0x800 and start executing any code there. My question is therefore, how can I tell BoostC that the first memory location which my program is to occupy should be 0x800 ? I have tried to modify the PIC18F4550.TDF as follows: Configure Co
×
×
  • Create New...