I'm recently facing a yaffs2 image write problem in u-boot.
In u-boot console, I write the yaffs2 image in ram to an already erased nand
flash with command "nand write.yaffs ${loadaddr} ${nandrootoffset}
${filesize}".
After that, if I boot using a ramdisk and mount that yaffs2 partition,
I can onl
6);
code3 = *(pAddr); //cycle 6: Addr: X0Fdata = 0x2201
AMD_SEND_CMD(baseaddr, ACMD_READMODE);
We need to add a `__asm__ __volatile__ ("sync"); ` between the write
and read operation to always get a correct result.
2009/10/28 Peter Pan
> Dear Wolfgang Denk:
>
> Our hardware sh
.
2009/11/26 Wolfgang Denk
> Dear Peter Pan,
>
> In message <48abf2c20911251756k1ca3fe19p26db4a65b68bc...@mail.gmail.com>
> you wrote:
> >
> > I have checked this problem again, and find out the reason why sometimes
> > we get a false value of the ID0 we read
My u-boot version is u-boot-2009-08.
In my U-boot, after I entered "nboot 80 0 0",
the following messages shows:
Loading from NAND 1GiB 3,3V 8-bit, offset 0x0
Image Name: Linux-2.6.22.sac.rd
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size:1045865 Bytes = 102
Dear Wolfgang Denk:
I'm using U-Boot-2009-08 now. And I have a problem booting
my linux image from nand flash. I can boot from my norflash
using NFS, and mount my Nand flash, nand flash works file with
fstype yaffs2.
I run command nboot 80 0 0 (device 0, offset 0, into memory
0x80), then it
"long long"
to "unsigned long". And the Function gets the same parameters caller gives.
Maybe ppc stack here does not support long long?
2009/11/30 Peter Pan
> Dear Wolfgang Denk:
> I'm using U-Boot-2009-08 now. And I have a problem booting
> my linux image from na
CONFIG_SYS_64BIT_VSPRINTF for correct output!
After I change the loff_t from long long to unsigned long, it works fine now.
2009/12/1 Scott Wood
>
> On Fri, Nov 27, 2009 at 08:14:41PM +0800, Peter Pan wrote:
> > My u-boot version is u-boot-2009-08.
> > In my U-boot, after I entered
Scott Wood :
> Peter Pan wrote:
>>
>> The previous u-boot version I use is U-boot 1.2.0, an ancient version.
>> So I upgrade the u-boot to 2009-08.
>> The platform is MPC8247.
>
> That's a chip, not a platform. Which NAND controller driver? What happens
> i
Recently, we had a issue that we need to start more than one board at
a time. The problem
we are facing is that every board is using the same u-boot, which
makes them all have the
same mac address.
Firstly, I think I can gives out a random MAC as we need, but I can
not find any rand() or srand()
f
rkers,
we can not set the MAC address by hand. So what I means is to make the
u-boot generate a temporarily random local-administration MAC and get the
correct information later.
May I know how other set their boards' MAC address. Is there any trick to
do this job.
2010/2/8 Wolfgang Denk :
&g
Thank you very much. I will check their approach.
2010/2/8 Wolfgang Denk :
> Dear Peter Pan,
>
> In message <48abf2c21002080330k285f07b2y8b55f978a28cd...@mail.gmail.com> you
> wrote:
>> I understand what your mean. But we need to setup the boards' information
>>
Thank you very much for your advice. That's a very nice approach.
We will try this in our next version.
2010/2/9 Aras Vaichas :
>>> There are many ways to install a MAC into your hardware -without
>>> hard-conding one into your image code.
>>>
Because of the quantity of the boards comparing w
My U-boot 1.2.0 works fine before. but I want to add some memory test
actions before u-boot start Linux.
I use the "mtest" command to test the memory. But the "mtest" command will
test the memory infinitely.
So, I change the /common/cmd_mem.c, and do the following change:
#if defined(CFG_ALT_MEMTE
r cross compile, and the ELDK gcc version is :
ppc_6xx-gcc(GCC) 4.2.2
Which part of the code may cause this kind of problem? Maybe I can send your
that part of my codes.
2009/10/27 Wolfgang Denk
> Dear Peter Pan,
>
> please keel the mailinmg list on Cc:
>
> In message <48a
I found out that even with the same source code, the final u-boot.bin
has a different MD5sum each time I build.
Is that possible to get an identical u-boot.bin for the same source
code, no matter when I build?
___
U-Boot mailing list
U-Boot@lists.denx.de
workaround to solve this problem.
2011/6/12 Mike Frysinger :
> On Saturday, June 11, 2011 02:55:41 Wolfgang Denk wrote:
>> Peter Pan wrote:
>> > I found out that even with the same source code, the final u-boot.bin
>> > has a different MD5sum each time I build.
>> > Is
OK, I will try to find that Linux patch and see how it goes.
And, first of all, I will suggest my manager to change the
checkout-build-release process. I also agree that just release the
binary we tested is a much better way.
Thank you guys.
2011/6/13 Jon Povey :
> u-boot-boun...@lists.denx.de
First of all, the examples/standalone/Makefile is still using architecture
"ppc" instead of "powerpc". The "sched" application is never compiled.
I replace "ppc" with "powerpc" inside this Makefile, the "sched"
application is now compiled.
But the "sched" application is not working correctly. Onc
I'm recently using YAFFS2 rootfs on our NAND flash. What I'm
experiencing is that
the u-boot console "nand write.yaffs" is not working.
With this image file, I can successfully write it to nand flash if I
boot into Linux. In
Linux console, I run "nandwrite -a -o /dev/mtd4 yaffs2.img". And then,
I c
-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de]
On
>> Behalf Of Peter Pan
>> Sent: Wednesday, September 21, 2011 9:09 AM
>> To: u-boot@lists.denx.de
>> Subject: [U-Boot] The command "nand write.yaffs" is not working correctly
>>
>> I'
Hi Wolfgang,
vxWorks needs all interrupt to be disabled before it's boot up, while
u-boot sometimes enables them.
Recently, I'm facing this kind of problem about booting up vxWorks
through bootvx command.
So, I added a patch to the common/cmd_elf.c to disable all interrupts
before run into vxWorks
printf ("## Starting vxWorks at 0x%08lx ...\n", addr);
((void (*)(void)) addr) ();
--
1.7.4.1
2011/10/12 Wolfgang Denk :
> Dear Peter Pan,
>
> In message
> you
> wrote:
>>
>> vxWorks needs all interrupt to be disabled before it's boot u
Hi Wolfgang,
I've installed the git-email packet now, but I can not make it work.
The "Unable to initialize SMTP properly" always pop up. T_T
This is the first time I send any patch to the community, sorry for
the incontinence.
This is tested on our board, and I think at least for any Freescale
E
bootvx : Disable interrupts before boot up vxWorks
vxWorks needs all interrupts to be disabled before boot up.
Signed-off-by: Ke Pan
---
Changes for v2:
- Remove console outputs
- Add a comment
- Change the log message
common/cmd_elf.c |2 ++
1 files changed, 2 insertions(+), 0 d
24 matches
Mail list logo
