Hello Pascal,
I have being able to succesfully flash our application onto 56F8356 controller board using the FLASH PROGRAMMER. After programming the application I have also verified the flash.
I recieve "SUCCESS" for both programming & verifying.
Now I want to know how to use the "TARGET BOARD" without USBTAP after flashing the application? It is not mentioned in the "Flash programmers User Manual".
Right now what I am doing is:
1) Programming the application
2) Verifying the applciation.
3) Removing the USBTAB
4) Reset the controller (Power ON & OFF) & check whether the application is working or not.
Is the above procedure correct? My application is not running on the TARGET after RESET.
Can you please guide me how to use the TARGET BOARD after FLASH PROGRAMMING the S-Record File.
Thank you,
Kanthi Uppala
Solved! Go to Solution.
Hello Moderators,
The problem was with the hardware. The "ExtBoot" pin should be grounded, it was connected to 3.3V. Hence there was no internal boot happening.
Ooops!!!!! It was my fault, sorry for the trouble.
Have a nice day.
Hello Moderators,
My Vector Base Address is proper: the below is the snapshot of linker file:
.p_Interruptsboot (RWX) : ORIGIN = 0x020000, LENGTH = 0x0004
.p_Interrupts (RWX) : ORIGIN = 0x000000, LENGTH = 0xA4
.p_Code (RWX) : ORIGIN = 0x0000A4, LENGTH = 0x01FF5C
ITCN.VBA = 0x0000
I am also giving the OMR & SIM_CONTROL Configuration used by me, please guide if any of the following is wrong:
OMR = 0x8000
SIM_CONTROL = 0x0000
SIM_PCE = 0xFFFF
SIM_CLKOSR = 0x0000
If the vector table is not functioning properly how come the other interrupts are working with USB TAP? Can you please answer this question?
Do I need to change any of the registers which I mentioned above?? Please take this request with high priority & help me in solving this issue.
My answer to the question is that no where in your previous message did you state the other interrupts were working. That's a new bit of information that I didn't have. Your reset vector is either configured wrong, or your initialization code is wrong. The program works when the debugger is present because the debugger does some hardware set up that your program is not doing. Check the initialization code you are using against that of the initialization code in a project made by the CodeWarrior wizard.
---Tom
Hello Moderators,
The problem was with the hardware. The "ExtBoot" pin should be grounded, it was connected to 3.3V. Hence there was no internal boot happening.
Ooops!!!!! It was my fault, sorry for the trouble.
Have a nice day.
Not a problem. We appreciate you reporting back what was the cause of your trouble. Perhaps it will help someone in the future, which is why I'm flagging your response as a solution. Good luck with your project.
---Tom