This is the mail archive of the ecos-discuss@sources.redhat.com 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]

Re: e7t ROM startup



[remember to CC the list!]

>>>>> "Simon" == Simon  <simoncc@ms46.url.com.tw> writes:

Simon> right, JTAG is neccesary.  I have two plateforms with the same
Simon> chip.  one is e7t and the other is SMC7004ABR.  I have put
Simon> redboot into SMC3004ABR.  such that I got two network
Simon> interfaces and one super I/O interface and enough memories for
Simon> my work.  it's quite good.  if not having JTAG tool, I am
Simon> trying to find out a solution to upload and replace with
Simon> redboot.

OK, no JTAG. I see two options then:

 o Add flash support to RedBoot and tell it to leave the first 64kB
   alone. Then use a RedBoot script to load a flash image to RAM and
   start it.  This requires that there's enough space in flash for
   both the Boot Monitor, RedBoot, and the app.

   You also risk bricking the board since you have no means of
   reprogramming the flash if you accidently trash the Boot Monitor.

 o Get the modules stuff working.

I'd obviously go for the latter, being less risky, but I can't really
help you with the problem (without you getting a contract - and it
would probably be much too expensive). 

We don't support general ROM startup on the E7T (or the AEB) because
it's such a tedious process to get it working. I suggest you either
ask ARM for guidance or find another development platform if you need
the ROM startup.

Jesper


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