[ECOS] arm-eabi-gdb

[ECOS] arm-eabi-gdb

[grahamlab]

Hi
I have just installed Cygwin and ecos.
I have built the test cases for my ecos configuration.
When I try to invoke the arm-eabi-gdb command from a Cygwin command window I
get retruned to the command prompt immediately.

Does anyone know why this happens

THnaks

Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22908205.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] arm-eabi-gdb

[Chris Zimman]

> Hi
> I have just installed Cygwin and ecos.
> I have built the test cases for my ecos configuration.
> When I try to invoke the arm-eabi-gdb command from a Cygwin command
> window I
> get retruned to the command prompt immediately.
> 
> Does anyone know why this happens

Graham,

There are virtually unlimited reasons that things can be not working.
There's no information in your post that would in any way enable anyone to
help you any further.

I suggest that:

(1)  Please stop top posting -- if you don't understand what that is, it's
when you reply to a message and put your reply above original message.  While
I don't personally care either way, top posting is not looked upon well on
this list.

(2)  Make sure your Cygwin (or whatever you're using) environment is working
OK first before you worry about getting GDB to talk to Redboot.  If you are
having general Cygwin troubles, there are Cygwin specific mailing lists that
assist with such things.  There is also commercial support (Gary and/or
eCosCentric), which I have been pointing a lot of people to as of late, since
some of the questions that have been coming up are more suited to that level
of support.

(3)  Don't repost the same question if you don't get an answer immediately.

Thanks

--Chris

--
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] arm-eabi-gdb

[grahamlab]

Chris Zimman wrote:
> 
>> Hi
>> I have just installed Cygwin and ecos.
>> I have built the test cases for my ecos configuration.
>> When I try to invoke the arm-eabi-gdb command from a Cygwin command
>> window I
>> get retruned to the command prompt immediately.
>> 
>> Does anyone know why this happens
> 
> Graham,
> 
> There are virtually unlimited reasons that things can be not working.
> There's no information in your post that would in any way enable anyone to
> help you any further.
> 
> I suggest that:
> 
> (1)  Please stop top posting -- if you don't understand what that is, it's
> when you reply to a message and put your reply above original message. 
> While
> I don't personally care either way, top posting is not looked upon well on
> this list.
> 
> (2)  Make sure your Cygwin (or whatever you're using) environment is
> working
> OK first before you worry about getting GDB to talk to Redboot.  If you
> are
> having general Cygwin troubles, there are Cygwin specific mailing lists
> that
> assist with such things.  There is also commercial support (Gary and/or
> eCosCentric), which I have been pointing a lot of people to as of late,
> since
> some of the questions that have been coming up are more suited to that
> level
> of support.
> 
> (3)  Don't repost the same question if you don't get an answer
> immediately.
> 
> Thanks
> 
> --Chris
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 

Chris

I started a new thread as this is a different (although related) topic.
I have read the eCos documentation and followed the instructions for
downloading Cygwin and then installing Ecos.
I can run the Ecos configuration tool and build.
Cygwin appears to be installed correctly.
But when I type
arm-eabi-gdb -help
nothing happens and I get returned to the command prompt.
my path is set correctly and arm-eabi-gdb exists
I am getting very frustrated at this point and would be grateful of any
information anyone can supply in this regard

Thanks 

Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22910034.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] arm-eabi-gdb

[Gary Thomas]

grahamlab wrote:
> 
> 
> Chris Zimman wrote:
>>> Hi
>>> I have just installed Cygwin and ecos.
>>> I have built the test cases for my ecos configuration.
>>> When I try to invoke the arm-eabi-gdb command from a Cygwin command
>>> window I
>>> get retruned to the command prompt immediately.
>>>
>>> Does anyone know why this happens
>> Graham,
>>
>> There are virtually unlimited reasons that things can be not working.
>> There's no information in your post that would in any way enable anyone to
>> help you any further.
>>
>> I suggest that:
>>
>> (1)  Please stop top posting -- if you don't understand what that is, it's
>> when you reply to a message and put your reply above original message. 
>> While
>> I don't personally care either way, top posting is not looked upon well on
>> this list.
>>
>> (2)  Make sure your Cygwin (or whatever you're using) environment is
>> working
>> OK first before you worry about getting GDB to talk to Redboot.  If you
>> are
>> having general Cygwin troubles, there are Cygwin specific mailing lists
>> that
>> assist with such things.  There is also commercial support (Gary and/or
>> eCosCentric), which I have been pointing a lot of people to as of late,
>> since
>> some of the questions that have been coming up are more suited to that
>> level
>> of support.
>>
>> (3)  Don't repost the same question if you don't get an answer
>> immediately.
>>
>> Thanks
>>
>> --Chris
>>
>> --
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>>
>>
> 
> Chris
> 
> I started a new thread as this is a different (although related) topic.
> I have read the eCos documentation and followed the instructions for
> downloading Cygwin and then installing Ecos.
> I can run the Ecos configuration tool and build.
> Cygwin appears to be installed correctly.
> But when I type
> arm-eabi-gdb -help
> nothing happens and I get returned to the command prompt.
> my path is set correctly and arm-eabi-gdb exists
> I am getting very frustrated at this point and would be grateful of any
> information anyone can supply in this regard

Actually, Chris did give you some valuable feedback.  You had
the basic stuff going using VirtualBox, albeit with problems.
Now that you've tried CygWin, you can't even get that far.
Not surprising given all the troubles folks have had with
CygWin over time.

Go back to VirtualBox and _really_ try to figure out what your
trouble is.  This does work - has for many folks - so you must
just have something setup wrong, most likely the actual serial
connection to your board.

One question - when you originally reported that you could
get the RedBoot prompt in your minicom window and then had
trouble getting code to download via GDB, did you still have
the minicom window open?



-- 
------------------------------------------------------------
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] arm-eabi-gdb

[grahamlab]

Gary Thomas wrote:
> 
> grahamlab wrote:
>> 
>> 
>> Chris Zimman wrote:
>>>> Hi
>>>> I have just installed Cygwin and ecos.
>>>> I have built the test cases for my ecos configuration.
>>>> When I try to invoke the arm-eabi-gdb command from a Cygwin command
>>>> window I
>>>> get retruned to the command prompt immediately.
>>>>
>>>> Does anyone know why this happens
>>> Graham,
>>>
>>> There are virtually unlimited reasons that things can be not working.
>>> There's no information in your post that would in any way enable anyone
>>> to
>>> help you any further.
>>>
>>> I suggest that:
>>>
>>> (1)  Please stop top posting -- if you don't understand what that is,
>>> it's
>>> when you reply to a message and put your reply above original message. 
>>> While
>>> I don't personally care either way, top posting is not looked upon well
>>> on
>>> this list.
>>>
>>> (2)  Make sure your Cygwin (or whatever you're using) environment is
>>> working
>>> OK first before you worry about getting GDB to talk to Redboot.  If you
>>> are
>>> having general Cygwin troubles, there are Cygwin specific mailing lists
>>> that
>>> assist with such things.  There is also commercial support (Gary and/or
>>> eCosCentric), which I have been pointing a lot of people to as of late,
>>> since
>>> some of the questions that have been coming up are more suited to that
>>> level
>>> of support.
>>>
>>> (3)  Don't repost the same question if you don't get an answer
>>> immediately.
>>>
>>> Thanks
>>>
>>> --Chris
>>>
>>> --
>>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>>
>>>
>>>
>> 
>> Chris
>> 
>> I started a new thread as this is a different (although related) topic.
>> I have read the eCos documentation and followed the instructions for
>> downloading Cygwin and then installing Ecos.
>> I can run the Ecos configuration tool and build.
>> Cygwin appears to be installed correctly.
>> But when I type
>> arm-eabi-gdb -help
>> nothing happens and I get returned to the command prompt.
>> my path is set correctly and arm-eabi-gdb exists
>> I am getting very frustrated at this point and would be grateful of any
>> information anyone can supply in this regard
> 
> Actually, Chris did give you some valuable feedback.  You had
> the basic stuff going using VirtualBox, albeit with problems.
> Now that you've tried CygWin, you can't even get that far.
> Not surprising given all the troubles folks have had with
> CygWin over time.
> 
> Go back to VirtualBox and _really_ try to figure out what your
> trouble is.  This does work - has for many folks - so you must
> just have something setup wrong, most likely the actual serial
> connection to your board.
> 
> One question - when you originally reported that you could
> get the RedBoot prompt in your minicom window and then had
> trouble getting code to download via GDB, did you still have
> the minicom window open?
> 
> 
> 
> -- 
> ------------------------------------------------------------
> 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
> 
> 
> 
I did not have mincom running.
I type arm-eabi-gdb -nw DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
at the gdb prompt 
set remotebaud 38400
target remote /dev/ttyS0

After this according to the ecos documentation I should see some information
about the current loaction and language.

What I get is
Remote Debugging using /dev/ttyS0
0x08003b3a in ?? ()

I dont get any extra information.

Is this a problem?

Thanks again

Graham


-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22910997.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] arm-eabi-gdb

[Chris Zimman]

[-- snip --]

Quoting reams of previous message is also not required, just enough to sort
of continue the conversation.

> I did not have mincom running.
> I type arm-eabi-gdb -nw
> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> at the gdb prompt
> set remotebaud 38400
> target remote /dev/ttyS0
> 
> After this according to the ecos documentation I should see some
> information
> about the current loaction and language.
> 
> What I get is
> Remote Debugging using /dev/ttyS0
> 0x08003b3a in ?? ()
> 
> I dont get any extra information.

It looks as though GDB has attached and you are sitting at the current PC.

> Is this a problem?

No, not necessarily.  You may well be sitting in Redboot also, which GDB
knows nothing about in terms of symbols (since you haven't told it about them
yet).

I don't mean this in any kind of an insulting way, but do you know how to use
GDB for something like this (eg. are you familiar with add-symbol-file)?
Did you build the tests with debugging enabled (eg. -g)?

Again, because there isn't really a ton of info here, I can't just look at it
and say "Ah ha!  The problem is [whatever]"

--Chris

--
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] arm-eabi-gdb

[Sergei Gavrikov]

grahamlab wrote:

[snip]

> I did not have mincom running.

Graham,

here http://ecos.sourceware.org/ml/ecos-discuss/2009-04/msg00041.html
you said opposite thing.

It's important to know: can you interact with the board using minicom on
guest VM? It's pity that you did not follow those my tips (lsof, fuser,
stty) http://ecos.sourceware.org/ml/ecos-discuss/2009-04/msg00067.html

Can you paste the outputs?

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] arm-eabi-gdb

[RONETIX - Ilko Iliev]

Dear Graham,

I recommend you to use JTAG debugging - you will spend a lot of time.

-- 
With best regards,
Ilko Iliev
Ronetix Development Tools GmbH
CPU Modules, JTAG/BDM Emulators and Flash Programmers
Waidhausenstrasse 13/5, 1140 Vienna, Austria
E-Mail: iliev@ronetix.at; Web: www.ronetix.at




Chris Zimman wrote:
> [-- snip --]
>
> Quoting reams of previous message is also not required, just enough to sort
> of continue the conversation.
>
>   
>> I did not have mincom running.
>> I type arm-eabi-gdb -nw
>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> at the gdb prompt
>> set remotebaud 38400
>> target remote /dev/ttyS0
>>
>> After this according to the ecos documentation I should see some
>> information
>> about the current loaction and language.
>>
>> What I get is
>> Remote Debugging using /dev/ttyS0
>> 0x08003b3a in ?? ()
>>
>> I dont get any extra information.
>>     
>
> It looks as though GDB has attached and you are sitting at the current PC.
>
>   
>> Is this a problem?
>>     
>
> No, not necessarily.  You may well be sitting in Redboot also, which GDB
> knows nothing about in terms of symbols (since you haven't told it about them
> yet).
>
> I don't mean this in any kind of an insulting way, but do you know how to use
> GDB for something like this (eg. are you familiar with add-symbol-file)?
> Did you build the tests with debugging enabled (eg. -g)?
>
> Again, because there isn't really a ton of info here, I can't just look at it
> and say "Ah ha!  The problem is [whatever]"
>
> --Chris
>
>   



-- 
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] arm-eabi-gdb

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 05:46:21PM +0200, RONETIX - Ilko Iliev wrote:
> Dear Graham,
>
> I recommend you to use JTAG debugging - you will spend a lot of time.

Graham, of course, RONETIX JTAG debuggers are nice tools, but, I would
add, you will spend a money in these crisis days. If you have enougth
RAM on the board, make a serial port work for you.

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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> grahamlab wrote:
> 
> [snip]
> 
>> I did not have mincom running.
> 
> Graham,
> 
> here http://ecos.sourceware.org/ml/ecos-discuss/2009-04/msg00041.html
> you said opposite thing.
> 
> It's important to know: can you interact with the board using minicom on
> guest VM? It's pity that you did not follow those my tips (lsof, fuser,
> stty) http://ecos.sourceware.org/ml/ecos-discuss/2009-04/msg00067.html
> 
> Can you paste the outputs?
> 
> 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
> 
> 
> 

Sergei
When I try to send a file using minicom I get the ymodem upload screen - it
is blank and remains so
lsof /dev/ttyS* - returns with no output
fuser /dev/ttyS* - returns with no output

output from stty - 
speed 38400 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt =
^R;
werase = ^W; lnext = ^V; flush = ^O; min = 0; time = 10;
-parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
-ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
-echoprt
-echoctl -echoke

Does this give you any clues?

Thanks Graham


-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22912027.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] arm-eabi-gdb

[grahamlab]

Chris Zimman wrote:
> 
> [-- snip --]
> 
> Quoting reams of previous message is also not required, just enough to
> sort
> of continue the conversation.
> 
>> I did not have mincom running.
>> I type arm-eabi-gdb -nw
>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> at the gdb prompt
>> set remotebaud 38400
>> target remote /dev/ttyS0
>> 
>> After this according to the ecos documentation I should see some
>> information
>> about the current loaction and language.
>> 
>> What I get is
>> Remote Debugging using /dev/ttyS0
>> 0x08003b3a in ?? ()
>> 
>> I dont get any extra information.
> 
> It looks as though GDB has attached and you are sitting at the current PC.
> 
>> Is this a problem?
> 
> No, not necessarily.  You may well be sitting in Redboot also, which GDB
> knows nothing about in terms of symbols (since you haven't told it about
> them
> yet).
> 
> I don't mean this in any kind of an insulting way, but do you know how to
> use
> GDB for something like this (eg. are you familiar with add-symbol-file)?
> Did you build the tests with debugging enabled (eg. -g)?
> 
> Again, because there isn't really a ton of info here, I can't just look at
> it
> and say "Ah ha!  The problem is [whatever]"
> 
> --Chris
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 
Chris
I am not entirely familiar with gdb in these circumstances.
I have simply followed the examples give in the eCos documentation and am
trying to understand why things are not working.
This is why there is not a lot of information.
All tests were built using -g
Cannot download a file using mincom it will just sit there

-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22912141.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] arm-eabi-gdb

[Gary Thomas]

grahamlab wrote:
> 
> 
> Chris Zimman wrote:
>> [-- snip --]
>>
>> Quoting reams of previous message is also not required, just enough to
>> sort
>> of continue the conversation.
>>
>>> I did not have mincom running.
>>> I type arm-eabi-gdb -nw
>>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>> at the gdb prompt
>>> set remotebaud 38400
>>> target remote /dev/ttyS0
>>>
>>> After this according to the ecos documentation I should see some
>>> information
>>> about the current loaction and language.
>>>
>>> What I get is
>>> Remote Debugging using /dev/ttyS0
>>> 0x08003b3a in ?? ()
>>>
>>> I dont get any extra information.
>> It looks as though GDB has attached and you are sitting at the current PC.
>>
>>> Is this a problem?
>> No, not necessarily.  You may well be sitting in Redboot also, which GDB
>> knows nothing about in terms of symbols (since you haven't told it about
>> them
>> yet).
>>
>> I don't mean this in any kind of an insulting way, but do you know how to
>> use
>> GDB for something like this (eg. are you familiar with add-symbol-file)?
>> Did you build the tests with debugging enabled (eg. -g)?
>>
>> Again, because there isn't really a ton of info here, I can't just look at
>> it
>> and say "Ah ha!  The problem is [whatever]"
>>
>> --Chris
>>
>> --
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>>
>>
> Chris
> I am not entirely familiar with gdb in these circumstances.
> I have simply followed the examples give in the eCos documentation and am
> trying to understand why things are not working.
> This is why there is not a lot of information.
> All tests were built using -g
> Cannot download a file using mincom it will just sit there

Get this to work first - it tells us that your VirtualBox can't
talk to the board under all circumstances.

Here's how to test it:

  VirtualBox:
    * run minicom to the board
    * get a RedBoot prompt
        RedBoot> lo -r -b %{FREEMEMLO} -m xm
    * at this point, you should see
        CCCC
    * tell minicom to send the file
        ^A-S
          ...

Follow these steps _exactly_ and tell us what happens in each.  Don't
leave anything out - we're not mind readers...



-- 
------------------------------------------------------------
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] arm-eabi-gdb

[Sergei Gavrikov]

grahamlab wrote:
> Sergei Gavrikov-4 wrote:
> > 
> > grahamlab wrote:
> > 
> > [snip]
> > 
> >> I did not have mincom running.
> > 
> > Graham,
> > 
> > here http://ecos.sourceware.org/ml/ecos-discuss/2009-04/msg00041.html
> > you said opposite thing.
> > 
> > It's important to know: can you interact with the board using minicom on
> > guest VM? It's pity that you did not follow those my tips (lsof, fuser,
> > stty) http://ecos.sourceware.org/ml/ecos-discuss/2009-04/msg00067.html
> > 
> > Can you paste the outputs?
> > 
> > Sergei

[snip]

> Sergei
> When I try to send a file using minicom I get the ymodem upload screen - it
> is blank and remains so
> lsof /dev/ttyS* - returns with no output
> fuser /dev/ttyS* - returns with no output

It's okay. I asked about because, sometimes some daemons can hold serial
port(s), like gps daemon, brltty, etc. So, the ports are free.

> output from stty - 
> speed 38400 baud; rows 0; columns 0; line = 0;
> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
> eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt =
> ^R;
> werase = ^W; lnext = ^V; flush = ^O; min = 0; time = 10;
> -parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
> -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
> -ixoff
> -iuclc -ixany -imaxbel -iutf8
> -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
> vt0 ff0
> -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
> -echoprt
> -echoctl -echoke
> 
> Does this give you any clues?
 
At the least, I see `-crtscts` (RTSCTS turned off) and 38400,n,8,1. Do
you prepare that minicom rc file for ownself? Once again:

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

Paste the above on bash prompt. You create .minirc.redboot in your $HOME.

Run minicom as `minicom -o redboot', reset the board, enter that 'load'
command and try upload (^A-s ...). Have you any progress?

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] arm-eabi-gdb

[Sergei Gavrikov]

On Mon, Apr 06, 2009 at 10:21:00AM -0600, Gary Thomas wrote:
> grahamlab wrote:
> > 
> > 
> > Chris Zimman wrote:
> >> [-- snip --]
> >>
> >> Quoting reams of previous message is also not required, just enough to
> >> sort
> >> of continue the conversation.
> >>
> >>> I did not have mincom running.
> >>> I type arm-eabi-gdb -nw
> >>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> >>> at the gdb prompt
> >>> set remotebaud 38400
> >>> target remote /dev/ttyS0
> >>>
> >>> After this according to the ecos documentation I should see some
> >>> information
> >>> about the current loaction and language.
> >>>
> >>> What I get is
> >>> Remote Debugging using /dev/ttyS0
> >>> 0x08003b3a in ?? ()
> >>>
> >>> I dont get any extra information.
> >> It looks as though GDB has attached and you are sitting at the current PC.
> >>
> >>> Is this a problem?
> >> No, not necessarily.  You may well be sitting in Redboot also, which GDB
> >> knows nothing about in terms of symbols (since you haven't told it about
> >> them
> >> yet).
> >>
> >> I don't mean this in any kind of an insulting way, but do you know how to
> >> use
> >> GDB for something like this (eg. are you familiar with add-symbol-file)?
> >> Did you build the tests with debugging enabled (eg. -g)?
> >>
> >> Again, because there isn't really a ton of info here, I can't just look at
> >> it
> >> and say "Ah ha!  The problem is [whatever]"
> >>
> >> --Chris
> >>
> >> --
> >> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> >> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> >>
> >>
> >>
> > Chris
> > I am not entirely familiar with gdb in these circumstances.
> > I have simply followed the examples give in the eCos documentation and am
> > trying to understand why things are not working.
> > This is why there is not a lot of information.
> > All tests were built using -g
> > Cannot download a file using mincom it will just sit there
> 
> Get this to work first - it tells us that your VirtualBox can't
> talk to the board under all circumstances.
> 
> Here's how to test it:
> 
>   VirtualBox:
>     * run minicom to the board
>     * get a RedBoot prompt
>         RedBoot> lo -r -b %{FREEMEMLO} -m xm
>     * at this point, you should see
>         CCCC
>     * tell minicom to send the file
>         ^A-S
>           ...
> 
> Follow these steps _exactly_ and tell us what happens in each.  Don't
> leave anything out - we're not mind readers...
> 

Gary, it seems that I knew something. I just tried:

sudo mv /usr/bin/{,no}sx
sudo mv /usr/bin/{,no}sz
sudo mv /usr/bin/{,no}sb

and minicom tries to send having no senders!

Graham,

Do you have /usr/bin/sz, /usr/bin/sx, /usr/bin/sb ?

Do

$ ls /usr/bin/sx

What you get?

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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> On Mon, Apr 06, 2009 at 10:21:00AM -0600, Gary Thomas wrote:
>> grahamlab wrote:
>> > 
>> > 
>> > Chris Zimman wrote:
>> >> [-- snip --]
>> >>
>> >> Quoting reams of previous message is also not required, just enough to
>> >> sort
>> >> of continue the conversation.
>> >>
>> >>> I did not have mincom running.
>> >>> I type arm-eabi-gdb -nw
>> >>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> >>> at the gdb prompt
>> >>> set remotebaud 38400
>> >>> target remote /dev/ttyS0
>> >>>
>> >>> After this according to the ecos documentation I should see some
>> >>> information
>> >>> about the current loaction and language.
>> >>>
>> >>> What I get is
>> >>> Remote Debugging using /dev/ttyS0
>> >>> 0x08003b3a in ?? ()
>> >>>
>> >>> I dont get any extra information.
>> >> It looks as though GDB has attached and you are sitting at the current
>> PC.
>> >>
>> >>> Is this a problem?
>> >> No, not necessarily.  You may well be sitting in Redboot also, which
>> GDB
>> >> knows nothing about in terms of symbols (since you haven't told it
>> about
>> >> them
>> >> yet).
>> >>
>> >> I don't mean this in any kind of an insulting way, but do you know how
>> to
>> >> use
>> >> GDB for something like this (eg. are you familiar with
>> add-symbol-file)?
>> >> Did you build the tests with debugging enabled (eg. -g)?
>> >>
>> >> Again, because there isn't really a ton of info here, I can't just
>> look at
>> >> it
>> >> and say "Ah ha!  The problem is [whatever]"
>> >>
>> >> --Chris
>> >>
>> >> --
>> >> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> >> and search the list archive:
>> http://ecos.sourceware.org/ml/ecos-discuss
>> >>
>> >>
>> >>
>> > Chris
>> > I am not entirely familiar with gdb in these circumstances.
>> > I have simply followed the examples give in the eCos documentation and
>> am
>> > trying to understand why things are not working.
>> > This is why there is not a lot of information.
>> > All tests were built using -g
>> > Cannot download a file using mincom it will just sit there
>> 
>> Get this to work first - it tells us that your VirtualBox can't
>> talk to the board under all circumstances.
>> 
>> Here's how to test it:
>> 
>>   VirtualBox:
>>     * run minicom to the board
>>     * get a RedBoot prompt
>>         RedBoot> lo -r -b %{FREEMEMLO} -m xm
>>     * at this point, you should see
>>         CCCC
>>     * tell minicom to send the file
>>         ^A-S
>>           ...
>> 
>> Follow these steps _exactly_ and tell us what happens in each.  Don't
>> leave anything out - we're not mind readers...
>> 
> 
> Gary, it seems that I knew something. I just tried:
> 
> sudo mv /usr/bin/{,no}sx
> sudo mv /usr/bin/{,no}sz
> sudo mv /usr/bin/{,no}sb
> 
> and minicom tries to send having no senders!
> 
> Graham,
> 
> Do you have /usr/bin/sz, /usr/bin/sx, /usr/bin/sb ?
> 
> Do
> 
> $ ls /usr/bin/sx
> 
> What you get?
> 
> 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
> 
> 
> 

Hi Sergei

I do dont have /bin/sx which I beleive is what minicom uses
Does this mater?

Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22922668.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] arm-eabi-gdb

[Sergei Gavrikov]

grahamlab wrote:
> Sergei Gavrikov-4 wrote:
> > 
> > On Mon, Apr 06, 2009 at 10:21:00AM -0600, Gary Thomas wrote:
> >> grahamlab wrote:
> >> > 
> >> > 
> >> > Chris Zimman wrote:
> >> >> [-- snip --]
> >> >>
> >> >> Quoting reams of previous message is also not required, just enough to
> >> >> sort
> >> >> of continue the conversation.
> >> >>
> >> >>> I did not have mincom running.
> >> >>> I type arm-eabi-gdb -nw
> >> >>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> >> >>> at the gdb prompt
> >> >>> set remotebaud 38400
> >> >>> target remote /dev/ttyS0
> >> >>>
> >> >>> After this according to the ecos documentation I should see some
> >> >>> information
> >> >>> about the current loaction and language.
> >> >>>
> >> >>> What I get is
> >> >>> Remote Debugging using /dev/ttyS0
> >> >>> 0x08003b3a in ?? ()
> >> >>>
> >> >>> I dont get any extra information.
> >> >> It looks as though GDB has attached and you are sitting at the current
> >> PC.
> >> >>
> >> >>> Is this a problem?
> >> >> No, not necessarily.  You may well be sitting in Redboot also, which
> >> GDB
> >> >> knows nothing about in terms of symbols (since you haven't told it
> >> about
> >> >> them
> >> >> yet).
> >> >>
> >> >> I don't mean this in any kind of an insulting way, but do you know how
> >> to
> >> >> use
> >> >> GDB for something like this (eg. are you familiar with
> >> add-symbol-file)?
> >> >> Did you build the tests with debugging enabled (eg. -g)?
> >> >>
> >> >> Again, because there isn't really a ton of info here, I can't just
> >> look at
> >> >> it
> >> >> and say "Ah ha!  The problem is [whatever]"
> >> >>
> >> >> --Chris
> >> >>
> >> >> --
> >> >> Before posting, please read the FAQ:
> >> http://ecos.sourceware.org/fom/ecos
> >> >> and search the list archive:
> >> http://ecos.sourceware.org/ml/ecos-discuss
> >> >>
> >> >>
> >> >>
> >> > Chris
> >> > I am not entirely familiar with gdb in these circumstances.
> >> > I have simply followed the examples give in the eCos documentation and
> >> am
> >> > trying to understand why things are not working.
> >> > This is why there is not a lot of information.
> >> > All tests were built using -g
> >> > Cannot download a file using mincom it will just sit there
> >> 
> >> Get this to work first - it tells us that your VirtualBox can't
> >> talk to the board under all circumstances.
> >> 
> >> Here's how to test it:
> >> 
> >>   VirtualBox:
> >>     * run minicom to the board
> >>     * get a RedBoot prompt
> >>         RedBoot> lo -r -b %{FREEMEMLO} -m xm
> >>     * at this point, you should see
> >>         CCCC
> >>     * tell minicom to send the file
> >>         ^A-S
> >>           ...
> >> 
> >> Follow these steps _exactly_ and tell us what happens in each.  Don't
> >> leave anything out - we're not mind readers...
> >> 
> > 
> > Gary, it seems that I knew something. I just tried:
> > 
> > sudo mv /usr/bin/{,no}sx
> > sudo mv /usr/bin/{,no}sz
> > sudo mv /usr/bin/{,no}sb
> > 
> > and minicom tries to send having no senders!
> > 
> > Graham,
> > 
> > Do you have /usr/bin/sz, /usr/bin/sx, /usr/bin/sb ?
> > 
> > Do
> > 
> > $ ls /usr/bin/sx
> > 
> > What you get?
> > 
> > Sergei

> Hi Sergei
> 
> I do dont have /bin/sx which I beleive is what minicom uses
> Does this mater?
> 
> Graham

It is a userspace binary (check it under /usr/bin directory, not /bin),
usually the sx, sb, and sz are companion of minicom package and minicom
uses these utility to send data using X/Y/Z modem protocol.

Try

$ which sx

If you have not these senders, you MUST install `lrzsz' package!

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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> On Mon, Apr 06, 2009 at 10:21:00AM -0600, Gary Thomas wrote:
>> grahamlab wrote:
>> > 
>> > 
>> > Chris Zimman wrote:
>> >> [-- snip --]
>> >>
>> >> Quoting reams of previous message is also not required, just enough to
>> >> sort
>> >> of continue the conversation.
>> >>
>> >>> I did not have mincom running.
>> >>> I type arm-eabi-gdb -nw
>> >>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> >>> at the gdb prompt
>> >>> set remotebaud 38400
>> >>> target remote /dev/ttyS0
>> >>>
>> >>> After this according to the ecos documentation I should see some
>> >>> information
>> >>> about the current loaction and language.
>> >>>
>> >>> What I get is
>> >>> Remote Debugging using /dev/ttyS0
>> >>> 0x08003b3a in ?? ()
>> >>>
>> >>> I dont get any extra information.
>> >> It looks as though GDB has attached and you are sitting at the current
>> PC.
>> >>
>> >>> Is this a problem?
>> >> No, not necessarily.  You may well be sitting in Redboot also, which
>> GDB
>> >> knows nothing about in terms of symbols (since you haven't told it
>> about
>> >> them
>> >> yet).
>> >>
>> >> I don't mean this in any kind of an insulting way, but do you know how
>> to
>> >> use
>> >> GDB for something like this (eg. are you familiar with
>> add-symbol-file)?
>> >> Did you build the tests with debugging enabled (eg. -g)?
>> >>
>> >> Again, because there isn't really a ton of info here, I can't just
>> look at
>> >> it
>> >> and say "Ah ha!  The problem is [whatever]"
>> >>
>> >> --Chris
>> >>
>> >> --
>> >> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> >> and search the list archive:
>> http://ecos.sourceware.org/ml/ecos-discuss
>> >>
>> >>
>> >>
>> > Chris
>> > I am not entirely familiar with gdb in these circumstances.
>> > I have simply followed the examples give in the eCos documentation and
>> am
>> > trying to understand why things are not working.
>> > This is why there is not a lot of information.
>> > All tests were built using -g
>> > Cannot download a file using mincom it will just sit there
>> 
>> Get this to work first - it tells us that your VirtualBox can't
>> talk to the board under all circumstances.
>> 
>> Here's how to test it:
>> 
>>   VirtualBox:
>>     * run minicom to the board
>>     * get a RedBoot prompt
>>         RedBoot> lo -r -b %{FREEMEMLO} -m xm
>>     * at this point, you should see
>>         CCCC
>>     * tell minicom to send the file
>>         ^A-S
>>           ...
>> 
>> Follow these steps _exactly_ and tell us what happens in each.  Don't
>> leave anything out - we're not mind readers...
>> 
> 
> Gary, it seems that I knew something. I just tried:
> 
> sudo mv /usr/bin/{,no}sx
> sudo mv /usr/bin/{,no}sz
> sudo mv /usr/bin/{,no}sb
> 
> and minicom tries to send having no senders!
> 
> Graham,
> 
> Do you have /usr/bin/sz, /usr/bin/sx, /usr/bin/sb ?
> 
> Do
> 
> $ ls /usr/bin/sx
> 
> What you get?
> 
> 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
> 
> 
> 

Hi All
I have installed sx etc and am now able to download a file using minicom -
at last some progress!!
However, I am still unable to use gdb - I'll keep trying but any advice
would be apprecaited

Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22922691.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] arm-eabi-gdb

[Sergei Gavrikov]

grahamlab wrote:
> Sergei Gavrikov wrote:
> > 
> > On Mon, Apr 06, 2009 at 10:21:00AM -0600, Gary Thomas wrote:
> >> grahamlab wrote:
> >> > 
> >> > 
> >> > Chris Zimman wrote:
> >> >> [-- snip --]
> >> >>
> >> >> Quoting reams of previous message is also not required, just enough to
> >> >> sort
> >> >> of continue the conversation.
> >> >>
> >> >>> I did not have mincom running.
> >> >>> I type arm-eabi-gdb -nw
> >> >>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> >> >>> at the gdb prompt
> >> >>> set remotebaud 38400
> >> >>> target remote /dev/ttyS0
> >> >>>
> >> >>> After this according to the ecos documentation I should see some
> >> >>> information
> >> >>> about the current loaction and language.
> >> >>>
> >> >>> What I get is
> >> >>> Remote Debugging using /dev/ttyS0
> >> >>> 0x08003b3a in ?? ()
> >> >>>
> >> >>> I dont get any extra information.
> >> >> It looks as though GDB has attached and you are sitting at the current
> >> PC.
> >> >>
> >> >>> Is this a problem?
> >> >> No, not necessarily.  You may well be sitting in Redboot also, which
> >> GDB
> >> >> knows nothing about in terms of symbols (since you haven't told it
> >> about
> >> >> them
> >> >> yet).
> >> >>
> >> >> I don't mean this in any kind of an insulting way, but do you know how
> >> to
> >> >> use
> >> >> GDB for something like this (eg. are you familiar with
> >> add-symbol-file)?
> >> >> Did you build the tests with debugging enabled (eg. -g)?
> >> >>
> >> >> Again, because there isn't really a ton of info here, I can't just
> >> look at
> >> >> it
> >> >> and say "Ah ha!  The problem is [whatever]"
> >> >>
> >> >> --Chris
> >> >>
> >> >> --
> >> >> Before posting, please read the FAQ:
> >> http://ecos.sourceware.org/fom/ecos
> >> >> and search the list archive:
> >> http://ecos.sourceware.org/ml/ecos-discuss
> >> >>
> >> >>
> >> >>
> >> > Chris
> >> > I am not entirely familiar with gdb in these circumstances.
> >> > I have simply followed the examples give in the eCos documentation and
> >> am
> >> > trying to understand why things are not working.
> >> > This is why there is not a lot of information.
> >> > All tests were built using -g
> >> > Cannot download a file using mincom it will just sit there
> >> 
> >> Get this to work first - it tells us that your VirtualBox can't
> >> talk to the board under all circumstances.
> >> 
> >> Here's how to test it:
> >> 
> >>   VirtualBox:
> >>     * run minicom to the board
> >>     * get a RedBoot prompt
> >>         RedBoot> lo -r -b %{FREEMEMLO} -m xm
> >>     * at this point, you should see
> >>         CCCC
> >>     * tell minicom to send the file
> >>         ^A-S
> >>           ...
> >> 
> >> Follow these steps _exactly_ and tell us what happens in each.  Don't
> >> leave anything out - we're not mind readers...
> >> 
> > 
> > Gary, it seems that I knew something. I just tried:
> > 
> > sudo mv /usr/bin/{,no}sx
> > sudo mv /usr/bin/{,no}sz
> > sudo mv /usr/bin/{,no}sb
> > 
> > and minicom tries to send having no senders!
> > 
> > Graham,
> > 
> > Do you have /usr/bin/sz, /usr/bin/sx, /usr/bin/sb ?
> > 
> > Do
> > 
> > $ ls /usr/bin/sx
> > 
> > What you get?
> > 
> > Sergei
> 
> Hi All
> I have installed sx etc and am now able to download a file using minicom -
> at last some progress!!
> However, I am still unable to use gdb - I'll keep trying but any advice
> would be apprecaited
> 
> Graham

Graham, try to load random images as I did point you in my first letter
with a checksum control: 10K, 20K, etc. The checksums MUST be equals.
How many RAM can you use?  Look at the RedBoot's startup screen. Try to
load random data so big as you can and verify the checksum(s).

If all will going smoothly, i.e.  xmodem's downloads, then try type '$'
in minicom. What's happined on the '$' press?

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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> grahamlab wrote:
>> Sergei Gavrikov wrote:
>> > 
>> > On Mon, Apr 06, 2009 at 10:21:00AM -0600, Gary Thomas wrote:
>> >> grahamlab wrote:
>> >> > 
>> >> > 
>> >> > Chris Zimman wrote:
>> >> >> [-- snip --]
>> >> >>
>> >> >> Quoting reams of previous message is also not required, just enough
>> to
>> >> >> sort
>> >> >> of continue the conversation.
>> >> >>
>> >> >>> I did not have mincom running.
>> >> >>> I type arm-eabi-gdb -nw
>> >> >>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> >> >>> at the gdb prompt
>> >> >>> set remotebaud 38400
>> >> >>> target remote /dev/ttyS0
>> >> >>>
>> >> >>> After this according to the ecos documentation I should see some
>> >> >>> information
>> >> >>> about the current loaction and language.
>> >> >>>
>> >> >>> What I get is
>> >> >>> Remote Debugging using /dev/ttyS0
>> >> >>> 0x08003b3a in ?? ()
>> >> >>>
>> >> >>> I dont get any extra information.
>> >> >> It looks as though GDB has attached and you are sitting at the
>> current
>> >> PC.
>> >> >>
>> >> >>> Is this a problem?
>> >> >> No, not necessarily.  You may well be sitting in Redboot also,
>> which
>> >> GDB
>> >> >> knows nothing about in terms of symbols (since you haven't told it
>> >> about
>> >> >> them
>> >> >> yet).
>> >> >>
>> >> >> I don't mean this in any kind of an insulting way, but do you know
>> how
>> >> to
>> >> >> use
>> >> >> GDB for something like this (eg. are you familiar with
>> >> add-symbol-file)?
>> >> >> Did you build the tests with debugging enabled (eg. -g)?
>> >> >>
>> >> >> Again, because there isn't really a ton of info here, I can't just
>> >> look at
>> >> >> it
>> >> >> and say "Ah ha!  The problem is [whatever]"
>> >> >>
>> >> >> --Chris
>> >> >>
>> >> >> --
>> >> >> Before posting, please read the FAQ:
>> >> http://ecos.sourceware.org/fom/ecos
>> >> >> and search the list archive:
>> >> http://ecos.sourceware.org/ml/ecos-discuss
>> >> >>
>> >> >>
>> >> >>
>> >> > Chris
>> >> > I am not entirely familiar with gdb in these circumstances.
>> >> > I have simply followed the examples give in the eCos documentation
>> and
>> >> am
>> >> > trying to understand why things are not working.
>> >> > This is why there is not a lot of information.
>> >> > All tests were built using -g
>> >> > Cannot download a file using mincom it will just sit there
>> >> 
>> >> Get this to work first - it tells us that your VirtualBox can't
>> >> talk to the board under all circumstances.
>> >> 
>> >> Here's how to test it:
>> >> 
>> >>   VirtualBox:
>> >>     * run minicom to the board
>> >>     * get a RedBoot prompt
>> >>         RedBoot> lo -r -b %{FREEMEMLO} -m xm
>> >>     * at this point, you should see
>> >>         CCCC
>> >>     * tell minicom to send the file
>> >>         ^A-S
>> >>           ...
>> >> 
>> >> Follow these steps _exactly_ and tell us what happens in each.  Don't
>> >> leave anything out - we're not mind readers...
>> >> 
>> > 
>> > Gary, it seems that I knew something. I just tried:
>> > 
>> > sudo mv /usr/bin/{,no}sx
>> > sudo mv /usr/bin/{,no}sz
>> > sudo mv /usr/bin/{,no}sb
>> > 
>> > and minicom tries to send having no senders!
>> > 
>> > Graham,
>> > 
>> > Do you have /usr/bin/sz, /usr/bin/sx, /usr/bin/sb ?
>> > 
>> > Do
>> > 
>> > $ ls /usr/bin/sx
>> > 
>> > What you get?
>> > 
>> > Sergei
>> 
>> Hi All
>> I have installed sx etc and am now able to download a file using minicom
>> -
>> at last some progress!!
>> However, I am still unable to use gdb - I'll keep trying but any advice
>> would be apprecaited
>> 
>> Graham
> 
> Graham, try to load random images as I did point you in my first letter
> with a checksum control: 10K, 20K, etc. The checksums MUST be equals.
> How many RAM can you use?  Look at the RedBoot's startup screen. Try to
> load random data so big as you can and verify the checksum(s).
> 
> If all will going smoothly, i.e.  xmodem's downloads, then try type '$'
> in minicom. What's happined on the '$' press?
> 
> 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
> 
> 
> 

Hi Sergei

I have tried downloading various random images as suggested and all download
successfully
Typing the $ seems to lock the display - is this what you expected?

Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22925189.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] arm-eabi-gdb

[Sergei Gavrikov]

grahamlab wrote:

[cut the wars with minicom]

> Hi Sergei
> 
> I have tried downloading various random images as suggested and all
> download successfully Typing the $ seems to lock the display - is this
> what you expected?
> 
> Graham

Yep. It seems for me, your RedBoot supports GDB.

Now (you work with some built elf binary), fulfil

i) invoke

$ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0

<copy and paste an output just the below for us>



ii) invoke

$ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0

<copy and paste an output the below for us>



iii)

We need to look on a startup screen your RedBoot

<copy and paste a starup-screen the below>


Note: I want to know a bit more about your RAM location and its size.
RedBoot talks about.


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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> grahamlab wrote:
> 
> [cut the wars with minicom]
> 
>> Hi Sergei
>> 
>> I have tried downloading various random images as suggested and all
>> download successfully Typing the $ seems to lock the display - is this
>> what you expected?
>> 
>> Graham
> 
> Yep. It seems for me, your RedBoot supports GDB.
> 
> Now (you work with some built elf binary), fulfil
> 
> i) invoke
> 
> $ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> 
> <copy and paste an output just the below for us>
> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0: ELF 32-bit LSB
> executable, ARM, version 1 (SYSV), statically linked, not stripped
> 
> 
> 
> ii) invoke
> 
> $ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> 
> <copy and paste an output the below for us>
> 
> section              size         addr
> .debug_aranges     0x1440          0x0
> .debug_pubnames    0x377d          0x0
> .debug_info       0x4de43          0x0
> .debug_abbrev      0xab3f          0x0
> .debug_line        0xad87          0x0
> .debug_frame       0x31f8          0x0
> .debug_str         0x8482          0x0
> .debug_loc         0xd8c1          0x0
> .rom_vectors          0x8   0x68008000
> .ARM.exidx           0x10   0x68008008
> .text              0x4330   0x68008018
> .rodata             0x38c   0x6800c348
> .eh_frame             0x8   0x6800c6d8
> .data               0x180   0x6800c6e0
> .bss               0x32f8   0x6800c860
> .ARM.attributes      0x2f          0x0
> .debug_ranges      0x44c0          0x0
> .comment            0x8f7          0x0
> Total             0x8db3b
> 
> 
> iii)
> 
> We need to look on a startup screen your RedBoot
> 
> <copy and paste a starup-screen the below>
> 
> RedBoot(tm) bootstrap and debug environment [ROM]           
> Non-certified release, version v3_0 - built 09:17:39, Apr  7 2009
>                                                             
> Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
> Free Software Foundation, Inc.                              
> RedBoot is free software, covered by the eCos license, derived from the
> GNU General Public License. You are welcome to change it and/or distribute
> copies of it under certain conditions. Under the license terms, RedBoot's
> source code and full license terms must have been made available to you.
> Redboot comes with ABSOLUTELY NO WARRANTY.                  
> 
> Platform: ST STM3210E EVAL (Cortex-M3) 
> RAM: 0x68000000-0x68100000 [0x68003188-0x68100000 available]
>      0x20000000-0x2000f000 [0x20000000-0x2000f000 available]                    
> RedBoot> 
> 
> Note: I want to know a bit more about your RAM location and its size.
> RedBoot talks about.
> 
> 
> 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/arm-eabi-gdb-tp22908205p22925798.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] arm-eabi-gdb

[grahamlab]

grahamlab wrote:
> 
> 
> Sergei Gavrikov-4 wrote:
>> 
>> grahamlab wrote:
>> 
>> [cut the wars with minicom]
>> 
>>> Hi Sergei
>>> 
>>> I have tried downloading various random images as suggested and all
>>> download successfully Typing the $ seems to lock the display - is this
>>> what you expected?
>>> 
>>> Graham
>> 
>> Yep. It seems for me, your RedBoot supports GDB.
>> 
>> Now (you work with some built elf binary), fulfil
>> 
>> i) invoke
>> 
>> $ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> 
>> <copy and paste an output just the below for us>
>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0: ELF 32-bit LSB
>> executable, ARM, version 1 (SYSV), statically linked, not stripped
>> 
>> 
>> 
>> ii) invoke
>> 
>> $ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> 
>> <copy and paste an output the below for us>
>> 
>> section              size         addr
>> .debug_aranges     0x1440          0x0
>> .debug_pubnames    0x377d          0x0
>> .debug_info       0x4de43          0x0
>> .debug_abbrev      0xab3f          0x0
>> .debug_line        0xad87          0x0
>> .debug_frame       0x31f8          0x0
>> .debug_str         0x8482          0x0
>> .debug_loc         0xd8c1          0x0
>> .rom_vectors          0x8   0x68008000
>> .ARM.exidx           0x10   0x68008008
>> .text              0x4330   0x68008018
>> .rodata             0x38c   0x6800c348
>> .eh_frame             0x8   0x6800c6d8
>> .data               0x180   0x6800c6e0
>> .bss               0x32f8   0x6800c860
>> .ARM.attributes      0x2f          0x0
>> .debug_ranges      0x44c0          0x0
>> .comment            0x8f7          0x0
>> Total             0x8db3b
>> 
>> 
>> iii)
>> 
>> We need to look on a startup screen your RedBoot
>> 
>> <copy and paste a starup-screen the below>
>> 
>> RedBoot(tm) bootstrap and debug environment [ROM]           
>> Non-certified release, version v3_0 - built 09:17:39, Apr  7 2009
>>                                                             
>> Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
>> Free Software Foundation, Inc.                              
>> RedBoot is free software, covered by the eCos license, derived from the
>> GNU General Public License. You are welcome to change it and/or
>> distribute
>> copies of it under certain conditions. Under the license terms, RedBoot's
>> source code and full license terms must have been made available to you.
>> Redboot comes with ABSOLUTELY NO WARRANTY.                  
>> 
>> Platform: ST STM3210E EVAL (Cortex-M3) 
>> RAM: 0x68000000-0x68100000 [0x68003188-0x68100000 available]
>>      0x20000000-0x2000f000 [0x20000000-0x2000f000 available]                    
>> RedBoot> 
>> 
>> Note: I want to know a bit more about your RAM location and its size.
>> RedBoot talks about.
>> 
>> 
>> 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
>> 
>> 
>> 
> 
> 

Hello again
I downloaded the bin_sem0 program via minicom and ran it successfully - I
just cant use gdb from the command line which I will need. Any more clues?
Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22926372.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] arm-eabi-gdb

[Sergei Gavrikov]

Graham wrote:
> Sergei Gavrikov wrote:
> > 
> > grahamlab wrote:
> > 
> > [cut the wars with minicom]
> > 
> >> Hi Sergei
> >> 
> >> I have tried downloading various random images as suggested and all
> >> download successfully Typing the $ seems to lock the display - is this
> >> what you expected?
> >> 
> >> Graham
> > 
> > Yep. It seems for me, your RedBoot supports GDB.
> > 
> > Now (you work with some built elf binary), fulfil
> > 
> > i) invoke
> > 
> > $ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> > 
> > <copy and paste an output just the below for us>
> > DevBoard_install/tests/kernel/v3_0/tests/bin_sem0: ELF 32-bit LSB
> > executable, ARM, version 1 (SYSV), statically linked, not stripped

Excellent! It's not stripped elf.

> > ii) invoke
> > 
> > $ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
> > 
> > <copy and paste an output the below for us>
> > 
> > section              size         addr
> > .debug_aranges     0x1440          0x0
> > .debug_pubnames    0x377d          0x0
> > .debug_info       0x4de43          0x0
> > .debug_abbrev      0xab3f          0x0
> > .debug_line        0xad87          0x0
> > .debug_frame       0x31f8          0x0
> > .debug_str         0x8482          0x0
> > .debug_loc         0xd8c1          0x0
> > .rom_vectors          0x8   0x68008000
> > .ARM.exidx           0x10   0x68008008
> > .text              0x4330   0x68008018
> > .rodata             0x38c   0x6800c348
> > .eh_frame             0x8   0x6800c6d8
> > .data               0x180   0x6800c6e0
> > .bss               0x32f8   0x6800c860
> > .ARM.attributes      0x2f          0x0
> > .debug_ranges      0x44c0          0x0
> > .comment            0x8f7          0x0
> > Total             0x8db3b

I see nothinig illegal the above: .text, .*data, .bss do seat silent in
the RAM its total size about 40K.

> > iii)
> > 
> > We need to look on a startup screen your RedBoot
> > 
> > <copy and paste a starup-screen the below>
> > 
> > RedBoot(tm) bootstrap and debug environment [ROM]           
> > Non-certified release, version v3_0 - built 09:17:39, Apr  7 2009
> >                                                             
> > Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
> > Free Software Foundation, Inc.                              
> > RedBoot is free software, covered by the eCos license, derived from the
> > GNU General Public License. You are welcome to change it and/or distribute
> > copies of it under certain conditions. Under the license terms, RedBoot's
> > source code and full license terms must have been made available to you.
> > Redboot comes with ABSOLUTELY NO WARRANTY.                  
> > 
> > Platform: ST STM3210E EVAL (Cortex-M3) 
> > RAM: 0x68000000-0x68100000 [0x68003188-0x68100000 available]
> >      0x20000000-0x2000f000 [0x20000000-0x2000f000 available]                    
What's a nice board! IMHO, it's very suitable for eCos. You have ~1M of
a volatile memory.

> > Note: I want to know a bit more about your RAM location and its size.
> > RedBoot talks about.
> > 
> > 
> > Sergei

Graham, let's resume what you've got:

1) You have arm-eabi GNU toolchain with it you are able to build eCos
   applications.

2) You have a nice bootstrap environment with GDB support -- RedBoot.

3) You are able using X-modem protocol and minicom to upload the images
   into RAM. IMHO, if you can to load a test image in a few hundreds of
   Kb into the RAM, your GDB must do it too.

Before to start debug GDB protocol, dance with packet's sizes, etc. My
the first guess: you misconfigured eCos build. I do not know how you
configured eCos build. I do not know what you check/uncheck using eCos
`configtool'.

So, can you reproduce the below just in Linux bash?

i. Build a minimal eCos stuff as

echo $ECOS_REPOSITORY >> report.txt
echo $PATH >> report.txt
cd /tmp
mkdir lab1
cd lab1
ecosconfig new stm3210e minimal
ecosconfig tree
make -s
make -s -C hal/common/current tests
ls -R install/tests >> report.txt

Note: attach the report.txt then.


ii. Leave minicom if it runs!

lsof /dev/ttyS0 ;# you must see no output


iii. Reset the board and invoke arm-eabi-gdb as

arm-eabi-gdb -q -nx install/tests/hal/common/current/tests/basic


iv. GDB

Now on GDB prompt type a line by a line (see the below)

(gdb) set logging on
(gdb) set remotebaud 38400
(gdb) target remote /dev/ttyS0

Here you can to see that board connected, if gdb wait here, reset the
board and try `target' command again.

(gdb) load

I very hope that will be done. If it will, continue:

(gdb) b cyg_test_init
(gdb) b cyg_test_exit
(gdb) c
(gdb) c


Please, repeat the above lab1 exactly! And the report about the results:
attach report.txt, gdb.txt. The files should be in that /tmp/lab1
directory.

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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> Graham wrote:
>> Sergei Gavrikov wrote:
>> > 
>> > grahamlab wrote:
>> > 
>> > [cut the wars with minicom]
>> > 
>> >> Hi Sergei
>> >> 
>> >> I have tried downloading various random images as suggested and all
>> >> download successfully Typing the $ seems to lock the display - is this
>> >> what you expected?
>> >> 
>> >> Graham
>> > 
>> > Yep. It seems for me, your RedBoot supports GDB.
>> > 
>> > Now (you work with some built elf binary), fulfil
>> > 
>> > i) invoke
>> > 
>> > $ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> > 
>> > <copy and paste an output just the below for us>
>> > DevBoard_install/tests/kernel/v3_0/tests/bin_sem0: ELF 32-bit LSB
>> > executable, ARM, version 1 (SYSV), statically linked, not stripped
> 
> Excellent! It's not stripped elf.
> 
>> > ii) invoke
>> > 
>> > $ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>> > 
>> > <copy and paste an output the below for us>
>> > 
>> > section              size         addr
>> > .debug_aranges     0x1440          0x0
>> > .debug_pubnames    0x377d          0x0
>> > .debug_info       0x4de43          0x0
>> > .debug_abbrev      0xab3f          0x0
>> > .debug_line        0xad87          0x0
>> > .debug_frame       0x31f8          0x0
>> > .debug_str         0x8482          0x0
>> > .debug_loc         0xd8c1          0x0
>> > .rom_vectors          0x8   0x68008000
>> > .ARM.exidx           0x10   0x68008008
>> > .text              0x4330   0x68008018
>> > .rodata             0x38c   0x6800c348
>> > .eh_frame             0x8   0x6800c6d8
>> > .data               0x180   0x6800c6e0
>> > .bss               0x32f8   0x6800c860
>> > .ARM.attributes      0x2f          0x0
>> > .debug_ranges      0x44c0          0x0
>> > .comment            0x8f7          0x0
>> > Total             0x8db3b
> 
> I see nothinig illegal the above: .text, .*data, .bss do seat silent in
> the RAM its total size about 40K.
> 
>> > iii)
>> > 
>> > We need to look on a startup screen your RedBoot
>> > 
>> > <copy and paste a starup-screen the below>
>> > 
>> > RedBoot(tm) bootstrap and debug environment [ROM]           
>> > Non-certified release, version v3_0 - built 09:17:39, Apr  7 2009
>> >                                                             
>> > Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
>> 2009
>> > Free Software Foundation, Inc.                              
>> > RedBoot is free software, covered by the eCos license, derived from the
>> > GNU General Public License. You are welcome to change it and/or
>> distribute
>> > copies of it under certain conditions. Under the license terms,
>> RedBoot's
>> > source code and full license terms must have been made available to
>> you.
>> > Redboot comes with ABSOLUTELY NO WARRANTY.                  
>> > 
>> > Platform: ST STM3210E EVAL (Cortex-M3) 
>> > RAM: 0x68000000-0x68100000 [0x68003188-0x68100000 available]
>> >      0x20000000-0x2000f000 [0x20000000-0x2000f000 available]                    
> What's a nice board! IMHO, it's very suitable for eCos. You have ~1M of
> a volatile memory.
> 
>> > Note: I want to know a bit more about your RAM location and its size.
>> > RedBoot talks about.
>> > 
>> > 
>> > Sergei
> 
> Graham, let's resume what you've got:
> 
> 1) You have arm-eabi GNU toolchain with it you are able to build eCos
>    applications.
> 
> 2) You have a nice bootstrap environment with GDB support -- RedBoot.
> 
> 3) You are able using X-modem protocol and minicom to upload the images
>    into RAM. IMHO, if you can to load a test image in a few hundreds of
>    Kb into the RAM, your GDB must do it too.
> 
> Before to start debug GDB protocol, dance with packet's sizes, etc. My
> the first guess: you misconfigured eCos build. I do not know how you
> configured eCos build. I do not know what you check/uncheck using eCos
> `configtool'.
> 
> So, can you reproduce the below just in Linux bash?
> 
> i. Build a minimal eCos stuff as
> 
> echo $ECOS_REPOSITORY >> report.txt
> echo $PATH >> report.txt
> cd /tmp
> mkdir lab1
> cd lab1
> ecosconfig new stm3210e minimal
> ecosconfig tree
> make -s
> make -s -C hal/common/current tests
> ls -R install/tests >> report.txt
> 
> Note: attach the report.txt then.
> 
> 
> ii. Leave minicom if it runs!
> 
> lsof /dev/ttyS0 ;# you must see no output
> 
> 
> iii. Reset the board and invoke arm-eabi-gdb as
> 
> arm-eabi-gdb -q -nx install/tests/hal/common/current/tests/basic
> 
> 
> iv. GDB
> 
> Now on GDB prompt type a line by a line (see the below)
> 
> (gdb) set logging on
> (gdb) set remotebaud 38400
> (gdb) target remote /dev/ttyS0
> 
> Here you can to see that board connected, if gdb wait here, reset the
> board and try `target' command again.
> 
> (gdb) load
> 
> I very hope that will be done. If it will, continue:
> 
> (gdb) b cyg_test_init
> (gdb) b cyg_test_exit
> (gdb) c
> (gdb) c
> 
> 
> Please, repeat the above lab1 exactly! And the report about the results:
> attach report.txt, gdb.txt. The files should be in that /tmp/lab1
> directory.
> 
> 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
> 
> 
> 

Hello Sergei
This worked - I manged to run gdb
So what was wrong with my first application? I did not change any settings
in the config tool, just used a default configuration. You will see that I
am still getting 'Ignoring packet error' and it seems to take quite a while
to download.
THnaks for you help so far  - what could be wrong with my original
configuration?

Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22927519.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] arm-eabi-gdb

[Sergei Gavrikov]

Graham wrote:

[snip]

> This worked - I manged to run gdb
> So what was wrong with my first application? I did not change any settings
> in the config tool, just used a default configuration. You will see that I
> am still getting 'Ignoring packet error' and it seems to take quite a while
> to download.
> THnaks for you help so far  - what could be wrong with my original
> configuration?
> 
> Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
> http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 

Hm, I am looking at gdb.txt... I would say, It most likes not work than
works: 31 bytes/sec and a lot of re-transmissions. I wonder, How many
re-transmissions you have when you load thist `basic' using x-modem?

The second Q: Can you ping from Linux guest your windows box? I would
suggest to try serial-to-tcp bridge. But you can still play with GDB
packet's sizes

(gdb) set remote memory-write-packet-size 64
(gdb) set remote memory-write-packet-size fixed
(gdb) set remote memory-write-packet-size 64
(gdb) set remote memory-write-packet-size fixed


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] arm-eabi-gdb

[grahamlab]

grahamlab wrote:
> 
> 
> Sergei Gavrikov-4 wrote:
>> 
>> Graham wrote:
>>> Sergei Gavrikov wrote:
>>> > 
>>> > grahamlab wrote:
>>> > 
>>> > [cut the wars with minicom]
>>> > 
>>> >> Hi Sergei
>>> >> 
>>> >> I have tried downloading various random images as suggested and all
>>> >> download successfully Typing the $ seems to lock the display - is
>>> this
>>> >> what you expected?
>>> >> 
>>> >> Graham
>>> > 
>>> > Yep. It seems for me, your RedBoot supports GDB.
>>> > 
>>> > Now (you work with some built elf binary), fulfil
>>> > 
>>> > i) invoke
>>> > 
>>> > $ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>> > 
>>> > <copy and paste an output just the below for us>
>>> > DevBoard_install/tests/kernel/v3_0/tests/bin_sem0: ELF 32-bit LSB
>>> > executable, ARM, version 1 (SYSV), statically linked, not stripped
>> 
>> Excellent! It's not stripped elf.
>> 
>>> > ii) invoke
>>> > 
>>> > $ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>> > 
>>> > <copy and paste an output the below for us>
>>> > 
>>> > section              size         addr
>>> > .debug_aranges     0x1440          0x0
>>> > .debug_pubnames    0x377d          0x0
>>> > .debug_info       0x4de43          0x0
>>> > .debug_abbrev      0xab3f          0x0
>>> > .debug_line        0xad87          0x0
>>> > .debug_frame       0x31f8          0x0
>>> > .debug_str         0x8482          0x0
>>> > .debug_loc         0xd8c1          0x0
>>> > .rom_vectors          0x8   0x68008000
>>> > .ARM.exidx           0x10   0x68008008
>>> > .text              0x4330   0x68008018
>>> > .rodata             0x38c   0x6800c348
>>> > .eh_frame             0x8   0x6800c6d8
>>> > .data               0x180   0x6800c6e0
>>> > .bss               0x32f8   0x6800c860
>>> > .ARM.attributes      0x2f          0x0
>>> > .debug_ranges      0x44c0          0x0
>>> > .comment            0x8f7          0x0
>>> > Total             0x8db3b
>> 
>> I see nothinig illegal the above: .text, .*data, .bss do seat silent in
>> the RAM its total size about 40K.
>> 
>>> > iii)
>>> > 
>>> > We need to look on a startup screen your RedBoot
>>> > 
>>> > <copy and paste a starup-screen the below>
>>> > 
>>> > RedBoot(tm) bootstrap and debug environment [ROM]           
>>> > Non-certified release, version v3_0 - built 09:17:39, Apr  7 2009
>>> >                                                             
>>> > Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
>>> 2009
>>> > Free Software Foundation, Inc.                              
>>> > RedBoot is free software, covered by the eCos license, derived from
>>> the
>>> > GNU General Public License. You are welcome to change it and/or
>>> distribute
>>> > copies of it under certain conditions. Under the license terms,
>>> RedBoot's
>>> > source code and full license terms must have been made available to
>>> you.
>>> > Redboot comes with ABSOLUTELY NO WARRANTY.                  
>>> > 
>>> > Platform: ST STM3210E EVAL (Cortex-M3) 
>>> > RAM: 0x68000000-0x68100000 [0x68003188-0x68100000 available]
>>> >      0x20000000-0x2000f000 [0x20000000-0x2000f000 available]                    
>> What's a nice board! IMHO, it's very suitable for eCos. You have ~1M of
>> a volatile memory.
>> 
>>> > Note: I want to know a bit more about your RAM location and its size.
>>> > RedBoot talks about.
>>> > 
>>> > 
>>> > Sergei
>> 
>> Graham, let's resume what you've got:
>> 
>> 1) You have arm-eabi GNU toolchain with it you are able to build eCos
>>    applications.
>> 
>> 2) You have a nice bootstrap environment with GDB support -- RedBoot.
>> 
>> 3) You are able using X-modem protocol and minicom to upload the images
>>    into RAM. IMHO, if you can to load a test image in a few hundreds of
>>    Kb into the RAM, your GDB must do it too.
>> 
>> Before to start debug GDB protocol, dance with packet's sizes, etc. My
>> the first guess: you misconfigured eCos build. I do not know how you
>> configured eCos build. I do not know what you check/uncheck using eCos
>> `configtool'.
>> 
>> So, can you reproduce the below just in Linux bash?
>> 
>> i. Build a minimal eCos stuff as
>> 
>> echo $ECOS_REPOSITORY >> report.txt
>> echo $PATH >> report.txt
>> cd /tmp
>> mkdir lab1
>> cd lab1
>> ecosconfig new stm3210e minimal
>> ecosconfig tree
>> make -s
>> make -s -C hal/common/current tests
>> ls -R install/tests >> report.txt
>> 
>> Note: attach the report.txt then.
>> 
>> 
>> ii. Leave minicom if it runs!
>> 
>> lsof /dev/ttyS0 ;# you must see no output
>> 
>> 
>> iii. Reset the board and invoke arm-eabi-gdb as
>> 
>> arm-eabi-gdb -q -nx install/tests/hal/common/current/tests/basic
>> 
>> 
>> iv. GDB
>> 
>> Now on GDB prompt type a line by a line (see the below)
>> 
>> (gdb) set logging on
>> (gdb) set remotebaud 38400
>> (gdb) target remote /dev/ttyS0
>> 
>> Here you can to see that board connected, if gdb wait here, reset the
>> board and try `target' command again.
>> 
>> (gdb) load
>> 
>> I very hope that will be done. If it will, continue:
>> 
>> (gdb) b cyg_test_init
>> (gdb) b cyg_test_exit
>> (gdb) c
>> (gdb) c
>> 
>> 
>> Please, repeat the above lab1 exactly! And the report about the results:
>> attach report.txt, gdb.txt. The files should be in that /tmp/lab1
>> directory.
>> 
>> 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
>> 
>> 
>> 
> 
> Hello Sergei
> This worked - I manged to run gdb
> So what was wrong with my first application? I did not change any settings
> in the config tool, just used a default configuration. You will see that I
> am still getting 'Ignoring packet error' and it seems to take quite a
> while to download.
> THnaks for you help so far  - what could be wrong with my original
> configuration?
> 
> Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
> http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
> 
Unfortunately this is not repeatable - just tried it again and it fails to
download!
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22927971.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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> Graham wrote:
> 
> [snip]
> 
>> This worked - I manged to run gdb
>> So what was wrong with my first application? I did not change any
>> settings
>> in the config tool, just used a default configuration. You will see that
>> I
>> am still getting 'Ignoring packet error' and it seems to take quite a
>> while
>> to download.
>> THnaks for you help so far  - what could be wrong with my original
>> configuration?
>> 
>> Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
>> http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
> 
> Hm, I am looking at gdb.txt... I would say, It most likes not work than
> works: 31 bytes/sec and a lot of re-transmissions. I wonder, How many
> re-transmissions you have when you load thist `basic' using x-modem?
> 
> The second Q: Can you ping from Linux guest your windows box? I would
> suggest to try serial-to-tcp bridge. But you can still play with GDB
> packet's sizes
> 
> (gdb) set remote memory-write-packet-size 64
> (gdb) set remote memory-write-packet-size fixed
> (gdb) set remote memory-write-packet-size 64
> (gdb) set remote memory-write-packet-size fixed
> 
> 
> 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
> 
> 
> 
Hello Sergei
Forgive my ignorance but I dont know how to ping my windows box
How do I set up a serial-to-tcp bridge?

Graham
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22928045.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] arm-eabi-gdb

[Sergei Gavrikov]

On Tue, Apr 07, 2009 at 03:25:06PM +0300, Sergei Gavrikov wrote:
> Graham wrote:
> 
> [snip]
> 
> > This worked - I manged to run gdb
> > So what was wrong with my first application? I did not change any settings
> > in the config tool, just used a default configuration. You will see that I
> > am still getting 'Ignoring packet error' and it seems to take quite a while
> > to download.
> > THnaks for you help so far  - what could be wrong with my original
> > configuration?
> > 
> > Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
> > http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
> 
> Hm, I am looking at gdb.txt... I would say, It most likes not work than
> works: 31 bytes/sec and a lot of re-transmissions. I wonder, How many
> re-transmissions you have when you load thist `basic' using x-modem?
> 
> The second Q: Can you ping from Linux guest your windows box? I would
> suggest to try serial-to-tcp bridge. But you can still play with GDB
> packet's sizes
> 
> (gdb) set remote memory-write-packet-size 64
> (gdb) set remote memory-write-packet-size fixed
> (gdb) set remote memory-write-packet-size 64
> (gdb) set remote memory-write-packet-size fixed

Last two lines are copy and paste typos

 (gdb) set remote memory-read-packet-size 64
 (gdb) set remote memory-read-packet-size fixed

64 -- just a guess, try the different sizes. Report, if it helped.

-- 
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] arm-eabi-gdb

[Gary Thomas]

grahamlab wrote:
> 
> 
> grahamlab wrote:
>>
>> Sergei Gavrikov-4 wrote:
>>> Graham wrote:
>>>> Sergei Gavrikov wrote:
>>>>> grahamlab wrote:
>>>>>
>>>>> [cut the wars with minicom]
>>>>>
>>>>>> Hi Sergei
>>>>>>
>>>>>> I have tried downloading various random images as suggested and all
>>>>>> download successfully Typing the $ seems to lock the display - is
>>>> this
>>>>>> what you expected?
>>>>>>
>>>>>> Graham
>>>>> Yep. It seems for me, your RedBoot supports GDB.
>>>>>
>>>>> Now (you work with some built elf binary), fulfil
>>>>>
>>>>> i) invoke
>>>>>
>>>>> $ file DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>>>>
>>>>> <copy and paste an output just the below for us>
>>>>> DevBoard_install/tests/kernel/v3_0/tests/bin_sem0: ELF 32-bit LSB
>>>>> executable, ARM, version 1 (SYSV), statically linked, not stripped
>>> Excellent! It's not stripped elf.
>>>
>>>>> ii) invoke
>>>>>
>>>>> $ arm-eabi-size -Ax DevBoard_install/tests/kernel/v3_0/tests/bin_sem0
>>>>>
>>>>> <copy and paste an output the below for us>
>>>>>
>>>>> section              size         addr
>>>>> .debug_aranges     0x1440          0x0
>>>>> .debug_pubnames    0x377d          0x0
>>>>> .debug_info       0x4de43          0x0
>>>>> .debug_abbrev      0xab3f          0x0
>>>>> .debug_line        0xad87          0x0
>>>>> .debug_frame       0x31f8          0x0
>>>>> .debug_str         0x8482          0x0
>>>>> .debug_loc         0xd8c1          0x0
>>>>> .rom_vectors          0x8   0x68008000
>>>>> .ARM.exidx           0x10   0x68008008
>>>>> .text              0x4330   0x68008018
>>>>> .rodata             0x38c   0x6800c348
>>>>> .eh_frame             0x8   0x6800c6d8
>>>>> .data               0x180   0x6800c6e0
>>>>> .bss               0x32f8   0x6800c860
>>>>> .ARM.attributes      0x2f          0x0
>>>>> .debug_ranges      0x44c0          0x0
>>>>> .comment            0x8f7          0x0
>>>>> Total             0x8db3b
>>> I see nothinig illegal the above: .text, .*data, .bss do seat silent in
>>> the RAM its total size about 40K.
>>>
>>>>> iii)
>>>>>
>>>>> We need to look on a startup screen your RedBoot
>>>>>
>>>>> <copy and paste a starup-screen the below>
>>>>>
>>>>> RedBoot(tm) bootstrap and debug environment [ROM]           
>>>>> Non-certified release, version v3_0 - built 09:17:39, Apr  7 2009
>>>>>                                                             
>>>>> Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
>>>> 2009
>>>>> Free Software Foundation, Inc.                              
>>>>> RedBoot is free software, covered by the eCos license, derived from
>>>> the
>>>>> GNU General Public License. You are welcome to change it and/or
>>>> distribute
>>>>> copies of it under certain conditions. Under the license terms,
>>>> RedBoot's
>>>>> source code and full license terms must have been made available to
>>>> you.
>>>>> Redboot comes with ABSOLUTELY NO WARRANTY.                  
>>>>>
>>>>> Platform: ST STM3210E EVAL (Cortex-M3) 
>>>>> RAM: 0x68000000-0x68100000 [0x68003188-0x68100000 available]
>>>>>      0x20000000-0x2000f000 [0x20000000-0x2000f000 available]                    
>>> What's a nice board! IMHO, it's very suitable for eCos. You have ~1M of
>>> a volatile memory.
>>>
>>>>> Note: I want to know a bit more about your RAM location and its size.
>>>>> RedBoot talks about.
>>>>>
>>>>>
>>>>> Sergei
>>> Graham, let's resume what you've got:
>>>
>>> 1) You have arm-eabi GNU toolchain with it you are able to build eCos
>>>    applications.
>>>
>>> 2) You have a nice bootstrap environment with GDB support -- RedBoot.
>>>
>>> 3) You are able using X-modem protocol and minicom to upload the images
>>>    into RAM. IMHO, if you can to load a test image in a few hundreds of
>>>    Kb into the RAM, your GDB must do it too.
>>>
>>> Before to start debug GDB protocol, dance with packet's sizes, etc. My
>>> the first guess: you misconfigured eCos build. I do not know how you
>>> configured eCos build. I do not know what you check/uncheck using eCos
>>> `configtool'.
>>>
>>> So, can you reproduce the below just in Linux bash?
>>>
>>> i. Build a minimal eCos stuff as
>>>
>>> echo $ECOS_REPOSITORY >> report.txt
>>> echo $PATH >> report.txt
>>> cd /tmp
>>> mkdir lab1
>>> cd lab1
>>> ecosconfig new stm3210e minimal
>>> ecosconfig tree
>>> make -s
>>> make -s -C hal/common/current tests
>>> ls -R install/tests >> report.txt
>>>
>>> Note: attach the report.txt then.
>>>
>>>
>>> ii. Leave minicom if it runs!
>>>
>>> lsof /dev/ttyS0 ;# you must see no output
>>>
>>>
>>> iii. Reset the board and invoke arm-eabi-gdb as
>>>
>>> arm-eabi-gdb -q -nx install/tests/hal/common/current/tests/basic
>>>
>>>
>>> iv. GDB
>>>
>>> Now on GDB prompt type a line by a line (see the below)
>>>
>>> (gdb) set logging on
>>> (gdb) set remotebaud 38400
>>> (gdb) target remote /dev/ttyS0
>>>
>>> Here you can to see that board connected, if gdb wait here, reset the
>>> board and try `target' command again.
>>>
>>> (gdb) load
>>>
>>> I very hope that will be done. If it will, continue:
>>>
>>> (gdb) b cyg_test_init
>>> (gdb) b cyg_test_exit
>>> (gdb) c
>>> (gdb) c
>>>
>>>
>>> Please, repeat the above lab1 exactly! And the report about the results:
>>> attach report.txt, gdb.txt. The files should be in that /tmp/lab1
>>> directory.
>>>
>>> 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
>>>
>>>
>>>
>> Hello Sergei
>> This worked - I manged to run gdb
>> So what was wrong with my first application? I did not change any settings
>> in the config tool, just used a default configuration. You will see that I
>> am still getting 'Ignoring packet error' and it seems to take quite a
>> while to download.
>> THnaks for you help so far  - what could be wrong with my original
>> configuration?
>>
>> Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
>> http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
>>
> Unfortunately this is not repeatable - just tried it again and it fails to
> download!

Any way you can try it at a slower speed?

BTW, your nabble.com URLs aren't accessible from the U.S. :-(
I had to use a machine in England to look at them.

-- 
------------------------------------------------------------
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] arm-eabi-gdb

[grahamlab]

Sergei Gavrikov-4 wrote:
> 
> On Tue, Apr 07, 2009 at 03:25:06PM +0300, Sergei Gavrikov wrote:
>> Graham wrote:
>> 
>> [snip]
>> 
>> > This worked - I manged to run gdb
>> > So what was wrong with my first application? I did not change any
>> settings
>> > in the config tool, just used a default configuration. You will see
>> that I
>> > am still getting 'Ignoring packet error' and it seems to take quite a
>> while
>> > to download.
>> > THnaks for you help so far  - what could be wrong with my original
>> > configuration?
>> > 
>> > Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
>> > http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
>> 
>> Hm, I am looking at gdb.txt... I would say, It most likes not work than
>> works: 31 bytes/sec and a lot of re-transmissions. I wonder, How many
>> re-transmissions you have when you load thist `basic' using x-modem?
>> 
>> The second Q: Can you ping from Linux guest your windows box? I would
>> suggest to try serial-to-tcp bridge. But you can still play with GDB
>> packet's sizes
>> 
>> (gdb) set remote memory-write-packet-size 64
>> (gdb) set remote memory-write-packet-size fixed
>> (gdb) set remote memory-write-packet-size 64
>> (gdb) set remote memory-write-packet-size fixed
> 
> Last two lines are copy and paste typos
> 
>  (gdb) set remote memory-read-packet-size 64
>  (gdb) set remote memory-read-packet-size fixed
> 
> 64 -- just a guess, try the different sizes. Report, if it helped.
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 
Setting the packet size to 64 works reliably
Thanks very much for all your help - it is really appreciated 
:jumping::jumping::jumping:
-- 
View this message in context: http://www.nabble.com/arm-eabi-gdb-tp22908205p22928333.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] arm-eabi-gdb

[Sergei Gavrikov]

On Tue, Apr 07, 2009 at 05:56:16AM -0700, grahamlab wrote:
> 
> 
> 
> Sergei Gavrikov-4 wrote:
> > 
> > On Tue, Apr 07, 2009 at 03:25:06PM +0300, Sergei Gavrikov wrote:
> >> Graham wrote:
> >> 
> >> [snip]
> >> 
> >> > This worked - I manged to run gdb
> >> > So what was wrong with my first application? I did not change any
> >> settings
> >> > in the config tool, just used a default configuration. You will see
> >> that I
> >> > am still getting 'Ignoring packet error' and it seems to take quite a
> >> while
> >> > to download.
> >> > THnaks for you help so far  - what could be wrong with my original
> >> > configuration?
> >> > 
> >> > Graham http://www.nabble.com/file/p22927519/report.txt report.txt 
> >> > http://www.nabble.com/file/p22927519/gdb.txt gdb.txt 
> >> 
> >> Hm, I am looking at gdb.txt... I would say, It most likes not work than
> >> works: 31 bytes/sec and a lot of re-transmissions. I wonder, How many
> >> re-transmissions you have when you load thist `basic' using x-modem?
> >> 
> >> The second Q: Can you ping from Linux guest your windows box? I would
> >> suggest to try serial-to-tcp bridge. But you can still play with GDB
> >> packet's sizes
> >> 
> >> (gdb) set remote memory-write-packet-size 64
> >> (gdb) set remote memory-write-packet-size fixed
> >> (gdb) set remote memory-write-packet-size 64
> >> (gdb) set remote memory-write-packet-size fixed
> > 
> > Last two lines are copy and paste typos
> > 
> >  (gdb) set remote memory-read-packet-size 64
> >  (gdb) set remote memory-read-packet-size fixed
> > 
> > 64 -- just a guess, try the different sizes. Report, if it helped.
> > 
> > -- 
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> > 
> > 
> > 
> Setting the packet size to 64 works reliably
> Thanks very much for all your help - it is really appreciated 
> :jumping::jumping::jumping:

And I am very glad that I must not up a virtual networking 'vis-a-vis'.
I hope that we can write "THE END" for this sitcom :-)

Happy eCosing,

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