On 29/08/2012 19:55, Alexander Graf wrote:
>>> Are they accessible through the monitor's p command? Would be good to
>>> implement there too if not.
>>
>> I don't think so, which syntax would you use anyway? $dcr[n] ?
>
> Sure, why not? Is that possible with the register parsing code? I don't kno
On 29.08.2012, at 10:43, François Revol wrote:
> On 29/08/2012 16:53, Alexander Graf wrote:
>>
>>
>> On 29.08.2012, at 04:03, François Revol wrote:
>>
>>> Hi,
>>> I noticed the DCRs weren't shown with the registers or another command,
>>> and tried to add one to dump them to help debugging
On 29/08/2012 16:53, Alexander Graf wrote:
>
>
> On 29.08.2012, at 04:03, François Revol wrote:
>
>> Hi,
>> I noticed the DCRs weren't shown with the registers or another command,
>> and tried to add one to dump them to help debugging my sam460ex target.
>> This first version doesn't list the n
On 29.08.2012, at 04:03, François Revol wrote:
> Hi,
> I noticed the DCRs weren't shown with the registers or another command,
> and tried to add one to dump them to help debugging my sam460ex target.
> This first version doesn't list the names since they aren't registered
> as such.
> I tried
Hi,
I noticed the DCRs weren't shown with the registers or another command,
and tried to add one to dump them to help debugging my sam460ex target.
This first version doesn't list the names since they aren't registered
as such.
I tried adding a name arg to ppc_dcr_register, and a #define to get it
