[BR-AVR32] Re: (ATTicket:230254) remote debugging Linux on the AVR32
Campanella, David
Fri Jan 4 04:37:29 CET 2008
- Previous message: [BR-AVR32] Re: (ATTicket:230254) remote debugging Linux on the AVR32
- Next message: [BR-AVR32] RE: (ATTicket:230254) remote debugging Linux on the AVR32
-
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Hans,
Thanks for the tip on the login in for the FTP server, yes that was an
issue on my part. In another email I detail out what I've done in
regards to .config and I have a kernel based on 2.6.23.atmel.4 that I
can run but still cannot debug.
I won't say much here, I'll save it for another email in progress,
trying to minimize the bulk here :)
Thanks again,
Dave
Dave Campanella
Sr. Field Applications Engineer
Atmel Corp.
Phone: Fax
-----Original Message-----
From: Hans-Christian Egtvedt [mailto:]
Sent: Thursday, January 03, 2008 4:46 AM
To: Haavard Skinnemoen
Cc: Campanella, David; ; ;
Subject: Re: [BR-AVR32] Re: (ATTicket:230254) remote debugging Linux on
the AVR32
Haavard Skinnemoen wrote:
> On Wed, 2 Jan 2008 20:35:22 -0800
>> When I use the "older" Kernel I can initiate a FTP session but can't
>> login due to issues with the username/password.
>
> Hmm...that's probably a different issue...
>
Root login is not allowed over FTP, due to ProFTPD default
configuration. Did you try login with "avr32"/"avr32!", without the ""?
Your previous email did not have a ! on the end of the password.
>> I seem to have issues on a few fronts here...
>>
>> a. the newer patched kernel - how do I get over these out of memory
>> issues.
>
> You probably need to disable some features to make the memory
footprint
> smaller. Could you post your .config and the output of dmesg?
>
Perhaps the locking debugging is turned on by default? It consumes a lot
of memory, even running with 16 MB SDRAM is a bit short. Check what is
enabled under kernel debugging.
>> b. for any of these kernels, what is the login for ftp???
>
> The kernel has nothing to do with it, so I'm ccing the buildroot list.
>
> If you can log in as root, you can try setting a new password for the
> avr32 user by running "passwd avr32". A hash of the password is stored
> in /etc/shadow.
>
I am able to ftp to NGW100/STK1002 running with Buildroot v2.1.0 default
images. User "avr32" and password "avr32!". What ftp client are you
using to connect?
>> Before I can do any debugging with the Studio tool I need to get more
>> comfortable with the Kernel itself.
>
> Sounds like a good plan, but apart from the out-of-memory issue, I
> think most of your problems are with userspace (i.e. buildroot.)
>
> Of course, since buildroot is completely customizable, it will always
> be possible to configure it so that it doesn't work with Studio. But I
> think we need to double-check that the default configuration is sane,
> and perhaps document better what needs to be enabled in order for
> Studio to work.
>
The default image should be sane. I think this may be related to either
wrong password and/or a kernel demanding too much RAM to run.
--
With kind regards,
Hans-Christian Egtvedt, Applications Enginer
- Previous message: [BR-AVR32] Re: (ATTicket:230254) remote debugging Linux on the AVR32
- Next message: [BR-AVR32] RE: (ATTicket:230254) remote debugging Linux on the AVR32
-
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]