From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/3] net: mv643xx: add driver support
Date: Sat, 25 Jan 2014 13:50:23 +0100 [thread overview]
Message-ID: <52E3B30F.6010509@gmail.com> (raw)
In-Reply-To: <20140125094411.GD25691@pengutronix.de>
On 01/25/2014 10:44 AM, Michael Grzeschik wrote:
> On Fri, Jan 24, 2014 at 08:17:23PM +0100, Sebastian Hesselbarth wrote:
>> On 01/24/2014 02:07 PM, Michael Grzeschik wrote:
>>> It would be nice to see if it is also working if barebox running as
>>> first stage bootloader. Can you try to get the UART-Image [1] via xmodem
>>> transfer running?
>>
>> Booting the UART image does work with current barebox master
>> d9a08d8bc5da ("net: phy: Fix crash when no phy is found")
>> and without your patch. I haven't applied your patch, yet.
>
> I can not reproduce that. My Images are not working with the
> uart boot mechanism. Even the first merged patches to support
> that do not boot here. What I do:
>
> sx -vv images/barebox-solidrun-cubox-uart.img < /dev/ttyUSB0 > /dev/ttyUSB0; microcom -p /dev/ttyUSB0
> ending images/barebox-solidrun-cubox-uart.img, 1448 blocks: Give your local XMODEM receive command now.
> Bytes Sent: 185472 BPS:9738
>
> Transfer complete
> connected to /dev/ttyUSB0
> Escape character: Ctrl-\
> Type the escape character followed by c to get to the menu or q to quit
>
> ----------
> From this point there is just silence.
I did the same except I am using minicom:
sx -vv images/barebox-solidrun-cubox-uart.img < /dev/ttyUSB0 >
/dev/ttyUSB0; minicom -D /dev/ttyUSB0
Then hit return and you see the barebox prompt.
BTW, you can also use kwboot that is also part of barebox:
./scripts/kwboot -t -B 115200 -D
./images/barebox-solidrun-cubox-uart.img /dev/ttyUSB0
If that also does not work, start from scratch:
make distclean
make solidrun_cubox_defconfig
make
and kwboot above
Just for the record, you are not trying this on a CuBox Pro, are you?
That would require a different RAM setup as it has 2GB and the one
shipped with barebox is for ES/1GB only.
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-01-25 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 19:23 [PATCH 0/3] dove: cubox: ethernet support Michael Grzeschik
2014-01-23 19:23 ` [PATCH 1/3] ARM: mvebu: make dove_memory_find reachable for drivers Michael Grzeschik
2014-01-23 19:23 ` [PATCH 2/3] net: mv643xx: add driver support Michael Grzeschik
2014-01-23 22:51 ` Sebastian Hesselbarth
2014-01-24 13:07 ` Michael Grzeschik
2014-01-24 19:17 ` Sebastian Hesselbarth
2014-01-25 9:44 ` Michael Grzeschik
2014-01-25 12:50 ` Sebastian Hesselbarth [this message]
2014-01-23 19:23 ` [PATCH 3/3] ARM: mvebu: add ethernet node Michael Grzeschik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E3B30F.6010509@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=mgr@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox