Vicne wrote:Do you have an idea what 0xFFFFFFE8 represents ?
leegong wrote:Well ,the first step is to find who sets or clears @FFFFFFE8 .
EDIT : regarding sub_BFC12E7C , i tend to think it is a RTOS service call , which is called without input parameter ,returns one bool output in v0 , it might be one of
the following RTOS service calls ,maybe this could provide some help with us :
leegong wrote:I think that sub_BFC031BC might be one of the four service calls above , have you found more other subs which check different bit position @ FFFFFFE8 ?
leegong wrote:If we are sure that sub_BFC12E7C is one of the four service calls ,then i think @ FFFFFFE8 might be a combination of bits flags
related to dispatch enable/disable ,cpu lock/unlock ... etc , there is a similar one in lower version RTOS in FR .
EDIT : @(FP+0x4D) in this post http://nikonhacker.com/viewtopic.php?f=2&t=86&start=30
leegong wrote:I traced booting progress with version2.16 and took a look at the status table of each task , 0xD structures from 0xFFFFF244 to 0xFFFFF314 with length = 0x10 bytes for
each top task
I'm wondering about why no task is in state of running according to RTOS specificication
Users browsing this forum: Google [Bot] and 6 guests