already leaning toward having
our next design boot from a small NOR or EEPROM instead.
I'll also have our hardware guy take another look for 4k parts that
don't require >1-bit ECC (and thanks for the link).
Thanks Scott
--
Matthew L. Creech
__
;special", in that it's guaranteed not to be bad for some
minimum # of P/E cycles; will ECC errors still accumulate the same as
any other block?
>
> AFAIK, we've just been using 1-bit hw ECC. I don't know what NAND chip
> was used for
r of flash? (This seems dangerous
for long-term usage, if errors accumulate in the blocks containing
U-Boot)
At this point we're mainly trying to size up our long-term options, if
2k part availability becomes a problem. Thanks!
--
Matthew L. Creech
write a new
image to blank flash.
2. Use the "ubinize" tool to create an image suitable for writing
directly to NAND. This takes a UBIFS image and "wraps" it to turn it
into a UBI image, which you can then use with "nand write".
ion is added to generate u-boot-nand.bin with its IPL split
into two 2k chunks
then we can boot and run entirely from a 4k page device on MPC 83xx, correct?
That would be very good news, as it seems that [some] 2k NAND parts
are starting to go EOL.
Thanks!
--
Matthew L. Creech
_
er
- ubifsload [address] [...]
ubifs.img was created with:
mkfs.ubifs -m 2048 -e 129024 -c 8152 -x lzo -U -v -r /path/to/root/ -o ubifs.img
Most of this looks similar to what you're doing, but here it is anyway
just in case.
--
Matthew L. Creech
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
default. Seems to
work that way, anyway. :)
--
Matthew L. Creech
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
default (assigns 0x50 and up to "root" partition)
ubi part root
and getting what seems like stack corruption around
ubi_read_volume_table() for table copy #2. Is there anything I can do
to try and narrow down what's going wrong, other than selectively
r
On Thu, Apr 30, 2009 at 3:36 PM, Matthew L. Creech wrote:
>
> The problem I'm currently running into is step 2, which throws an
> error in ubi_io_write() (see below). Googling around turned up a few
> hits that suggested turning off sub-page writes, so I tried adding
> NAND
ite: error -5 while writing 512 bytes to PEB 4:512, written
0 bytes
UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 5:512, written
0 bytes
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -5
UBI init error -5
exit not allowed from mai
On Thu, Jan 22, 2009 at 3:36 PM, Matthew L. Creech wrote:
>
> => imi 10
>
> ## Checking Image at 0010 ...
...
>
> => md 13e61d
> 0013e61d: 4c696e75 78006e65 74627364 004e6574Linux.netbsd.Net
> ...
>
Okay, upon re-reading this I saw where the
se, I'm doing a standard "make MPC8313ERDB_NAND_33_config; make".
Any ideas on how to debug this are appreciated, thanks!
--
Matthew L. Creech
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
*(.got1)
. = ALIGN(16);
-*(.rodata)
-*(.rodata1)
-*(.rodata.str1.4)
+*(.rodata*)
*(.eh_frame)
}
.fini : { *(.fini)} =0
--
Matthew L. Creech
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/
lder
GCC (I tested with 4.3.2 and 4.2.1). The attached one-liner works for
us on the 83xx; if there are no ill effects, perhaps all of the PPC
link scripts could do something like this to fix any similar issues.
--
Matthew L. Creech
ppc-83xx-link-fix.patch
Description: Binary data
_
space for
some reason. I'm not sure whether the issue lies with U-Boot or with
binutils, though, or how to fix it - any ideas on what's wrong here?
Thanks
--
Matthew L. Creech
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
15 matches
Mail list logo
