Hi Wolfgang,
On Sun, Jan 31, 2010 at 9:27 PM, Wolfgang Denk wrote:
> Dear Chetan Nanda,
>
> In message <7f245da81001310745i8e54f9dr95cb4c0af0a74...@mail.gmail.com>
> you wrote:
> >
> > As there is considerable difference between the logs I am getting and
> logs
ese differences.
~cnanda
On Sun, Jan 31, 2010 at 8:43 PM, Wolfgang Denk wrote:
> Dear Chetan Nanda,
>
> In message <7f245da81001310646x12451ac8s5ac9bda0fd6ac...@mail.gmail.com>
> you wrote:
> >
> > Tried with loady command in u-boot and ymodem option from minicom.
>
Tried with loady command in u-boot and ymodem option from minicom.
With this combination I am able to transfer and run uImage.
~cnanda
On Sat, Jan 30, 2010 at 10:02 PM, Wolfgang Denk wrote:
> Dear Chetan Nanda,
>
> In message <7f245da81001300735x6d0727f8s2f530d6a3540e...@mail.gmai
HI all,
I am working on OMAP3 based SoC. I am trying to send uImage over serial port
using kermit.
I have followed folowing:
1. issued a loadb command on u-boot prompt.
2. On c-termit> send /bin uImage
Every time after this transfer get started but then aborted automatically
with following error
On Sat, Nov 7, 2009 at 7:16 PM, Dirk Behme wrote:
> Chetan Nanda wrote:
>
>> Hi List,
>>
>> I am trying to compile U-Boot for beagleboard. I have run following
>> commands:
>>
>> make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
>> make CROSS_COM
n 'blue_LED_on' cannot be declared weak
board.c:112: error: inline function 'blue_LED_off' cannot be declared weak
I get the U-Boot code from Git repository few days back using:
git clone git://git.denx.de/u-boot.git u-boot-main
cd u-boot-main
y? I'm obviously overlooking something I think.
So romReserved will not get called in normal booting-sequence as code will
jump to 'reset' label.
In case of some exception 'romReserved' will be called and then board will
struck in while loop.
Thanks,
Che
On Mon, Jul 27, 2009 at 8:36 PM, Tim Braun wrote:
> Chetan Nanda wrote:
> > We have a MIPS-4KEC based SoC and running an older version of U-Boot
> > (1.1.3) on it. It is working perfectly fine.
> > Board has 8MB AMD flash and starting address of that flash is
> > 0xBFC0
- 0xBFFF (4MB) is accessible, as it lies in un-mapped, un-cached region
of MIPS.
>From 0xC000 lies in mapped memory area of MIPS.
Now my questions are, creating entry in TLBs is sufficient to access rest of
4MB of flash?
Is their any interface provided in U-boot to update TLB?
Thanks,
Che
9 matches
Mail list logo
