Dear Jayasooriah,
The "T" command is disabled when CRP is enabled.
Though the "G tEsT A" or "G tEsT T" commands were mentioned in the
earlier revisions of the User Manual's we realized that they do not
help the application in any way. Hence we skipped their descriptions
in the later revisions. These commands were solely meant for Philips
testing facilities.
The way the bootloader has been implemented so far will lead a
customer using either "T" or "G tEsT" command to a dead-end. Having
commands designed for in-house use only, together with reasons
ranging from a command not being fully functional (T command lacking
synchronization capabilities in different versions of the
bootloader) all the way to not having a useful code at all ("G
tEsT"), it becomes obvious why the "T" and "G tEsT" commands are not
part of the latest releases of the LPC2000 documentation.
We hope these details will help you and all other LPC2000 users in
their current work and future designs with these microcontrollers.
Regards,
Philips Apps Team
--- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@y...>
wrote:
>
> Dear philips_apps,
>
> I am very pleased that you have finally chosen to repsond to two of
> the three core issues I raised in this forum.
>
> I am anxiously awaiting confirmation of third issue relating to CSI
> vulnerability.
>
> Arising from explanation of T and 'tEsT' arguments, please clarify:
>
> 1/ if the T command disabled when CEP is enabled;
>
> 2/ if it is corect to say that what happpens to the boot sector
code
> is indetermine should any user enter "G tEsT A" or "G tEsT T"; and
>
> 3/ if you knew about these when you posted the "CRP Update"
message.
>
> Thank you.
>
> Jaya
>
> --- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@y...>
wrote:
> >
> > Hello all LPC2000 participants,
> >
> > Here are some answers to the T and G command related questions
that
> > have been asked on this forum recently.
> >
> > T command
> > =========Message
Re: T and G commands
2006-01-12 by philips_apps
Attachments
- No local attachments were found for this message.