On 2006-11-13 18:30 -0000, David Bisset wrote:
> >> 3) I can't seem to use the new bflash jtag code on balloon2 at all,
> >> either in bflash or jflash mode. It is working for anyone else?
>
> This will not work.
>
> All the code for Balloon 2 is built into jflash, and I have had it working.
Do you mean bflash there? Or do you mean balloon2 only works using
the jflash interface/compatibility code?
> However there are a couple of default states (internal to bflash) that are
> different between Balloon3 and Balloon2 and the code to context switch them
> is not clean, so they were left set for Balloon3 since that is what bflash
> was to be used for.
>
> The reason for the unclean-ness is that I have fully parameterised the
> settings for Balloon2 and Balloon3 so that simply changing the definition
> structs is sufficient to switch processors (and indeed add new ones). The
> problem with the existing parameterisation is that there was no easy way to
> state if a signal was active high or active low (its default can be set but
> not the sense).
> This needs to be added. (From memory the signals in question are the bus
> enables and you should find some commented out lines that simply invert
> these, however until I get back to this in a few weeks I can't put my hand
> on my heart and say that by swapping the comments bflash will work for L2.)
I can't find anything that looks like that, although I'm wandering
around in the gloom rather at the moment. There is partSetDataBus and
partSetBusControl. Or should it be in one of the .h files?
I see that for B3 servel extra control structures are set up which are
not set up for B2:
part_data.data_bus = PXA270DataBus;
part_data.address_bus = PXA270AddressBus;
part_data.control = PXA270ControlSignals;
The .h files describes these as stuff which would be parsed out of the
BDSL files, but currently isn't. I see no sign of any BDSL files at
the moment, so perhaps these need setting up for B2? There is
no correspdoning SA1100ControlSignals in balloon2-signals.h Certainly the
nullness of part_data.control gives me a Segfault at part_driver.c:521
(in jtagGetData():
idx = part->control_pin_map[i];
pin = part->control[idx].enable;
(part->control is 0, and so is idx (although that might be right).
I have no idea how to derive these structs from the BDSL file I don't
have...so I think I'm stuck again.
> I also remember having to swap the output line defs in playsvx to make it
> work with the xilinx dongle however that was about 2 years ago so this may
> be a red herring.
Yes. I had a look at that and what was in svn corresponded to what you
told me was right. It was just the port_en pullup.
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
(text/plain)