Raúl Sánchez Siles wrote: > Hello All: > > Thanks a lot for the prompt answers, unlike this e-mail. I've been off from > the office since my post, so sorry for it. > > I now notice I failed to provide sufficient details about the issue at > discussion. The flash uses is a 16bit data width, but it is connected using > just 8 bit width. Only the lower data byte is output by the chip and the A-1 > address line is used. So in summary, one 16bit width flash chip used as 8bit > width by a 8bit data width processor. > OK, so that is a chipwidth = buswidth =1 szenario.
>> Um - no. The x16_as_x8 option is used for 16-bit flashes that can be >> used with an 8-bit data bus. The reason for that option is that in that >> mode, the "magic" address values used for commands is shifted 1 bit >> against what is used on "real" 8-bit flashs. The option should only tell >> that a 16-bit flash chip is connected to a 8-bit bus - having multiple >> such chips in parallel must be handled by the chip/bus geometry handling. >> > > And again, I think this is the point. I'll try to implement this parameter. > Looks like what I only need is that "magic", it's only that so far I wasn't > able to make the flash work any other way. > > I think I aim that the following line works: > > flash bank cfi 0x80000000 0x1000000 1 1 0 x16_as_x8 > > Please, correct me if I'm wrong. > That looks right, yes - I can't tell if it actually works, but that is the way it is meant to be used. > >> You might have a look at the CFI code in u-boot, which I *think* does >> handle this situation correct, however, I have no board with such a >> flash layout, so I can't really tell. >> > > Thanks, I'll take a look. > In the x16_as_x8 case, I would suggest not looking at u-boot but rather directly trying to get the openocd code to work on your board - if x16_as_x8 should be broken, it should not be too difficult to fix - it is just a matter of having a board to test the code on. cu Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
