>>Where do I set the destination device (UART1, UART2) for printf?
>>
>>I can't even find the source for stdio.h
>>    
>>
>
>
>Hi Tom,
>
>The stdio library will direct its output to a fuction call write()  (forget
>its prototype, but I believe it's explained in the library manual).  If you
>can find the source (I'm not sure if it included in the C30 package) you'll
>find that it will output to UART1.
>
>
>Best regards,
>
>WH Tan
>
>  
>

>2006/6/8, Tom Sefranek <tcsspam_OUTcmcorp.com>:
>  
>
>>No, after reading that there is NO peripheral support for the PIC24 series,
>>I switched my code for a pin identical dsPIC30F6011.
>>(Unfortunately it only has 6K of RAM.)
>>If I compile "my"  UART2  write(), I get errors about all kinds of
>>undeclared stuff.
>>If you are interested, tomorrow, I can send my source code, it's pretty
>>small.
>>
>>    
>>
>
>
>OK.  Can you try this:
>
>Create a new write.c file, and put the following into it.  Don't
>forget to add it to your project tree.
>
>
>
>
>
>#include <p30fxxxx.h>
>#include <stdio.h>
>
>#define        SPEN        0x8000u
>#define        TXEN        0x0400u
>#define        TRMT        0x0100u
>#define        TXBF        0x0200u
>#define        RCDA        0x0001u
>
>int write(int handle, void *buffer, unsigned int len)
>{
>        int i;
>        
>        switch (handle)
>        {
>        case 0:
>        case 1:
>        case 2:
>                if ((U2MODE & SPEN) == 0)
>                {
>                        U2BRG = 0;
>                        U2MODE |= SPEN;
>                }
>                if ((U2STA & TXEN) == 0)
>                {
>                        U2STA |= TXEN;
>                }
>                for (i = len; i; --i)
>                {
>                        while (U2STA & TXBF);
>                        U2TXREG = *(char*)buffer++;
>                }
>                break;
>        default:
>                break;
>        }
>        return(len);
>}
>
>
>
>
>
>
>Best regards,
>
>  
>

> >#include <p30fxxxx.h>
> >#include <stdio.h>
> >
> >#define        SPEN    0x8000u
> >#define        TXEN    0x0400u
> >#define        TRMT    0x0100u
> >#define        TXBF    0x0200u
> >#define        RCDA    0x0001u
> >
> >int write(int handle, void *buffer, unsigned int len)
> >{
> >       int i;
> >
> >       switch (handle)
> >       {
> >       case 0:
> >       case 1:
> >       case 2:
> >               if ((U2MODE & SPEN) == 0)
> >               {
> >                       U2BRG = 0;
> >                       U2MODE |= SPEN;
> >               }
> >               if ((U2STA & TXEN) == 0)
> >               {
> >                       U2STA |= TXEN;
> >               }
> >               for (i = len; i; --i)
> >               {
> >                       while (U2STA & TXBF);
> >                       U2TXREG = *(char*)buffer++;
> >               }
> >               break;
> >       default:
> >               break;
> >       }
> >       return(len);
> >}

> More fun with C30 for the PIC24s...
>
>
> I can not get the compiler to pay ANY attention to uart.h
>
> I added it to the MPLAB include path $(incdir) and even added it explicitly
> in the MPLAB includes folder as a file.
>
> If I invoke definitions unique to PIC 24 UART (Defined in uart.h) the
> compiler complains they are undefined.
>
>
> Source file line:
>        USART2_STA_Value = UART_INT_TX & UART_IrDA_POL_INV_ZERO &
> UART_SYNC_BREAK_DISABLED & UART_TX_ENABLE & UART_INT_RX_3_4_FUL &
> UART_ADR_DETECT_DIS & UART_RX_OVERRUN_CLEAR;
>
>
> Compiler results:
>
> Inits.c: In function `inits':
>
> Inits.c:140: error: `UART_IrDA_POL_INV_ZERO' undeclared (first use in this
> function)
>
> Inits.c:140: error: (Each undeclared identifier is reported only once
>
> Inits.c:140: error: for each function it appears in.)
>
> Inits.c:140: error: `UART_SYNC_BREAK_DISABLED' undeclared (first use in this
> function)
>
> Halting build on first failure as requested.
>
>
> Programming in C are good... with asprin.
>
> Tom
>
>  *
>  |  __O    Thomas C. Sefranek  RemoveMEWA1RHPTakeThisOuTARRL.NET
>  |_-\<,_   Amateur Radio Operator: WA1RHP
>  (*)/ (*)  Bicycle mobile on 145.41MHz PL74.4
>
> ARRL Instructor, Technical Specialist, VE Contact.
> hamradio.cmcorp.com/inventory/Inventory.html
> http://www.harvardrepeater.org

>Tom,
>
>Can you get printf working for PIC24's UART2?
>
>I just tested my Explorer 16 demo board (which has been sleeping for
>almost 2 month), and I seem to be able to output something.  If you're
>interested, please let me know.
>
>
>Best regards,
>
>  
>

>2006/8/21, Tom Sefranek wrote:
>
>  
>
>>I got it to compile, but I can't get the chip into debug with  MPLAB.
>>    
>>
>
>
>Tom,
>
>Do you mean debug in SIM30? My version didn't output to SIM too.
>
>Or do you mean ICD2?
>
>
>  
>

> 2006/8/21, Tom Sefranek wrote:
>
> > I posted the error text lat week.
>
>  Apparently I have missed that message.  Anyway I
> read it now in my
> gmail mailbox.  I love gmail... it's my PIC mail
> archive now and I
> never deleted a PICList message since I used it :)
>
> The device I'm working with is PIC24FJ128GA010 (the
> PIM on Exp16
> board, rev 0x3001 reported by ICD2).  The ICD2
> debugging seems to be
> working just fine. I can break and view the memory
> content etc.  From
> you description of the other message posted, sounds
> like you haven't
> used the _CONFIG macro to set the configuration
> settings. Just for
> your reference, I have the following in my C file
> contain the main()
> routine:
>
> // Setup configuration bits
> _CONFIG1(JTAGEN_OFF &        // JTAG Disabled
>        GCP_OFF &        // Code Protection Disabled
>        GWRP_OFF &        // Write Protection Disabled
>        COE_OFF &        // Clip-on Emulation Disabled
>        FWDTEN_OFF &        // Watchdog Timer Disabled
>        ICS_PGx2)        // ICD2 pins select: EMUC/EMUD share
> PGC2/PGD2
>
> _CONFIG2(FCKSM_CSDCMD &        // Clock switching and clock
> monitor: Only
> clock switching enabled
>        OSCIOFNC_ON &        // OSCO/RC15 function: RC15
>        POSCMOD_HS &        // Oscillator Selection: HS oscillator
>        FNOSC_PRI)        // Primary oscillator (XT, HS, EC)
>
> Your processor might be a bit different, but you can
> have a clue by
> looking into the processor header file, which you
> can find in your C30
> folder.
>
>
> Well I'm searching for the equivalent alphabet
> revision representation
> for PIC24FJ128GA010 . You know that is the most
> confuse issue that
> Microchip has ever made - ICD2 report something like
> rev 0x3001 while
> their errata sheet has a title something like rev
> A1, A2...etc.  Then
> sometime the short description of ICD2 report was
> missing from the
> errate sheet. Still undergo testing of my
> GetSiliconRevision()
> routine...
>
> I hope you can find a solution soon.
>
>
> Best wishes,
>
> --
> WH Tan

> 2006/8/21, John Chung wrote:
>
> >     I am trying to program the PIC24FJ128GA010  on
> > the Explorer 16. I still have a problem detecting
> the
> > MCU using my ICD2.
>
> Sounds like a defective board!?
>
> But a few questions for you:
>
> 1) Did the pre-programmed demo application work?
>

> Firmware version: 02.00.06.00
>
> and my MPLAB version is 7.41.
>
> And apart from connection check, you might want to
> confirm the power
> supply: both the reading reported in MPLAB and
> measured by a true DMM.
>
> In MPLAB IDE, I got:
>
> Target Vdd: 3.24V
> Target Vpp: 3.20V (I think becasue I was not
> performing any
> programming at the moment)

> 2006/8/21, John Chung wrote:
>
>
> > > 3) What type of connection you used for ICD?
> USB or
> > > COM?  Did ICD2
> > > detect other device or board?
> >
> >  ICD2 was using USB. BTW I did use the same ICD2
> to
> > detect my PIC16F873. No problem with that PIC.
> ICD2
> > did not detect any other device. the device Id
> return
> > from the PIC24 was 0. The power line were okay.
> Maybe
> > I need to do a continuity test btw the RJ-12 and
> the
> > chip itself......
>
> But did the OS got downloaded?  I check my version
> in the setting
> dialogue box, it says:
>
> MPLAB ICD2 Version: 07.40.00.18
> Firmware Type: 33F  ( Funny I'm working with PIC24)
> Firmware version: 02.00.06.00
>
> and my MPLAB version is 7.41.
>
> And apart from connection check, you might want to
> confirm the power
> supply: both the reading reported in MPLAB and
> measured by a true DMM.
>
> In MPLAB IDE, I got:
>
> Target Vdd: 3.24V
> Target Vpp: 3.20V (I think becasue I was not
> performing any
> programming at the moment)
> MPLAB ICD2 Vpp: 14.06V
>
>
> Measured by DMM:
>
> The Red colour +5V test 'ring' : 4.99V
> The Red coluor +3.3V test ring: 3.29V
>
> I also probe several capacitor on the PIM, from what
> I see here there
> are C7, C2, C3, C4, C8, C1.  All of them give 3.29V
> at one terminal,
> and close to 0V at another terminal.
>
> The only exceptions are C6 and C5: I haven't
> examined closely yet what
> are their purpose but they sound like part of the
> on-chip regulator,
> which give 2.5V.
>
>
> Best wishes,
>
> --
> WH Tan