Re: [Solved/Patch Question] Weird 5200/mtd-ram problem

2009-05-27 Thread Jon Smirl
On Wed, May 27, 2009 at 3:54 PM, Albrecht Dreß wrote: > Hi all: > > Am 25.05.09 23:47 schrieb(en) Wolfram Sang: >>> >>> A word or long copy of 0x0055aaff with U-Boot works fine, but a byte copy >>> filled the whole ram with 0x.  The reason is apparently that the >>> chip is attached to t

[Solved/Patch Question] Weird 5200/mtd-ram problem

2009-05-27 Thread Albrecht Dreß
Hi all: Am 25.05.09 23:47 schrieb(en) Wolfram Sang: A word or long copy of 0x0055aaff with U-Boot works fine, but a byte copy filled the whole ram with 0x. The reason is apparently that the chip is attached to the local bus in 16-bit mode, which is incompatible with byte accesses.

Re: Weird 5200/mtd-ram problem

2009-05-25 Thread Wolfram Sang
> A word or long copy of 0x0055aaff with U-Boot works fine, but a byte > copy filled the whole ram with 0x. The reason is apparently > that the chip is attached to the local bus in 16-bit mode, which is > incompatible with byte accesses. However, the Local Bus doesn't provide > "l

Re: Weird 5200/mtd-ram problem

2009-05-25 Thread Wolfgang Denk
Dear Albrecht =?iso-8859-1?b?RHJl3w==?=, In message <1243273283.332...@antares> you wrote: > > Thanks for youre help, and sorry for the late reply - I've been on > vacation... Hally you... > For the mtd driver, I tracked down the problem via mapram_write() (in > drivers/mtd/chips/map_ram.c)

Re: Weird 5200/mtd-ram problem

2009-05-25 Thread Albrecht Dreß
Hi Gary & Wolfram: Thanks for youre help, and sorry for the late reply - I've been on vacation... Am 20.05.09 21:59 schrieb(en) Gary Thomas: Try to access this without using the cache. Unfortunately, this is not cache related - I switched the dcache off completely - same results. Am 20

Re: Weird 5200/mtd-ram problem

2009-05-20 Thread Wolfram Sang
> For the test I created a "pattern file" which is filled with the unsigned > long 0x0055aaff. Using the Abatron BDI3000, I can write the pattern file to > the ram and re-read it without problems. The same applies to u-boot (write > ram via tftp, dump contents). Does it work with byte, word and

Re: Weird 5200/mtd-ram problem

2009-05-20 Thread Gary Thomas
Albrecht Dreß wrote: > Am 20.05.09 16:23 schrieb(en) Gary Thomas: >> > In Linux, when I write the file to /dev/mtdx, the last dword of each >> block is broken, e.g. when running "dd if=pattern of=/dev/mtd5 bs=512" >> the dword's at offset 0x1fc, 0x3fc, ... are 0x (instead of >> 0x0055aaff)

Re: Weird 5200/mtd-ram problem

2009-05-20 Thread Albrecht Dreß
Am 20.05.09 16:23 schrieb(en) Gary Thomas: > In Linux, when I write the file to /dev/mtdx, the last dword of each block is broken, e.g. when running "dd if=pattern of=/dev/mtd5 bs=512" the dword's at offset 0x1fc, 0x3fc, ... are 0x (instead of 0x0055aaff), if I use bs=1024 the dwords

Re: Weird 5200/mtd-ram problem

2009-05-20 Thread Gary Thomas
Albrecht Dreß wrote: > Hi all, > > I ran into a weird problem when I tried to access a static (NV) ram attached > to the localbus of a '5200 using Wolfram's mtd-ram OF driver (on a stock > 2.6.29.1 kernel). The 512k ram chip is connected in 16-bit mode to cs1. the > of entry reads > > nv...

Weird 5200/mtd-ram problem

2009-05-20 Thread Albrecht Dre�
Hi all, I ran into a weird problem when I tried to access a static (NV) ram attached to the localbus of a '5200 using Wolfram's mtd-ram OF driver (on a stock 2.6.29.1 kernel). The 512k ram chip is connected in 16-bit mode to cs1. the of entry reads nv...@1,0 { compatible = "mtd-ram";