NXP LPC17xx USB Secondary Bootloader

The boot loader simply burns contents of the target .bin file into the code FLASH of your LPC17xx parts, starting from 0x2000.

What is the size of the .bin file?
Does the size fit to your LPC17xx code FLASH, counting in 0x2000 offset?

Tsuneo

The boot loader simply burns contents of the target .bin file into the code FLASH of your LPC17xx parts, starting from 0x2000.

What is the size of the .bin file?
Does the size fit to your LPC17xx code FLASH, counting in 0x2000 offset?

Tsuneo

Yes, of course. The bin file size if 84.6 KB, and chip has 504KB free.

I must say that I can add local variables, I can add as much as the code I want. Only global variables cause the problem. Therefore I think it is not related to the file size.

Something is very weird here.

Wait, now I will try to write a hello world program which fails, than we will know for sure what is it about...

Working code:

int dummy2;
int *dummy3;
char Dummy_check[500];

#include <LPC17xx.h>
#include "system_LPC17xx.c"

int main ()
{ // Init clock 96Mhz, 12 Mhz crystal SystemInit(); SystemCoreClockUpdate();

//Init output pin for blinking led LPC_PINCON->PINSEL7&=~(3<<18); LPC_GPIO3->FIODIR=1<<25;

while(1) { for (long i=0;i<2500000;i++); //delay for a fraction of a second LPC_GPIO3->FIOSET=1<<25; //LED ON for (long i=0;i<2500000;i++); //delay for a fraction of a second LPC_GPIO3->FIOCLR=1<<25; //LED OFF };
}

Not working code:

//int dummy2;
int *dummy3;
char Dummy_check[500];

#include <LPC17xx.h>
#include "system_LPC17xx.c"

int main ()
{ // Init clock 96Mhz, 12 Mhz crystal SystemInit(); SystemCoreClockUpdate();

//Init output pin for blinking led LPC_PINCON->PINSEL7&=~(3<<18); LPC_GPIO3->FIODIR=1<<25;

while(1) { for (long i=0;i<2500000;i++); //delay for a fraction of a second LPC_GPIO3->FIOSET=1<<25; //LED ON for (long i=0;i<2500000;i++); //delay for a fraction of a second LPC_GPIO3->FIOCLR=1<<25; //LED OFF };
}

If I comment the dummy3, the code also don't work. I can change the size of a field Dummy_check.

In this case the problem occurs when removing a variable. Sometimes the problem occurs then adding them.

Any ideas?

Might you have an issue with how you align the stack?

By the way - it does not hurt if you look up the posting instructions for source code. It's described directly above the input message box.

It is probably something with stack.
I have set on both: bootloader, and user aplication the adress for memory: 0x10000000, and size 0x8000.

It was like that by default.

If I select IRAM2 with a start at 0x2007C000 for user application, then it works normally.
I know that IRAM2 is divided into two sections, so I rather would not use this area.

My apologizes for the unformated source code.
My first post here, lesson learned.