This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CKFA on 28035 through eCAN problem

Hi All :

I am now using CKFA example code as a serial transmit boot loader with eCAN

I can upload my bin file to  MCU in the memory address I assigned ,and when I use memory browser to check the data in MCU ,it seems to be OK cause the data in start address and in stop address  are the same as the word data in the  Bin file I upload,

After  I finished the upload sequence and do flash program through CKFA , the MCU should go to the address I assigned and start run the Appcode I upload,  but in my case ,It will return to the start address of CKFA, and since I have upload my bin file,which make CKFA set a parameter called "u16_Calibration_Status" to 0x11    ,CKFA will go to the start address of AppCode ,but as before ,It will return to CKFA itself ,so it  become a loop and the MCU never go to my AppCode

I tried 2 cases with the same linker file :

A. file size is 3246 bytes  

B. file size is 39,954 bytes

Case A is successed and Case B  failed  with the situation I wrote above, so I don't know what will make the difference?

here are some of my configuration i CKFA and the linker file of both CKFA and my own project

in CKFA.C :

#define FLASH_RANGE 0x8000 // FLASHH
#define DEST_ADDR 0x3E8000

#define BLOCK_SIZE FLASH_RANGE+1L
#define RAM_BUFFER_SIZE 2048
#define Device_cal (void (*)(void))0x3D7C80
#define AppCode (void (*)(void))0x3E8000

#define CHECKSUM_EXPECTED 0xCEE7
#define CHECKSUM_FASH (0xFFFF*FLASH_RANGE)

Thanks for your helps!

 7558.attachment.7z