First line loads a pointer to r3 Second line adds offset to pinter to r3, and than data from that offset is stored to r3. PPc code can use only 16 bit addressing and makes full address out of 2 commands I have another quick question, How to set up in IDApro r14-r17 registers with fixed values as in...

i have the following: a.png and FKLAFUGD is a label for the following address: b.png whats the point in calling lis r3,0x5d before calling a lhz command? i mean, wont the lhz just overwrite what the lis did? from what ive learned: lis r3,0x5d // this makes r3 = 0x5d0000 lhz r3, offset FKLAFUGD(r3) /...

first of all, thanks for all the help, it was crucial! i found ghidra to be easier to use than ida (maybe this is the case for ppc only, but this is what worked for me), so ill share how i did it. please forgive any dumbness i might say here, im not very familiar with most technical terms (even basi...

Fairly certain rlsol and misopl are calculated, so yes, I'd assume they will still change, regardless of limiters. Could be wrong, I only deal with ME9.6, but the basics are the same. hi, i have logged all the torque limiters i could find, and they dont seem to be the issue. its like there is a TB ...

i will log the usual limiters then, and post back. thanks for your input.

i was under the impression that if there was any limiter, my misopl and rlsol would show as the limited values (i.e. it would be applied and shown).

if it was iop would i still get these numbers for misopl and rlsol or would it be already showing as the limited numbers?

i generated kfmiop from irl using excel:

hi, please find attached the corresponding log in case checking it is necessary. can someone point me to that could possibly limit the throttle opening other than KFWDKSMX (already maxed) and KLRLNMXN has more than enough load? MKBRMXWP, KFMDBGRG, KFMDBGRK, MIVMXPNGE, MIVMXNIVE, MDGAT, KFWDKSMX, all...

Just from eyeballing it, those repeated patterns @ 16 bit values make me think that's calibration data, not code. Also because the arrow in the map at the top shows no code around it. If you have an XDF see if that area or data around it in the non-code section is defined as calibration data. sorry...

so after doing it all I went to options -> general -> reanalyze program. it ran through the whole thing and made a lot more of the top bar into blue area (regular function). then i did the reanalyze program thing again, and it turned even more area into blue. after this, it wouldnt change anymore by...

kur4o wrote: ↑Fri Mar 08, 2024 9:52 pm Some vectors are jump to offset and don`t use absolute addressing mode. In that case use C button to convert to instruction->branch to vector.

thanks, that worked!