Re: [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel

[Wayne Warren <wwarren@emacinc.com>]

  
> > 
> > So it looks like maybe __ipipe_tsc_get is working as expected? 
> 
> Yes, the debugger can not know what is at 0xffff0f40 because the code
> copied there is not known at compilation (though you can run disass
> *0xffff0f40, this should work). __ipipe_tsc_register does copy the
> actual code, but before __ipipe_tsc_register copies the code, the code
> there simply returns r0 and r1 set to 0.
> 
> You should try and put a breakpoint at 0xffff040 to see what address is
> invalid. Maybe the counter virtual address is invalid, or the access to
> the timer register because the timer is not enabled yet at hardware level.
> 

disass *0xffff0f40 did not work, "No function contains specified
address."

So in other words, you are saying that if __ipipe_tsc_register had not
registered the code, the exception would not occur because it would
simply set r0 and r1 to 0 then return to the calling function? Just want
to be certain I understand...

I did try to put a breakpoint at 0xffff040 (but I think you meant
0xfff0f040, i tried both) but then I get "Warning: Cannot insert
breakpoint 10. Error accessing memory address 0xffff040: Unknown error".

> >                       
> >>
> >> Or apply the following patch:
> >> http://git.xenomai.org/?p=ipipe-gch.git;a=commitdiff;h=42dd9056983cb6f65b6a336363f2f08f4426625a;hp=3b51cebda0b0d0123cb61b6ec07ecb62f293a528
> > 
> > I will try this out, thanks!
> 
> It will probably not fix this issue, but it is better to start from that
> code anyway.
> 

Okay, just to be clear are you suggesting that we start all over with
this patch, merge in the TI changes and our own code, and begin
debugging again from there?