[ECOS] running test cases

[ECOS] running test cases

[grahamlab]

Hello everyone

When I try to run gdb I am seeing the following

(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
0x08003b3a in ?? ()
(gdb) load
Loading section .rom_vectors, size 0x8 lma 0x68008000
Loading section .ARM.exidx, size 0x10 lma 0x68008008
Loading section .text, size 0x4330 lma 0x68008018
Ignoring packet error, continuing...

can anyone tell me what I am doing wrong

Graham
-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22873616.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Gary Thomas]

grahamlab wrote:
> Hello everyone
> 
> When I try to run gdb I am seeing the following
> 
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> 0x08003b3a in ?? ()
> (gdb) load
> Loading section .rom_vectors, size 0x8 lma 0x68008000
> Loading section .ARM.exidx, size 0x10 lma 0x68008008
> Loading section .text, size 0x4330 lma 0x68008018
> Ignoring packet error, continuing...
> 
> can anyone tell me what I am doing wrong

Pretty hard to say since we've no idea what platform you're using :-(

Most likely cause is trying to load code into RAM that RedBoot
(or GDB stubs) uses.

Provide some [real] details and we might be able to help.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Hello again
I am running Umbunto on a pc through  VM Virtual box and targetting the
STM3120E dev board.
I have successfuly built and downloaded RedBoot using St's demo flash
loader. I have verified that this is running by connecting hyperterminal to
the dev board and seeing the RedBoot gdb prompt.

I have then performed a default build of eCos for the dev board and then try
to run gdb from the command line in the virtual machine.

The command used to invoke gdb was 
arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0

at the gdb prompt I type 
set remotebaud 38400
target remote /dev/ttyS0
and get the output below

I have tried various builds with different baud rates.

Any help would be greatly appreciated

Graham


Gary Thomas wrote:
> 
> grahamlab wrote:
>> Hello everyone
>> 
>> When I try to run gdb I am seeing the following
>> 
>> (gdb) target remote /dev/ttyS0
>> Remote debugging using /dev/ttyS0
>> 0x08003b3a in ?? ()
>> (gdb) load
>> Loading section .rom_vectors, size 0x8 lma 0x68008000
>> Loading section .ARM.exidx, size 0x10 lma 0x68008008
>> Loading section .text, size 0x4330 lma 0x68008018
>> Ignoring packet error, continuing...
>> 
>> can anyone tell me what I am doing wrong
> 
> Pretty hard to say since we've no idea what platform you're using :-(
> 
> Most likely cause is trying to load code into RAM that RedBoot
> (or GDB stubs) uses.
> 
> Provide some [real] details and we might be able to help.
> 
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22880984.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

grahamlab wrote:
> Hello again
> I am running Umbunto on a pc through  VM Virtual box and targetting
> the STM3120E dev board.
> I have successfuly built and downloaded RedBoot using St's demo flash
> loader. I have verified that this is running by connecting
> hyperterminal to the dev board and seeing the RedBoot gdb prompt.
> 
> I have then performed a default build of eCos for the dev board and
> then try to run gdb from the command line in the virtual machine.
> 
> The command used to invoke gdb was 
> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> 
> at the gdb prompt I type 
> set remotebaud 38400
> target remote /dev/ttyS0
> and get the output below

As I could understand you run GDB on VirtualBox, because your host OS !=
Linux. What's about the serial port settings? Be sure that there is not
set any flow control for the serial port. Use 'mode' command on the host
side and 'stty' on the guest side to check it. Can you download the same
executable in the RAM using X/Y/Z modem? Any virtual port is a something
different from the real one. First, be sure that you can upload a few
tens kilobytes on the target via virtual serial port, and then you can
dance with GDB. So, try RedBoot's `load' command and the HyperTerm's
`send file' ability to check a communication with the real serial port.
Then you can use the guest's `minicom' program to check that the virtual
serial port works as expected too. If you'll get the result, then try
GDB on the guest again.


Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Hi everyone

I can see the redboot monitor in minicom running in my virtual box but I
still cannot get gdb working - I get the same results

What else can I try?

Graham


Sergei Gavrikov-4 wrote:
> 
> grahamlab wrote:
>> Hello again
>> I am running Umbunto on a pc through  VM Virtual box and targetting
>> the STM3120E dev board.
>> I have successfuly built and downloaded RedBoot using St's demo flash
>> loader. I have verified that this is running by connecting
>> hyperterminal to the dev board and seeing the RedBoot gdb prompt.
>> 
>> I have then performed a default build of eCos for the dev board and
>> then try to run gdb from the command line in the virtual machine.
>> 
>> The command used to invoke gdb was 
>> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> 
>> at the gdb prompt I type 
>> set remotebaud 38400
>> target remote /dev/ttyS0
>> and get the output below
> 
> As I could understand you run GDB on VirtualBox, because your host OS !=
> Linux. What's about the serial port settings? Be sure that there is not
> set any flow control for the serial port. Use 'mode' command on the host
> side and 'stty' on the guest side to check it. Can you download the same
> executable in the RAM using X/Y/Z modem? Any virtual port is a something
> different from the real one. First, be sure that you can upload a few
> tens kilobytes on the target via virtual serial port, and then you can
> dance with GDB. So, try RedBoot's `load' command and the HyperTerm's
> `send file' ability to check a communication with the real serial port.
> Then you can use the guest's `minicom' program to check that the virtual
> serial port works as expected too. If you'll get the result, then try
> GDB on the guest again.
> 
> 
> Sergei
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22885001.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Sat, Apr 04, 2009 at 09:11:06AM -0700, grahamlab wrote:
> 
> Hi everyone
> 
> I can see the redboot monitor in minicom running in my virtual box but I
> still cannot get gdb working - I get the same results
> 
> What else can I try?
> 
> Graham
 
To see the prompt is good news, but, that's not enough. You have to
answer on 2 questions: 1st) Can you upload a file with RedBoot using X/Y
modem protocol? and 2nd) Is RedBoot built with GDB support?

First, let's check a upload ability. I assume that your RedBoot supports
X/Y modem protocols.

Create a test image, just ten Kb of random data.

$ dd if=/dev/urandom of=image count=20
20+0 records in
20+0 records out
10240 bytes (10 kB) copied, 0.00334058 s, 3.1 MB/s

$ cksum image
3833649115 10240 image

We have got the test binary file in 10K and we knew its CRC check sum.

Run minicom: `minicom -o', reset the board.

RedBoot> help load
Load a file
   load [-r] [-v] [-d] [-h <host>] [-p <TCP port>][-m <varies>] [-c <channel_number>] [-b <base_address>] <file_name>

Enter a command

RedBoot> load -r -m ymodem -b %{freememlo}
C

Here press ^A-s, choose `ymodem', specify a path to that image and start
the loading. On a success, you must to see something like the below

CRaw file loaded 0x8100b800-0x8100dfff, assumed entry at 0x8100b800            
xyzModem - CRC mode, 83(SOH)/0(STX)/0(CAN) packets, 3 retries                  
RedBoot>

Then using the RedBoot's cksum command check the uploaded image:

RedBoot> cksum
Computing cksum for area 8100b800-8100e000
POSIX cksum = 3833649115 10240 (0xe480d7db 0x00002800)
RedBoot>

As you can see the CRCs are equals. Can you reproduce this on your
target? If you can, then we will try to answer on the second question.

Sergei.


> 
> Sergei Gavrikov-4 wrote:
> > 
> > grahamlab wrote:
> >> Hello again
> >> I am running Umbunto on a pc through  VM Virtual box and targetting
> >> the STM3120E dev board.
> >> I have successfuly built and downloaded RedBoot using St's demo flash
> >> loader. I have verified that this is running by connecting
> >> hyperterminal to the dev board and seeing the RedBoot gdb prompt.
> >> 
> >> I have then performed a default build of eCos for the dev board and
> >> then try to run gdb from the command line in the virtual machine.
> >> 
> >> The command used to invoke gdb was 
> >> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> >> 
> >> at the gdb prompt I type 
> >> set remotebaud 38400
> >> target remote /dev/ttyS0
> >> and get the output below
> > 
> > As I could understand you run GDB on VirtualBox, because your host OS !=
> > Linux. What's about the serial port settings? Be sure that there is not
> > set any flow control for the serial port. Use 'mode' command on the host
> > side and 'stty' on the guest side to check it. Can you download the same
> > executable in the RAM using X/Y/Z modem? Any virtual port is a something
> > different from the real one. First, be sure that you can upload a few
> > tens kilobytes on the target via virtual serial port, and then you can
> > dance with GDB. So, try RedBoot's `load' command and the HyperTerm's
> > `send file' ability to check a communication with the real serial port.
> > Then you can use the guest's `minicom' program to check that the virtual
> > serial port works as expected too. If you'll get the result, then try
> > GDB on the guest again.
> > 
> > 
> > Sergei
> > 
> > -- 
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> > 
> > 
> > 
> 
> -- 
> View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22885001.html
> Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Thanks for taking the time to help

I have tried what you suggested but don't get anything in the upload area in
minicom!!

What does that mean?

Graham

grahamlab wrote:
> 
> Hello again
> I am running Umbunto on a pc through  VM Virtual box and targetting the
> STM3120E dev board.
> I have successfuly built and downloaded RedBoot using St's demo flash
> loader. I have verified that this is running by connecting hyperterminal
> to the dev board and seeing the RedBoot gdb prompt.
> 
> I have then performed a default build of eCos for the dev board and then
> try to run gdb from the command line in the virtual machine.
> 
> The command used to invoke gdb was 
> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> 
> at the gdb prompt I type 
> set remotebaud 38400
> target remote /dev/ttyS0
> and get the output below
> 
> I have tried various builds with different baud rates.
> 
> Any help would be greatly appreciated
> 
> Graham
> 
> 
> Gary Thomas wrote:
>> 
>> grahamlab wrote:
>>> Hello everyone
>>> 
>>> When I try to run gdb I am seeing the following
>>> 
>>> (gdb) target remote /dev/ttyS0
>>> Remote debugging using /dev/ttyS0
>>> 0x08003b3a in ?? ()
>>> (gdb) load
>>> Loading section .rom_vectors, size 0x8 lma 0x68008000
>>> Loading section .ARM.exidx, size 0x10 lma 0x68008008
>>> Loading section .text, size 0x4330 lma 0x68008018
>>> Ignoring packet error, continuing...
>>> 
>>> can anyone tell me what I am doing wrong
>> 
>> Pretty hard to say since we've no idea what platform you're using :-(
>> 
>> Most likely cause is trying to load code into RAM that RedBoot
>> (or GDB stubs) uses.
>> 
>> Provide some [real] details and we might be able to help.
>> 
>> -- 
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>> 
>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22885709.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Gary Thomas]

grahamlab wrote:
> Thanks for taking the time to help
> 
> I have tried what you suggested but don't get anything in the upload area in
> minicom!!
> 
> What does that mean?

Still need details: "don't get anything in the upload area" is as
useless as "doctor, it hurts"

When you run the RedBoot 'load' command, what happens?  Do you see
lines like what Sergei proposed?

Send the output from your minicom so we can understand better what
your problem(s) are.

> grahamlab wrote:
>> Hello again
>> I am running Umbunto on a pc through  VM Virtual box and targetting the
>> STM3120E dev board.
>> I have successfuly built and downloaded RedBoot using St's demo flash
>> loader. I have verified that this is running by connecting hyperterminal
>> to the dev board and seeing the RedBoot gdb prompt.
>>
>> I have then performed a default build of eCos for the dev board and then
>> try to run gdb from the command line in the virtual machine.
>>
>> The command used to invoke gdb was 
>> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>
>> at the gdb prompt I type 
>> set remotebaud 38400
>> target remote /dev/ttyS0
>> and get the output below
>>
>> I have tried various builds with different baud rates.
>>
>> Any help would be greatly appreciated
>>
>> Graham
>>
>>
>> Gary Thomas wrote:
>>> grahamlab wrote:
>>>> Hello everyone
>>>>
>>>> When I try to run gdb I am seeing the following
>>>>
>>>> (gdb) target remote /dev/ttyS0
>>>> Remote debugging using /dev/ttyS0
>>>> 0x08003b3a in ?? ()
>>>> (gdb) load
>>>> Loading section .rom_vectors, size 0x8 lma 0x68008000
>>>> Loading section .ARM.exidx, size 0x10 lma 0x68008008
>>>> Loading section .text, size 0x4330 lma 0x68008018
>>>> Ignoring packet error, continuing...
>>>>
>>>> can anyone tell me what I am doing wrong
>>> Pretty hard to say since we've no idea what platform you're using :-(
>>>
>>> Most likely cause is trying to load code into RAM that RedBoot
>>> (or GDB stubs) uses.
>>>
>>> Provide some [real] details and we might be able to help.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Sat, Apr 04, 2009 at 10:16:30AM -0700, grahamlab wrote:
> 
> Thanks for taking the time to help
> 
> I have tried what you suggested but don't get anything in the upload area in
> minicom!!

Try the same, but using the real serial port (!VM) and HyperTerm.
Shutdown VM.  And try to upload any test file using HyperTerm. It
handles X/Y protocols too. Can you upload the files using HT?

Sergei.

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Hello

It appears I cannot load any file from within hyperterm or minicom.
Where do I find out if RedBoot was built with GDB suport

Thanks

Graham


Sergei Gavrikov-4 wrote:
> 
> On Sat, Apr 04, 2009 at 09:11:06AM -0700, grahamlab wrote:
>> 
>> Hi everyone
>> 
>> I can see the redboot monitor in minicom running in my virtual box but I
>> still cannot get gdb working - I get the same results
>> 
>> What else can I try?
>> 
>> Graham
>  
> To see the prompt is good news, but, that's not enough. You have to
> answer on 2 questions: 1st) Can you upload a file with RedBoot using X/Y
> modem protocol? and 2nd) Is RedBoot built with GDB support?
> 
> First, let's check a upload ability. I assume that your RedBoot supports
> X/Y modem protocols.
> 
> Create a test image, just ten Kb of random data.
> 
> $ dd if=/dev/urandom of=image count=20
> 20+0 records in
> 20+0 records out
> 10240 bytes (10 kB) copied, 0.00334058 s, 3.1 MB/s
> 
> $ cksum image
> 3833649115 10240 image
> 
> We have got the test binary file in 10K and we knew its CRC check sum.
> 
> Run minicom: `minicom -o', reset the board.
> 
> RedBoot> help load
> Load a file
>    load [-r] [-v] [-d] [-h <host>] [-p <TCP port>][-m <varies>] [-c
> <channel_number>] [-b <base_address>] <file_name>
> 
> Enter a command
> 
> RedBoot> load -r -m ymodem -b %{freememlo}
> C
> 
> Here press ^A-s, choose `ymodem', specify a path to that image and start
> the loading. On a success, you must to see something like the below
> 
> CRaw file loaded 0x8100b800-0x8100dfff, assumed entry at 0x8100b800            
> xyzModem - CRC mode, 83(SOH)/0(STX)/0(CAN) packets, 3 retries                  
> RedBoot>
> 
> Then using the RedBoot's cksum command check the uploaded image:
> 
> RedBoot> cksum
> Computing cksum for area 8100b800-8100e000
> POSIX cksum = 3833649115 10240 (0xe480d7db 0x00002800)
> RedBoot>
> 
> As you can see the CRCs are equals. Can you reproduce this on your
> target? If you can, then we will try to answer on the second question.
> 
> Sergei.
> 
> 
>> 
>> Sergei Gavrikov-4 wrote:
>> > 
>> > grahamlab wrote:
>> >> Hello again
>> >> I am running Umbunto on a pc through  VM Virtual box and targetting
>> >> the STM3120E dev board.
>> >> I have successfuly built and downloaded RedBoot using St's demo flash
>> >> loader. I have verified that this is running by connecting
>> >> hyperterminal to the dev board and seeing the RedBoot gdb prompt.
>> >> 
>> >> I have then performed a default build of eCos for the dev board and
>> >> then try to run gdb from the command line in the virtual machine.
>> >> 
>> >> The command used to invoke gdb was 
>> >> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> >> 
>> >> at the gdb prompt I type 
>> >> set remotebaud 38400
>> >> target remote /dev/ttyS0
>> >> and get the output below
>> > 
>> > As I could understand you run GDB on VirtualBox, because your host OS
>> !=
>> > Linux. What's about the serial port settings? Be sure that there is not
>> > set any flow control for the serial port. Use 'mode' command on the
>> host
>> > side and 'stty' on the guest side to check it. Can you download the
>> same
>> > executable in the RAM using X/Y/Z modem? Any virtual port is a
>> something
>> > different from the real one. First, be sure that you can upload a few
>> > tens kilobytes on the target via virtual serial port, and then you can
>> > dance with GDB. So, try RedBoot's `load' command and the HyperTerm's
>> > `send file' ability to check a communication with the real serial port.
>> > Then you can use the guest's `minicom' program to check that the
>> virtual
>> > serial port works as expected too. If you'll get the result, then try
>> > GDB on the guest again.
>> > 
>> > 
>> > Sergei
>> > 
>> > -- 
>> > Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> > 
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>> http://www.nabble.com/running-test-cases-tp22873616p22885001.html
>> Sent from the Sourceware - ecos-discuss mailing list archive at
>> Nabble.com.
>> 
>> 
>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22903721.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

I follow Sergei's instructions and get the minicom upload screen - but then
nothing happens.
When I try from Hyperterm it says "no response from remote system"

Any other ideas

Graham


Gary Thomas wrote:
> 
> grahamlab wrote:
>> Thanks for taking the time to help
>> 
>> I have tried what you suggested but don't get anything in the upload area
>> in
>> minicom!!
>> 
>> What does that mean?
> 
> Still need details: "don't get anything in the upload area" is as
> useless as "doctor, it hurts"
> 
> When you run the RedBoot 'load' command, what happens?  Do you see
> lines like what Sergei proposed?
> 
> Send the output from your minicom so we can understand better what
> your problem(s) are.
> 
>> grahamlab wrote:
>>> Hello again
>>> I am running Umbunto on a pc through  VM Virtual box and targetting the
>>> STM3120E dev board.
>>> I have successfuly built and downloaded RedBoot using St's demo flash
>>> loader. I have verified that this is running by connecting hyperterminal
>>> to the dev board and seeing the RedBoot gdb prompt.
>>>
>>> I have then performed a default build of eCos for the dev board and then
>>> try to run gdb from the command line in the virtual machine.
>>>
>>> The command used to invoke gdb was 
>>> arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>>
>>> at the gdb prompt I type 
>>> set remotebaud 38400
>>> target remote /dev/ttyS0
>>> and get the output below
>>>
>>> I have tried various builds with different baud rates.
>>>
>>> Any help would be greatly appreciated
>>>
>>> Graham
>>>
>>>
>>> Gary Thomas wrote:
>>>> grahamlab wrote:
>>>>> Hello everyone
>>>>>
>>>>> When I try to run gdb I am seeing the following
>>>>>
>>>>> (gdb) target remote /dev/ttyS0
>>>>> Remote debugging using /dev/ttyS0
>>>>> 0x08003b3a in ?? ()
>>>>> (gdb) load
>>>>> Loading section .rom_vectors, size 0x8 lma 0x68008000
>>>>> Loading section .ARM.exidx, size 0x10 lma 0x68008008
>>>>> Loading section .text, size 0x4330 lma 0x68008018
>>>>> Ignoring packet error, continuing...
>>>>>
>>>>> can anyone tell me what I am doing wrong
>>>> Pretty hard to say since we've no idea what platform you're using :-(
>>>>
>>>> Most likely cause is trying to load code into RAM that RedBoot
>>>> (or GDB stubs) uses.
>>>>
>>>> Provide some [real] details and we might be able to help.
> 
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904017.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Chris Holgate]

Hi Graham,

It's starting to sound as though the serial port emulation on your
virtualisation software may not be up to the job.  Unless you have a
compelling reason for using Linux, it might be worth installing cygwin
and trying the native Windows tools instead.

http://ecos.sourceware.org/cygwin.html

Chris.

grahamlab wrote:
> Hello
> 
> It appears I cannot load any file from within hyperterm or minicom.
> Where do I find out if RedBoot was built with GDB suport
> 
> Thanks
> 
> Graham
> 
> 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Chris

I cannot even load a file using Hyperterm in windows - it cannot reach the
remote machine.



Chris Holgate wrote:
> 
> Hi Graham,
> 
> It's starting to sound as though the serial port emulation on your
> virtualisation software may not be up to the job.  Unless you have a
> compelling reason for using Linux, it might be worth installing cygwin
> and trying the native Windows tools instead.
> 
> http://ecos.sourceware.org/cygwin.html
> 
> Chris.
> 
> grahamlab wrote:
>> Hello
>> 
>> It appears I cannot load any file from within hyperterm or minicom.
>> Where do I find out if RedBoot was built with GDB suport
>> 
>> Thanks
>> 
>> Graham
>> 
>> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904139.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

grahamlab wrote:
> 
> I follow Sergei's instructions and get the minicom upload screen - but then
> nothing happens.
> When I try from Hyperterm it says "no response from remote system"
> 
> Graham

I just wonder, Do you enter `load' command in RedBoot before to start
the upload?

Redboot> load -r -b %{freememlo} -m ymodem
C

At once, as you hit <Enter> you have to see 'C' letter and then you must
start upload ('send file' in HT). Again, what's about flow control?
Valid settings are 38400,n,8,1 (no software/hardware flow control).


Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

At last some success!!
I can download a file using hyperterm.
I cannot do this in minicom, I think it may have to do with flow control.
How do I set flow control in the Linux environment?

Graham

Sergei Gavrikov-4 wrote:
> 
> grahamlab wrote:
>> 
>> I follow Sergei's instructions and get the minicom upload screen - but
>> then
>> nothing happens.
>> When I try from Hyperterm it says "no response from remote system"
>> 
>> Graham
> 
> I just wonder, Do you enter `load' command in RedBoot before to start
> the upload?
> 
> Redboot> load -r -b %{freememlo} -m ymodem
> C
> 
> At once, as you hit <Enter> you have to see 'C' letter and then you must
> start upload ('send file' in HT). Again, what's about flow control?
> Valid settings are 38400,n,8,1 (no software/hardware flow control).
> 
> 
> Sergei
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904693.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 01:55:02AM -0700, grahamlab wrote:
> 
> At last some success!!
> I can download a file using hyperterm.
> I cannot do this in minicom, I think it may have to do with flow control.
> How do I set flow control in the Linux environment?

Using minicom:

^A-o
  Serial port setup
    ...


Or prepare

cat >~/.minicom.redboot <<EOF
pu port             /dev/ttyS0
pu baudrate         38400
pu bits             8
pu parity           N
pu stopbits         1
pu rtscts           No
EOF

and then run minicom as 'minicom -o redboot'

To check the settings

$ stty -a -F /dev/ttyS0	;# man stty, man minicom.

Sergei

> Graham
> 
> Sergei Gavrikov-4 wrote:
> > 
> > grahamlab wrote:
> >> 
> >> I follow Sergei's instructions and get the minicom upload screen - but
> >> then
> >> nothing happens.
> >> When I try from Hyperterm it says "no response from remote system"
> >> 
> >> Graham
> > 
> > I just wonder, Do you enter `load' command in RedBoot before to start
> > the upload?
> > 
> > Redboot> load -r -b %{freememlo} -m ymodem
> > C
> > 
> > At once, as you hit <Enter> you have to see 'C' letter and then you must
> > start upload ('send file' in HT). Again, what's about flow control?
> > Valid settings are 38400,n,8,1 (no software/hardware flow control).
> > 
> > 
> > Sergei
> > 
> > -- 
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> > 
> > 
> > 
> 
> -- 
> View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904693.html
> Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 12:06:35PM +0300, Sergei Gavrikov wrote:
> On Mon, Apr 06, 2009 at 01:55:02AM -0700, grahamlab wrote:
> > 
> > At last some success!!
> > I can download a file using hyperterm.
> > I cannot do this in minicom, I think it may have to do with flow control.
> > How do I set flow control in the Linux environment?
> 
> Using minicom:
> 
> ^A-o
>   Serial port setup
>     ...
> 
> 
> Or prepare
> 
> cat >~/.minicom.redboot <<EOF
> pu port             /dev/ttyS0
> pu baudrate         38400
> pu bits             8
> pu parity           N
> pu stopbits         1
> pu rtscts           No
> EOF
> 
> and then run minicom as 'minicom -o redboot'
> 
> To check the settings
> 
> $ stty -a -F /dev/ttyS0	;# man stty, man minicom.
> 

If you'll get a success with the upload using minicom... Then try

$ stty -crtscts -F /dev/ttyS0
$ arm-eabi-gdb -q -nx <...>/test

But, I belived that GDB sets up a serial port properly.

Sergei

> 
> > Graham
> > 
> > Sergei Gavrikov-4 wrote:
> > > 
> > > grahamlab wrote:
> > >> 
> > >> I follow Sergei's instructions and get the minicom upload screen - but
> > >> then
> > >> nothing happens.
> > >> When I try from Hyperterm it says "no response from remote system"
> > >> 
> > >> Graham
> > > 
> > > I just wonder, Do you enter `load' command in RedBoot before to start
> > > the upload?
> > > 
> > > Redboot> load -r -b %{freememlo} -m ymodem
> > > C
> > > 
> > > At once, as you hit <Enter> you have to see 'C' letter and then you must
> > > start upload ('send file' in HT). Again, what's about flow control?
> > > Valid settings are 38400,n,8,1 (no software/hardware flow control).
> > > 
> > > 
> > > Sergei
> > > 
> > > -- 
> > > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> > > 
> > > 
> > > 
> > 
> > -- 
> > View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904693.html
> > Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
> > 
> > 
> > -- 
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Hi Sergei

I am sure I have the correct settings in mincom but still cannot download a
file

Is there anything else I can try?

Graham

Sergei Gavrikov-4 wrote:
> 
> On Mon, Apr 06, 2009 at 01:55:02AM -0700, grahamlab wrote:
>> 
>> At last some success!!
>> I can download a file using hyperterm.
>> I cannot do this in minicom, I think it may have to do with flow control.
>> How do I set flow control in the Linux environment?
> 
> Using minicom:
> 
> ^A-o
>   Serial port setup
>     ...
> 
> 
> Or prepare
> 
> cat >~/.minicom.redboot <<EOF
> pu port             /dev/ttyS0
> pu baudrate         38400
> pu bits             8
> pu parity           N
> pu stopbits         1
> pu rtscts           No
> EOF
> 
> and then run minicom as 'minicom -o redboot'
> 
> To check the settings
> 
> $ stty -a -F /dev/ttyS0	;# man stty, man minicom.
> 
> Sergei
> 
>> Graham
>> 
>> Sergei Gavrikov-4 wrote:
>> > 
>> > grahamlab wrote:
>> >> 
>> >> I follow Sergei's instructions and get the minicom upload screen - but
>> >> then
>> >> nothing happens.
>> >> When I try from Hyperterm it says "no response from remote system"
>> >> 
>> >> Graham
>> > 
>> > I just wonder, Do you enter `load' command in RedBoot before to start
>> > the upload?
>> > 
>> > Redboot> load -r -b %{freememlo} -m ymodem
>> > C
>> > 
>> > At once, as you hit <Enter> you have to see 'C' letter and then you
>> must
>> > start upload ('send file' in HT). Again, what's about flow control?
>> > Valid settings are 38400,n,8,1 (no software/hardware flow control).
>> > 
>> > 
>> > Sergei
>> > 
>> > -- 
>> > Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> > 
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>> http://www.nabble.com/running-test-cases-tp22873616p22904693.html
>> Sent from the Sourceware - ecos-discuss mailing list archive at
>> Nabble.com.
>> 
>> 
>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904967.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 02:14:15AM -0700, grahamlab wrote:
> 
> Hi Sergei
> 
> I am sure I have the correct settings in mincom but still cannot download a
> file
> 
> Is there anything else I can try?

Please, do not top post.

So, you have the success with HT (!VM). VM's serial ports are something
specific. It may work, it may not work. But there is a light in a tube.
You can try to use serial-to-tcp bridge. It's software what you can run
on the host (windows) and all data flow from/to the real serial port
will be directed to/from the specified TCP port.

If you disable serial ports handling in VM, start such a bridge program,
then it can be possible (I hope) to connect on the specified TCP port
using GDB on guest (Linux). Can you ping the Host PC from the Guest OS?

... And what's wrong with cygwin environment?

Sergei

> 
> Graham
> 
> Sergei Gavrikov-4 wrote:
> > 
> > On Mon, Apr 06, 2009 at 01:55:02AM -0700, grahamlab wrote:
> >> 
> >> At last some success!!
> >> I can download a file using hyperterm.
> >> I cannot do this in minicom, I think it may have to do with flow control.
> >> How do I set flow control in the Linux environment?
> > 
> > Using minicom:
> > 
> > ^A-o
> >   Serial port setup
> >     ...
> > 
> > 
> > Or prepare
> > 
> > cat >~/.minicom.redboot <<EOF
> > pu port             /dev/ttyS0
> > pu baudrate         38400
> > pu bits             8
> > pu parity           N
> > pu stopbits         1
> > pu rtscts           No
> > EOF
> > 
> > and then run minicom as 'minicom -o redboot'
> > 
> > To check the settings
> > 
> > $ stty -a -F /dev/ttyS0	;# man stty, man minicom.
> > 
> > Sergei
> > 
> >> Graham
> >> 
> >> Sergei Gavrikov-4 wrote:
> >> > 
> >> > grahamlab wrote:
> >> >> 
> >> >> I follow Sergei's instructions and get the minicom upload screen - but
> >> >> then
> >> >> nothing happens.
> >> >> When I try from Hyperterm it says "no response from remote system"
> >> >> 
> >> >> Graham
> >> > 
> >> > I just wonder, Do you enter `load' command in RedBoot before to start
> >> > the upload?
> >> > 
> >> > Redboot> load -r -b %{freememlo} -m ymodem
> >> > C
> >> > 
> >> > At once, as you hit <Enter> you have to see 'C' letter and then you
> >> must
> >> > start upload ('send file' in HT). Again, what's about flow control?
> >> > Valid settings are 38400,n,8,1 (no software/hardware flow control).
> >> > 
> >> > 
> >> > Sergei
> >> > 
> >> > -- 
> >> > Before posting, please read the FAQ:
> >> http://ecos.sourceware.org/fom/ecos
> >> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> >> > 
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context:
> >> http://www.nabble.com/running-test-cases-tp22873616p22904693.html
> >> Sent from the Sourceware - ecos-discuss mailing list archive at
> >> Nabble.com.
> >> 
> >> 
> >> -- 
> >> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> >> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> > 
> > -- 
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> > 
> > 
> > 
> 
> -- 
> View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22904967.html
> Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Hello again

So I gave up with virtual box and installed cygwin.
Now when I run the gdb command I am returned to the shell prompt nothing
else happens!

The manual states 
Start a command shell (such as a Cygwin shell window in Windows) with the
environment variables set as described in the toolchain documentation

Where is the toolchain documentation, what environment variables do I need?

thanks

Graham


Sergei Gavrikov-4 wrote:
> 
> On Mon, Apr 06, 2009 at 02:14:15AM -0700, grahamlab wrote:
>> 
>> Hi Sergei
>> 
>> I am sure I have the correct settings in mincom but still cannot download
>> a
>> file
>> 
>> Is there anything else I can try?
> 
> Please, do not top post.
> 
> So, you have the success with HT (!VM). VM's serial ports are something
> specific. It may work, it may not work. But there is a light in a tube.
> You can try to use serial-to-tcp bridge. It's software what you can run
> on the host (windows) and all data flow from/to the real serial port
> will be directed to/from the specified TCP port.
> 
> If you disable serial ports handling in VM, start such a bridge program,
> then it can be possible (I hope) to connect on the specified TCP port
> using GDB on guest (Linux). Can you ping the Host PC from the Guest OS?
> 
> ... And what's wrong with cygwin environment?
> 
> Sergei
> 
>> 
>> Graham
>> 
>> Sergei Gavrikov-4 wrote:
>> > 
>> > On Mon, Apr 06, 2009 at 01:55:02AM -0700, grahamlab wrote:
>> >> 
>> >> At last some success!!
>> >> I can download a file using hyperterm.
>> >> I cannot do this in minicom, I think it may have to do with flow
>> control.
>> >> How do I set flow control in the Linux environment?
>> > 
>> > Using minicom:
>> > 
>> > ^A-o
>> >   Serial port setup
>> >     ...
>> > 
>> > 
>> > Or prepare
>> > 
>> > cat >~/.minicom.redboot <<EOF
>> > pu port             /dev/ttyS0
>> > pu baudrate         38400
>> > pu bits             8
>> > pu parity           N
>> > pu stopbits         1
>> > pu rtscts           No
>> > EOF
>> > 
>> > and then run minicom as 'minicom -o redboot'
>> > 
>> > To check the settings
>> > 
>> > $ stty -a -F /dev/ttyS0	;# man stty, man minicom.
>> > 
>> > Sergei
>> > 
>> >> Graham
>> >> 
>> >> Sergei Gavrikov-4 wrote:
>> >> > 
>> >> > grahamlab wrote:
>> >> >> 
>> >> >> I follow Sergei's instructions and get the minicom upload screen -
>> but
>> >> >> then
>> >> >> nothing happens.
>> >> >> When I try from Hyperterm it says "no response from remote system"
>> >> >> 
>> >> >> Graham
>> >> > 
>> >> > I just wonder, Do you enter `load' command in RedBoot before to
>> start
>> >> > the upload?
>> >> > 
>> >> > Redboot> load -r -b %{freememlo} -m ymodem
>> >> > C
>> >> > 
>> >> > At once, as you hit <Enter> you have to see 'C' letter and then you
>> >> must
>> >> > start upload ('send file' in HT). Again, what's about flow control?
>> >> > Valid settings are 38400,n,8,1 (no software/hardware flow control).
>> >> > 
>> >> > 
>> >> > Sergei
>> >> > 
>> >> > -- 
>> >> > Before posting, please read the FAQ:
>> >> http://ecos.sourceware.org/fom/ecos
>> >> > and search the list archive:
>> http://ecos.sourceware.org/ml/ecos-discuss
>> >> > 
>> >> > 
>> >> > 
>> >> 
>> >> -- 
>> >> View this message in context:
>> >> http://www.nabble.com/running-test-cases-tp22873616p22904693.html
>> >> Sent from the Sourceware - ecos-discuss mailing list archive at
>> >> Nabble.com.
>> >> 
>> >> 
>> >> -- 
>> >> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> >> and search the list archive:
>> http://ecos.sourceware.org/ml/ecos-discuss
>> > 
>> > -- 
>> > Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>> > 
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>> http://www.nabble.com/running-test-cases-tp22873616p22904967.html
>> Sent from the Sourceware - ecos-discuss mailing list archive at
>> Nabble.com.
>> 
>> 
>> -- 
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22906503.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 12:39:07PM +0300, Sergei Gavrikov wrote:
> On Mon, Apr 06, 2009 at 02:14:15AM -0700, grahamlab wrote:
> > 
> > I am sure I have the correct settings in mincom but still cannot download a
> > file
> > 
> > Is there anything else I can try?
> 
> Please, do not top post.
> 
> So, you have the success with HT (!VM). VM's serial ports are something
> specific. It may work, it may not work. But there is a light in a tube.

As far as I remember, you wrote that you did see the RedBoot's prompt in
minicom too on Guest OS (it is good news). Can you send some output?
Invoke the below commands on Linux Guest, when VM'd started, but, do not
start GDB or minicom.

$ lsof /dev/ttyS*
<copy output>

$ fuser /dev/ttyS*
<copy and send output>

$ stty -F /dev/ttyS0
<copy and send output>


Sergei


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

grahamlab wrote:
> 
> Hello again
> 
> So I gave up with virtual box and installed cygwin.
> Now when I run the gdb command I am returned to the shell prompt nothing
> else happens!
> 
> The manual states 
> Start a command shell (such as a Cygwin shell window in Windows) with the
> environment variables set as described in the toolchain documentation
> 
> Where is the toolchain documentation, what environment variables do I need?

Exactly the same things as on Linux: ECOS_REPOSITORY and PATH variables.
There is ecosenv.sh script there, and you must source it:

$ source /opt/ecos/ecosenv.sh

or

$ . /opt/ecos/ecosenv.sh>

Then, I typed 3 lines the below as a mentor:

---
It seems for me that it's time for you to read the eCos documentation
http://ecos.sourceware.org/docs-latest/

Your eCos distro has the same HTML pages.
---

and I followed by the link the below and it was surprise for me this page
http://ecos.sourceware.org/docs-latest/user-guide/user-guide-installation.html

directed me here
http://ecos.sourceware.org/getstart.html

There is no much info for eCos N.B. about environment variables :-) on
the getstart.html page. So, in cygwin's bash prompt, type

$ . /opt/ecos/ecosenv.sh

then try

$ echo $ECOS_REPOSITORY

and

$ echo $PATH

Do you see a path to arm-eabi GNU tools?

$ arm-eabi-gcc -v


Hey, eCos gurus, where is step by step installation (preparation) guide
for eCos N.B.? Enlighten Graham, please. My mother language is not
English, so, it's difficult for me to assist Graham. Graham, if you are
not CLI guy, then use `eCos configtool'.

Graham, I'm sorry, but in any case, a reading is a right way to start
with anything.

Regards,

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[grahamlab]

Sergei

I have read the documentation and followed your instructions to the letter.
I have the correct environement variables but when I enter arm-eabi-gdb I
get retruned to the shell prompt immediately. 
I do not know why this is the case

Thank-you for your patience

Graham


Sergei Gavrikov-4 wrote:
> 
> grahamlab wrote:
>> 
>> Hello again
>> 
>> So I gave up with virtual box and installed cygwin.
>> Now when I run the gdb command I am returned to the shell prompt nothing
>> else happens!
>> 
>> The manual states 
>> Start a command shell (such as a Cygwin shell window in Windows) with the
>> environment variables set as described in the toolchain documentation
>> 
>> Where is the toolchain documentation, what environment variables do I
>> need?
> 
> Exactly the same things as on Linux: ECOS_REPOSITORY and PATH variables.
> There is ecosenv.sh script there, and you must source it:
> 
> $ source /opt/ecos/ecosenv.sh
> 
> or
> 
> $ . /opt/ecos/ecosenv.sh>
> 
> Then, I typed 3 lines the below as a mentor:
> 
> ---
> It seems for me that it's time for you to read the eCos documentation
> http://ecos.sourceware.org/docs-latest/
> 
> Your eCos distro has the same HTML pages.
> ---
> 
> and I followed by the link the below and it was surprise for me this page
> http://ecos.sourceware.org/docs-latest/user-guide/user-guide-installation.html
> 
> directed me here
> http://ecos.sourceware.org/getstart.html
> 
> There is no much info for eCos N.B. about environment variables :-) on
> the getstart.html page. So, in cygwin's bash prompt, type
> 
> $ . /opt/ecos/ecosenv.sh
> 
> then try
> 
> $ echo $ECOS_REPOSITORY
> 
> and
> 
> $ echo $PATH
> 
> Do you see a path to arm-eabi GNU tools?
> 
> $ arm-eabi-gcc -v
> 
> 
> Hey, eCos gurus, where is step by step installation (preparation) guide
> for eCos N.B.? Enlighten Graham, please. My mother language is not
> English, so, it's difficult for me to assist Graham. Graham, if you are
> not CLI guy, then use `eCos configtool'.
> 
> Graham, I'm sorry, but in any case, a reading is a right way to start
> with anything.
> 
> Regards,
> 
> Sergei
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/running-test-cases-tp22873616p22907700.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

grahamlab wrote:
> 
> Sergei
> 
> I have read the documentation and followed your instructions to the letter.
> I have the correct environement variables but when I enter arm-eabi-gdb I
> get retruned to the shell prompt immediately. 
> I do not know why this is the case

I'm sorry I do not use cygwin. But, I remember that someone wrote about
`libmpfr1'. Have you installed the library. Refer to
http://ecos.sourceware.org/cygwin.html and see the NOTE there.

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] running test cases

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 02:09:41PM +0300, Sergei Gavrikov wrote:
> On Mon, Apr 06, 2009 at 12:39:07PM +0300, Sergei Gavrikov wrote:
> > On Mon, Apr 06, 2009 at 02:14:15AM -0700, grahamlab wrote:
> > > 
> > > I am sure I have the correct settings in mincom but still cannot download a
> > > file
> > > 
> > > Is there anything else I can try?
> > 
> > Please, do not top post.
> > 
> > So, you have the success with HT (!VM). VM's serial ports are something
> > specific. It may work, it may not work. But there is a light in a tube.
> 
> As far as I remember, you wrote that you did see the RedBoot's prompt in
> minicom too on Guest OS (it is good news). Can you send some output?
> Invoke the below commands on Linux Guest, when VM'd started, but, do not
> start GDB or minicom.

Graham, you wrote that you successfully build eCos under VirtualBox. I
hope that you did not delete that image, because, you had a working
environment. You had one issue: serial port connection on VM. I brief
look at VirtualBox' User Manual (there is pdf on their site). They do
not talk about any issues with virtual serial ports, IMHO, you must
configure the ports properly. See chaptres 3.7.6, 8.5.4 from the Sun xVM
Virtual Box User Manual (2.1.4).

I sure that Sun offers an excellent virtualization. And it seems for me
that if you configure their VM properly, your problem will go away. You
can ask about your issue just here
http://www.virtualbox.org/wiki/Community


Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss