CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to support@ccsinfo.com

18f4553 usb

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
nicotec



Joined: 07 Nov 2008
Posts: 60

View user's profile Send private message

18f4553 usb
PostPosted: Tue Dec 21, 2010 5:26 am     Reply with quote

Hi everyone,
can anyone help me to understand if there are errors/missing in my code (v4.114) considering that I'm using a 20MHz quartz; I need just to start to understand if sequence to use hardware usb built-in sequence is correct to obtain enumeration since my simulation with proteus not work I suppose there is an error.
Thanks in advance and regards

Code:

#include <18F4553.h>
#device ICD=TRUE

#FUSES NOWDT                    //No Watch Dog Timer
#FUSES WDT128                   //Watch Dog Timer uses 1:128 Postscale
#FUSES PLL5                    //Divide By 5
#FUSES CPUDIV4                  //System Clock by 4
#FUSES USBDIV                   //USB clock source comes from PLL divide by 2
#FUSES HSPLL                    //High Speed Crystal/Resonator with PLL enabled
#FUSES FCMEN                    //Fail-safe clock monitor enabled
#FUSES IESO                     //Internal External Switch Over mode enabled
#FUSES NOPUT                    //No Power Up Timer
#FUSES NOBROWNOUT               //No brownout reset
#FUSES BORV27                   //Brownout reset at 2.7V
#FUSES VREGEN                   //USB voltage regulator enabled
#FUSES NOPBADEN                 //PORTB pins are configured as digital I/O on RESET
#FUSES LPT1OSC                  //Timer1 configured for low-power operation
#FUSES MCLR                     //Master Clear pin enabled
#FUSES STVREN                   //Stack full/underflow will cause reset
#FUSES NOLVP                    //No low voltage prgming, B3(PIC16) or B5(PIC18) used for I/O
#FUSES ICPRT                    //ICPRT enabled
#FUSES NOXINST                  //Extended set extension and Indexed Addressing mode disabled (Legacy mode)
#FUSES DEBUG                    //Debug mode for use with ICD
#FUSES NOPROTECT                //Code not protected from reading
#FUSES NOCPB                    //No Boot Block code protection
#FUSES NOCPD                    //No EE protection
#FUSES NOWRT                    //Program memory not write protected
#FUSES NOWRTC                   //configuration not registers write protected
#FUSES NOWRTB                   //Boot block not write protected
#FUSES NOWRTD                   //Data EEPROM not write protected
#FUSES NOEBTR                   //Memory not protected from table reads
#FUSES NOEBTRB                  //Boot block not protected from table reads

#use delay(crystal=20000000,  clock=4000000)
#use rs232(UART1, baud=9600, parity=N, bits=8, stop=1)
#include <pic18_usb.h>
#include <usb_desc_hid.h>
#include <usb.c>

//#int_usb


void main()
{
   setup_timer_3(T3_DISABLED|T3_DIV_BY_1);
   //printf("\r\nUSBN: 0x%X", usbn_get_version());
   printf("Starting USB...");
   usb_init();
   usb_attach();
   if(usb_enumerated())
   {
      printf("Enumerated");
   }
   
   while(true)
   {
      output_high(PIN_B0);
      delay_ms(1);
      output_low(PIN_B0);
      delay_ms(1);
   }
}
Douglas Kennedy



Joined: 07 Sep 2003
Posts: 755
Location: Florida

View user's profile Send private message AIM Address

PostPosted: Tue Dec 21, 2010 7:39 am     Reply with quote

This board is about hardware and the CCS compiler. Proteus is neither of these since it is a simulator and brings with its own host of potential issues.
The way forward is to actually build a circuit. With the circuit you can tell which errors reported by Proteus are real or just free features of Proteus.
nicotec



Joined: 07 Nov 2008
Posts: 60

View user's profile Send private message

re: pic18f4553 usb
PostPosted: Tue Dec 21, 2010 8:11 am     Reply with quote

Sorry for misunderstanding but I don't need any help on Proteus. Only to know if the concept of code is correct or there are missing a calling procedure for the first initialization of usb module.
Thanks in advance and regards.
Ttelmah



Joined: 11 Mar 2010
Posts: 19328

View user's profile Send private message

PostPosted: Tue Dec 21, 2010 9:23 am     Reply with quote

You have two 'disagreeing' sets of clock settings.
The fuses say:

HSPLL - CPU clock will come from the PLL (PLL is _always_ 'enabled').
PLL5 - Take external crystal/5 to feed PLL.
CPUDIV4 - Divide PLL/2 by 6 (look at the data sheet to see why....), to feed CPU.

So with the fuses, the CPU will be running at 8MHz, but your clock setup line says to run it at 4MHz (which requires HS, not HSPLL).

There can be problems trying to run USB, with a CPU clock as low as 4MHz....

Best Wishes
nicotec



Joined: 07 Nov 2008
Posts: 60

View user's profile Send private message

18f4553 usb
PostPosted: Tue Dec 21, 2010 1:35 pm     Reply with quote

Sorry, since I need to use usb, from data sheet I need to set MCU frequency to 24MHz so could You confirm that it would be 24000000 and not 4000000 with fuse needed to be changed accordingly?

Thanks in advance and Regards
Ttelmah



Joined: 11 Mar 2010
Posts: 19328

View user's profile Send private message

PostPosted: Tue Dec 21, 2010 3:59 pm     Reply with quote

I think you are misunderstanding the oscillator.

The oscillator on the 53, is the same layout as on the 4550 (this is why the 4553 data sheet refers you to the 4550 data sheet, and describes itself as 'supplementary' to this).
For full speed USB, the only requirement, is that the PLL, is generating 96Mhz. You can run the CPU at any one of several dozen frequencies, choosing divisions of the external clock, from the PLL, or even the internal RC oscillator.
To get to 96MHz, given the PLL is *24, you need a 'feed' at 4MHz to this. Since available dividers are 1,2,3,4,5,6,10 & 12, you are restricted to a crystal at 4,8,12,16,10,24 MHz, or an external oscillator at the same frequencies or 40/48 MHz.

So starting from one of these frequencies, you then select the PLL divider needed to give 4MHz. For the 20MHz quartz, this implies PLL5. Then you can select the CPU to feed from the USB PLL, the crystal, or the internal oscillator HSPLL, HS, or INTRC.
If using HS, or HSPLL, the incoming frequency (96MHz for the later, or the crystal frequency for the former), can be divided. (CPUDIV1 to CPUDIV4). However the actual divisions are 1,2,3,4, if using 'HS', or 2,3,4 & 6, if using HSPLL. So with the 20MHz clock, you could run:
20,10,6.66,5,48,32,24,16 MHz, or the frequencies from the internal RC oscillator. CPUDIV4, gives division by 6, if using the PLL....

So straight away, 4MHz, is not one of the options with this crystal. However there are also timing constraints on USB (how fast it must respond), and the lowest rates, can sometimes cause problems, especially if your code is doing much else. Personally, I'd probably select a slightly slower crystal (8MHz), which will reduce the oscillator consumption a little, and run the CPU at this frequency, which is adequate if you are not wanting to do too much.

Now your reference to 24MHz, makes me think that you are possibly looking at the oscillator on the J50 chips, and wanting to run the USB at low speed, rather than full speed (which requires this speed).

Best Wishes
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group