initialiazation of arm

only one problem is, to make it working i have to touch one of my Oscilloscope probe to crystal of controller

I think it's obvious that it's a hardware problem. Hence, no amount of testing in Keil simulator or Proteus will help solve it. The code has nothing to do with it.
Fix your crystal oscillator or get somebody to fix it.

only one problem is, to make it working i have to touch one of my Oscilloscope probe to crystal of controller

I think it's obvious that it's a hardware problem. Hence, no amount of testing in Keil simulator or Proteus will help solve it. The code has nothing to do with it.
Fix your crystal oscillator or get somebody to fix it.

You may have a damaged crystal. Or wrong type of crystal. Or wrong burden capacitors. Or maybe badly routed traces for the crystal.

But as noted, you have to separate hardware and software errors.

Hi Mike Kleshov,

Thanks for immediate reply for my post.
As you suggested i tested my hardware.The crystal cap across crystal are of value of 20P
And one 1 M Ohm resistor between two leads of crystal.
The issue is i have one code written by old programmer written in Code Warrior witch is
based on OS ucos and it runs successfully.
So not able to solve this problem.
There is one 8mb External ram IS61LV51216 connected on board. The address given on development board are

SRAM-Addr: 0x80000000--0x8007FFFF(Bank0) FPGA-Addr: 0x81000000--0x8100003F(Bank1) FLASH-Addr: 0x82000000--0x820FFFFF(Bank2) LCD-Addr: 0x83000000--0x830FFFFF(Bank3)

Is there is any relation of this peripheral?
But as given in my program i already using on chip Flash & RAM.And all the pins going to select the other chip are disabled.
Please help me to solve this problem.
Thank in advance,

Girish.

Hi Per A Westermark,

Thanks for immediate reply for my post.
As you suggested i tested my hardware.The crystal cap across crystal are of value of 20P
And one 1 M Ohm resistor between two leads of crystal.
The issue is i have one code written by old programmer written in Code Warrior witch is
based on OS ucos and it runs successfully.
So not able to solve this problem.
There is one 8mb External ram IS61LV51216 connected on board. The address given on development board are

SRAM-Addr: 0x80000000--0x8007FFFF(Bank0) FPGA-Addr: 0x81000000--0x8100003F(Bank1) FLASH-Addr: 0x82000000--0x820FFFFF(Bank2) LCD-Addr: 0x83000000--0x830FFFFF(Bank3)

Is there is any relation of this peripheral?
But as given in my program i already using on chip Flash & RAM.And all the pins going to select the other chip are disabled.
Please help me to solve this problem.
Thank in advance,

Girish.

If there is bad routing of the signals (the signals needs to be very short and ground plane design is also important), or the component values of crystal or burden capacitors are marginal, then you can get into trouble during the power-up sequence, i.e. the timing when you power up an external RAM in relation to when you power up the crystal oscillator can make a difference.

How is your layout and component values in relation to reference designs?

hi,
Thanks again,

As explained earlier the crystal of 11.0592 Mhz. Capacitor across crystal are of 20PF.
Resistor between two leads of crystal is of 1 M ohm.Power of 3.3v.
Port2 pin P2.26,P2.27 (Boot0 & Boot1) tied to Vcc(3.3V),V3 = 3.3 V,
Port0 Pin14 P0.14 to 3.3V
With Proper grounding and power traces as this board is of commercial product.

Is initialization routine is ok? any need to modify,any correction ?
Please reply ,
Thanks
Girish.

hi,
I also modified initialization of PLL of lpc2214 as following way till i got same result.

         void init(void)
         {
                // Initial PLL & VPB Clock For ET-ARM7 STAMP LPC2119
                // Start of Initial PLL for Generate Processor Clock
                // PLL Configuration Setup
                // X-TAL =      11.0592
                // M(Multiply) = 3                3
                // P(Divide) = 2                  2
                // Processor Clock(cclk) = M x OSC
                //                       =      3*11.0592
                //                       =      33.1776
                // FCCO = cclk x 2 x P
                //      = 132.7104
                // VPB Clock(pclk) = 16.5888
                // Start of Initial PLL for Generate Processor Clock
                PLLCFG &= 0xE0;    // Reset MSEL0:4
                PLLCFG |= 0x02;    // MSEL(PLL Multiply) = 3
                PLLCFG &= 0x9F;    // Reset PSEL0:1
                PLLCFG |= 0x20;    // PSEL(PLL Devide) = 2
                PLLCON &= 0xFC;    // Reset PLLC,PLLE
                PLLCON |= 0x01;    // PLLE = 1 = Enable PLL

                PLLFEED = 0xAA;    // Start Update PLL Config
                PLLFEED = 0x55;
                while (!(PLLSTAT & 0x00000400));  // Wait PLL Lock bit
                PLLCON |= 0x02;    // PLLC = 1 (Connect PLL Clock)
                PLLFEED = 0xAA;     // Start Update PLL Config
                PLLFEED = 0x55;
                VPBDIV &= 0xFC;    // Reset VPBDIV
                VPBDIV |= 0x01;    // VPB Clock(pclk) = cclk / 1
                // End of Initial PLL for Generate Processor Clock

                // Start of Initial MAM Function
                MAMCR = 0x00;     // Disable MAM Function
                MAMTIM = 0x03;     // MAM Timing = 3 Cycle of cclk
                MAMCR = 0x02;     // Enable MAM = Full Function
                // End of Initial MAM Function
                // Start of Main Function Here
         }

Please help,
Girish

I haven't looked into the individual steps you use when setting up the PLL, but the user manual clearly describes the requried steps. And it's important that the PLL constants also are correctly selected.

But back to the oscillator - note that the frequency is not the only parameter for a crystal.

hi,

As you suggested i tested crystal.The waveform and voltage across crystal are according to specs.
The PLL setting is done as given in user manual.which is also written in comment in above code.
so is there is any issue of mode of arm like user,Data Abort,udef,IRq,supervisory etc
& if so it is how to sort out this issue?
Thanks
Girish

You tested the crystal? You have equpiment to measure, and characterize, a crystal?

What results did you get?

What inductances did you measure?
What static capacitance?
What motional capacitance?
What load capacitance?
What drive level?
What equivalent series resistance?
What operating mode - fundamental or third overtone?
What cut?
What temperature range?
...

A crystal really is not just a magic device with a stamped frequency on the case. With wrong type of crystal and/or wrong burden capacitors in relation to processor, you can get into lots of troubles with oscillators that never starts, or starts sometimes, who only start within specific temperature ranges or depending on of voltage and noise levels etc.

So the startup code should match the recommended code from the processor documentation, but the capacitors, trace layout and crystal should also match the recommendations. And different processors are more or less sensitive to variations. Some processors can handle almost everything, while other processors have very narrow windows where the oscillator will work well - or at all.

Dear Sir,

As early stated i didn't went so deeply for testing crystal.
I checked voltage across crystal and waveform of crystal.It was OK.
If Agreed the crystal is faulty then the issue is if i program the hex file of old programmer in same IC it works successfully.
Only if i program the same ic with hex file of my program then i have to touch the probe of oscilloscope to one of crystal pin then it starts working.
How i can convinced to my senior on this issue?

I also grounded body of crystal.
will you please help for sorting out this,

Thanks in advance,

Girish

I checked voltage across crystal and waveform of crystal.It was OK.
yes, you said that already, to have "checked voltage across crystal" you have touched it with a scope probe

With Proper grounding and power traces as this board is of commercial product.
that is no guarantee there are many shoddy "commercial products" how long are the traces to xtal and burden caps? how long traces to and what are the Vdd decoupling caps?

Erik

Another thing - does your processor always make use of an external oscillator, or does it boot with an internal RC oscillator like 23xx does? In that case - what code do you have that turns on the external oscillator and waits for it to stabilize before it may be connected for use by the core?

You post code for the PLL (seems to be different PLL settings for the two codes) but the PLL needs input. Is the oscillator spun up correcly before connected?

Just show him/her!

Get him/her to help you: he/she knows you, knows your project, can see your hardware, can probe it him/herself, can see your software, etc, etc - nobody on a forum has any of those advantages!

Do you mean that you are creating this board to be used as a commercial product?

Or have you bought the board as a ready-made commercial product?

If you've bought the board as a ready-made commercial product, why are you not seeking support from your supplier?

Hi,

Thanks for your kind Co-operation,
Yes i posted two codes .First is sample code of led blinking. Other is i made as given in user manual.
My senior is not embedded professional is Analog Expert. So i can not ask my queries to him.
Other thing is the board which i am working is old board and is customized from other party.
So i am only having the circuit diagram and a sample code. Which is based on ucosII and no other details. So i cant get more help from my resources.
On power up initiate the PLL frequency which is on 11 Mhz. is anything else required ?

Thanks & Regards

Girish.