This is the mail archive of the ecos-bugs@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]

[Issue 1000959] New: Redboot cli accepts no input


Please do not reply to this email. Use the web interface provided at:
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000959

           Summary: Redboot cli accepts no input
           Product: eCos
           Version: 3.0
          Platform: aeb (ARM evaluation board (AEB-1))
        OS/Version: ARM
            Status: UNCONFIRMED
          Severity: normal
          Priority: normal
         Component: RedBoot
        AssignedTo: gary@mlbassoc.com
        ReportedBy: markthetyke@4dv.net
         QAContact: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


When I load redboot it shows the startup banner and prompt but when I type in
minicom nothing is echoed and nothing is executed. It just hangs at the command
prompt until I reset the micro back to the version of RedBoot I have in ROM.
I have another version of RedBoot that came with the board and that works fine
but it is from an earlier version of ECOS. I am using version 3 and this is a
GPS4020 board, which is an ARM7TDMI micro. I need to reload RedBoot as I am
Increasing the amount of memory on the board. I can compile and run a C
application using my current configuration of ECOS, and this responds to
keyboard input so it is not a hardware issue, I can also go back to the version
of RedBoot I have in ROM and this works fine. The RAM version of RedBoot that
came with the board also works fine when loaded via the serial interface at
bootup. So this tells me it is something to do with the RedBoot configuration,
this wants to compile an ELF binary even though I am using the EABI tool chain.
I have been running a GPS application on this board for several months with no
problems from ECOS or RedBoot so apart for this issue it works great.

I am sure this is a configuration problem but I have tried adding in the TTY
and Hardware serial packages with no luck. If I select the termios package I
get an unresolvable conflict.

-- 
Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.


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