Re: fwkdp setup
Re: fwkdp setup
- Subject: Re: fwkdp setup
- From: Prokash Sinha <email@hidden>
- Date: Wed, 29 Jun 2016 14:46:28 -0700
Thanks once again Brian.
I just tried once more. I can issue NMI using the keys, but got a connection using
lldb (lldb) kip-remote localhost KDP-REATTACH fails.
Same response with
xcrun lldb …. Assuming it will pick the correct lldb ( just in case ).
I’m using 10.11 OS X. Not sure if it matters or not …
Thanks for explaining some of the bits interpretations.
Now I’m starting to wonder if the male-male firewire cable is good or not.
Any terminal like software one can recommend to test out the connection outside lldb ? Like Hyperterminal ???
-Prokash On Jun 29, 2016, at 1:54 PM, Brian Bechtel < email@hidden> wrote:
You need "sudo" to modify nvram. You must reboot after setting nvram, to let the changes take effect. On the target: sudo nvram boot-args="debug=0x146 kdp_match_name=firewire fwkdp=0x8000" sudo shutdown -r now
The host needs no boot-args. You do not invoke fwkdp as root; invoke it normally. Open a terminal window and type fwkdp has a bug in the status message it outputs. It mentions gdb, which is obsolete. Please file a bug report via http://bugreporter.apple.com. Leave the terminal window with fwkdp open. Open another terminal window, and type lldb (lldb) kdp-remote localhost fwkdp acts as a redirector of packets, making it appear as if your host has panicked, then sending all the packets via firewire to the target.
debug=0x8146 changes the NMI key from Left-⌘ + Right-⌘ + Power to the Power button alone. That's the 0x8000 bit debug=0x145 halts at early boot. That's the 0x1 bit.
If those aren't working, you haven't properly set boot-args on the target machine.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden