This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: linking a program for download to at91sam7x-resident redboot


> well, this little hello-program I want to launch from redboot is just
> my example to climb the learning curve of how it has to be done. The
> code-part of the program I ultimately want to launch from redboot is
> too big to go into RAM. So it has to run from flash.  And I need redboot to
> have a loader on board, so the application can be updated if required.
> Unfortunately I can not use the bootloader that comes with all
> AT91SAM7x-based systems, because it (SAM_BA) supports USB and the
> serial debug-I/F only and both of them are not implemented (not accesible)
on
> the board I am using here - hence (a minimum) redboot was identified as the
> solution of the problem.
> 
> The FIS in my case only has to take a small script that launches my
> big-app if UART0 or UART1 does not receive a ctrl-c character during a
timeout
> interval of a few seconds. In such a case it would abort the script and
> one would be able to use redboot for downloading a program (direct load
> into flash).  Any comments on these ideas?

Hi Robert,

I don't know the AT91SAM7 stuff too well, but I guess as was pointed out,
there's a CDL option to change the startup location of a flash app just for
the AT91s.  From the perspective of what you're trying to do with Redboot and
the timeouts, there shouldn't be any problem.  I don't know the specifics of
that particular AT91 option, and how it behaves, but fundamentally, there's
nothing wrong with what you're trying to do.

--Chris

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]