Jump to content
Sign in to follow this  
jaero

New Devices

Recommended Posts

Hi. I want to ask for new device support, especialy newer 18F XLP 3,3V devices. Or if it is enough to write new .H and .TDF files, because my quick looking around revealed that I don't know how to set chip FLASH and RAM size. So simple copy and edit would not be possible. Maybe this thing must be for device in the "system" already. My first candidate is 18F25J11, for my GSM module :unsure:

 

Thanks, Jaero

Share this post


Link to post
Share on other sites

jaero,

Hi. I want to ask for new device support, especialy newer 18F XLP 3,3V devices. Or if it is enough to write new .H and .TDF files, because my quick looking around revealed that I don't know how to set chip FLASH and RAM size. So simple copy and edit would not be possible. Maybe this thing must be for device in the "system" already. My first candidate is 18F25J11, for my GSM module :unsure:
We are in the process of adding a lot of new devices, the 18F25J11 happens to already be first on the list.

 

Will make this available as soon as its done.

 

Regards

Dave

Share this post


Link to post
Share on other sites
Will make this available as soon as its done.
Here is a link to some new header files and TDF files: http://www.sourceboost.com/CommonDown..._21-11-2009.zip

 

PIC18F24J11, PIC18F24J50, PIC18F25J11, PIC18F25J50, PIC18F26J11, PIC18F26J50, PIC18F44J11, PIC18F44J50, PIC18F45J11, PIC18F45J50, PIC18F46J11, PIC18F46J50, PIC18LF24J11, PIC18LF24J50, PIC18LF25J11, PIC18LF25J50, PIC18LF26J11, PIC18LF26J50, PIC18LF44J11, PIC18LF44J50, PIC18LF45J11, PIC18LF45J50, PIC18LF46J11, PIC18LF46J50

 

These are really hot off the press, so currently lack any target configuration options.

 

Regards

Dave

Share this post


Link to post
Share on other sites
Can you please check that link, even with slashes replaced it points to 404... Thanks!
Works ok for me, even on different PCs in different locations.

 

Regards

Dave

Share this post


Link to post
Share on other sites
Works ok for me, even on different PCs in different locations.

:unsure: even on windows and with iexplorer, no go from my location. I don't have any proxies or filters in the path... Can you please send it to my profile e-mail? I'll be very thankful! I want to try the 25j11 support...

Share this post


Link to post
Share on other sites
Works ok for me, even on different PCs in different locations.

:unsure: even on windows and with iexplorer, no go from my location. I don't have any proxies or filters in the path... Can you please send it to my profile e-mail? I'll be very thankful! I want to try the 25j11 support...

Send me you email address and I'll send it onto you. I would post it on the forum but it's too big.

 

Regards

Dave

Share this post


Link to post
Share on other sites
Works ok for me, even on different PCs in different locations.

:unsure: even on windows and with iexplorer, no go from my location. I don't have any proxies or filters in the path... Can you please send it to my profile e-mail? I'll be very thankful! I want to try the 25j11 support...

Send me you email address and I'll send it onto you. I would post it on the forum but it's too big.

 

Regards

Dave

 

It seems to be a problem with the case of the URL.

 

http://www.sourceboost.com/CommonDownload/..._21-11-2009.zip

 

works here.

 

Regards,

 

Steve

Share this post


Link to post
Share on other sites
It seems to be a problem with the case of the URL.

Right. That one worked with me. I already have the files from Dave and here are some observations: CONFIG defines are missing in the header files. Also CVRCON (voltage reference) definition is missing for 18f25j11 (maybe for others). Anyway, these are details and I am very thankful for the files! :)

Share this post


Link to post
Share on other sites

Thank you for the new part definitions! I'm using the PIC18F24J11 in my product design, and I was able to get the support working with BoostC (using MPLAB IDE) (6.97 beta 2) and everything was working great until I tried to use the PPS port remapping feature.

 

I'm using the 2nd EUSART on pins RB3 (RX) and RB2 (TX). The transmitter works, but I can't get the receiver to operate. BoostC appears to be making the correct assembler output to do the port locking function. I've tried both C and inline asm (they produce essentially the same output anyway) to set up the PPS module and am now totally stumped. Many dozens of PIC designs under my belt, I feel completely stumped by this one.

 

If anyone has any ideas it would be great. It's the very last peripheral I need to get going before I can finish this thing....

 

 

 

Thanks!

 

Andrew

Share this post


Link to post
Share on other sites

New hot off the press tdf and header files can be found here:

http://www.sourceboost.com/CommonDownload/..._04-12-2009.zip.

 

It now includes the following devices:

PIC18F13K22, PIC18F14K22, PIC18F2458, PIC18F24J11, PIC18F24J50, PIC18F2553, PIC18F25J11, PIC18F25J50, PIC18F2682, PIC18F26J11, PIC18F26J50, PIC18F4458, PIC18F44J11, PIC18F44J50, PIC18F4553, PIC18F45J11, PIC18F45J50, PIC18F4682, PIC18F46J11, PIC18F46J50, PIC18F6393, PIC18F63J11, PIC18F6493, PIC18F64J11, PIC18F65J11, PIC18F6628, PIC18F66J55, PIC18F66J90, PIC18F66J93, PIC18F6723, PIC18F67J90, PIC18F67J93, PIC18F8393, PIC18F83J11, PIC18F83J90, PIC18F8493, PIC18F8628, PIC18F86J90, PIC18F86J93, PIC18F8723, PIC18F87J90, PIC18F87J93, PIC18L14K50, PIC18LF13K22, PIC18LF13K50, PIC18LF14K22, PIC18LF14K50, PIC18LF24J11, PIC18LF24J50, PIC18LF25J11, PIC18LF25J50, PIC18LF26J11, PIC18LF26J50, PIC18LF44J11, PIC18LF44J50, PIC18LF45J11, PIC18LF45J50, PIC18LF46J11, PIC18LF46J50

 

Regards

Dave

Share this post


Link to post
Share on other sites
Thank you for the new part definitions! I'm using the PIC18F24J11 in my product design, and I was able to get the support working with BoostC (using MPLAB IDE) (6.97 beta 2) and everything was working great until I tried to use the PPS port remapping feature.

 

I'm using the 2nd EUSART on pins RB3 (RX) and RB2 (TX). The transmitter works, but I can't get the receiver to operate. BoostC appears to be making the correct assembler output to do the port locking function. I've tried both C and inline asm (they produce essentially the same output anyway) to set up the PPS module and am now totally stumped. Many dozens of PIC designs under my belt, I feel completely stumped by this one.

 

If anyone has any ideas it would be great. It's the very last peripheral I need to get going before I can finish this thing....

 

 

 

Thanks!

 

Andrew

 

Check pin directions for selected RPx. I'm using 25j11 with two usarts and both are working fine. Here is relevant piece from my source (RB3=RX, RB2=TX):

portb = 0xff; trisb = 0xf9;
asm {
MOVLB 0x0E
MOVLW 0x55
MOVWF _eecon2, 0
MOVLW 0xAA
MOVWF _eecon2, 0
BCF _ppscon, IOLOCK, 1

MOVLW 6
MOVWF _rpinr16, 1
MOVLW 5
MOVWF _rpor5, 1

MOVLW 0x55
MOVWF _eecon2, 0
MOVLW 0xAA
MOVWF _eecon2, 0
BSF _ppscon, IOLOCK, 1
}

Share this post


Link to post
Share on other sites
New hot off the press tdf and header files can be found here:

http://www.sourceboost.com/CommonDownload/..._04-12-2009.zip.

 

Dave, I mentioned earlier - missing CVRCON definition for some devices. I found that it was an error in Microchip header files and it is now in the errata (found it for 18f25j11). Is it possible for such additions to get it to your definitions? And still missing configuration defs, as they are no more at locations near 0x300000, but at end of program flash... Maybe they are missing in Microchip header files too.

Share this post


Link to post
Share on other sites
New hot off the press tdf and header files can be found here:

http://www.sourceboost.com/CommonDownload/..._04-12-2009.zip.

 

Dave, I mentioned earlier - missing CVRCON definition for some devices. I found that it was an error in Microchip header files and it is now in the errata (found it for 18f25j11). Is it possible for such additions to get it to your definitions? And still missing configuration defs, as they are no more at locations near 0x300000, but at end of program flash... Maybe they are missing in Microchip header files too.

Microchip supplied data is the primary source of data for our header and TDF files, so if the error is in there we will reproduce the same error unless we notice that its wrong or missing which considering the amount of data is less likely.

 

On the configuration front we are adopting a new style (as per Microchips new configuration style):

 

#pragma CONFIG WDT = ON

 

This work is nearly complete, so should be included in the next release.

 

Regards

Dave

Share this post


Link to post
Share on other sites

Your content will need to be approved by a moderator

Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×