Jam Iqbal wrote:

Since you have send me an e-mail with the same text I will answer just
in the forum so maybe others can jump in and add remarks.

> I am using STR710 Z2T6.
> The IDE including Compiler and linker, which I
> am using is IDEaliST.

Which versions of the GNU tools (binutils/gcc) are you using?

> Whereas the application is for traffic control. It
> was working fine. Code was written by some other guy. When I tried to
> download the same working code using Bluetooth, It stucked. I guess, it
> might be because of I used wrong rom file (and the new code overwritten
> bootloader).

Difficult to help without locking into the bootloader source-code.

>  Then I have to make a JTAG interface (Wigggler compatible board by
> Anglia). Now after fully erasing the FLASH, when I download the original
> s19/bin file of bootloader in flash of STR710, it shows unpredictable
> behaviour.

Show the source-code of the bootloader. Are the flash-write routines
executed in RAM? Is remapping handled correctly in the user-application
(location of exception-vectors, remapping bits)?

> After programming FLASH, when I restart the board, after a
> couple of minutes (2-3 min), the status LEDs on the board
> (GSM,Bluetooth, Heratbeat etc) becomes ON and then the board is stucked.

Are these LEDs connected the the STR7 or to the GSM or bluetooth module?
A lot of GSM and Bluetooth modules offer connections for status-LEDs, so
these LEDs will not indicate problems with the STR7 firmware and just
show the status of the modules.

> Even resetting the board, does not turn these status LEDs OFF. Please
> remember I have NOT yet downloaded code of my application into FLASH.
> This was result of just downloading bootloader in STR710.

So the flash-write routines have never been called during the test? Did
you monitor the stack-pointers while the bootloader is active?

Is there some kind of timeout in the bootloader-code so the bootloader
waits for incoming new code for some time and tries to start the
application if nothing has been received?

> I changed the
> board, but it did not help. Do not know what mistake, I am making. :(
> Because the on/off status LEDs of the board should have nothing to do
> with the bootloader.

The LEDs will only give some hints if they are connected directly to the
STR7. Please show the schematic of your board.

>   Just to clarify, setting of my Bootloader rom71x file are:
>
>   CODE (rx) : ORIGIN = 0x40000000, LENGTH = 0x00004000
>   DATA (rw) : ORIGIN = 0x20000000, LENGTH = 0x00003000
>
>  Any clue, what to check? Please do not hesitate to ask me if you need
> further clarification. I hope your couple of minutes would be helpful to
> sort out my stupid mistake. :)

It may be just a "stupid mistake" but it's very difficult to sort this
out without the source-code of the bootloader and more information on
the hardware. A minimal example with full source-code for an application
which should be uploaded through the bootloader will help too to see how
remapping is handled, maybe you can extract this from your "traffic
control" application.

Martin Thomas