|
@Tril,
Here is something interesting...
I was looking at your TimeBalance plugin, to see if I could see anything that might be giving frost_dk problems, and I noticed that the load-time values for the iTram addresses are not valid (outside the iTram address range).
i.e. (here is a partial dump after loading the plugin)
idelay write dwFL at 0x0;
idelay read drFL at 0x241c127;
idelay write dwFR at 0x241c128;
idelay read drFR at 0x483824d;
idelay write dwRL at 0x483824e;
idelay read drRL at 0x4838250;
idelay write dwRR at 0x4838251;
idelay read drRR at 0x6c449a4;
idelay write dwC at 0x6c449a5;
idelay read drC at 0x6c500a4;
Note that your iTram size is 4190, so none of the above addresses should be above 0x105e (they are way out of range).
However, after clicking reset (or adjusting a slider):
idelay write dwFL at 0x0;
idelay read drFL at 0x2;
idelay write dwFR at 0x3;
idelay read drFR at 0x5;
idelay write dwRL at 0x6;
idelay read drRL at 0x8;
idelay write dwRR at 0x9;
idelay read drRR at 0xb;
idelay write dwC at 0xc;
idelay read drC at 0xe;
This is making me wonder if maybe there is something wrong with the plugin loading code in 3538m.
BTW: Although the addresses seem off when loading the plugin, it does not mute my sound when connected (as with frost_dk), but maybe this is a contributing factor to the problem that frost_dk is having.
|