cheatsheet.md (b56bec0d27d997fd5cbc3b0bc2f8d74d7f739b48) cheatsheet.md (03504a9557ae8e269039bc2cf1803967ec2c2ffc)
1
2# OpenBMC cheatsheet
3
4This document is intended to provide a set of recipes for common OpenBMC
5customisation tasks, without having to know the full yocto build process.
6
7## Using a local kernel build
8

--- 130 unchanged lines hidden (view full) ---

139window. This results in having an easily accessible qemu command session.
140```-monitor stdio -serial pty -nodefaults```
141
142
143## Booting the host
144
145Login:
146```
1
2# OpenBMC cheatsheet
3
4This document is intended to provide a set of recipes for common OpenBMC
5customisation tasks, without having to know the full yocto build process.
6
7## Using a local kernel build
8

--- 130 unchanged lines hidden (view full) ---

139window. This results in having an easily accessible qemu command session.
140```-monitor stdio -serial pty -nodefaults```
141
142
143## Booting the host
144
145Login:
146```
147curl -c cjar -k -X POST -H "Content-Type: application/json" -d '{"data": [ "root", "0penBmc" ] }' https://bmc/login
147curl -c cjar -k -X POST -H "Content-Type: application/json" -d '{"data": [ "root", "0penBmc" ] }' https://${bmc}/login
148```
149
150Connect to host console:
151```
152ssh -p 2200 root@bmc
153```
154
155Power on:
156```
157curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT \
158 -d '{"data": "xyz.openbmc_project.State.Host.Transition.On"}' \
148```
149
150Connect to host console:
151```
152ssh -p 2200 root@bmc
153```
154
155Power on:
156```
157curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT \
158 -d '{"data": "xyz.openbmc_project.State.Host.Transition.On"}' \
159 https://bmc/xyz/openbmc_project/state/host0/attr/RequestedHostTransition
159 https://${bmc}/xyz/openbmc_project/state/host0/attr/RequestedHostTransition
160```
161
162## GDB
163
164[SDK build](#building-the-openbmc-sdk) provides GDB and debug symbols:
165
166* `$GDB` is available to use once SDK environment is setup
167* Debug symbols are located in `.debug/` directory of each executable

--- 26 unchanged lines hidden ---
160```
161
162## GDB
163
164[SDK build](#building-the-openbmc-sdk) provides GDB and debug symbols:
165
166* `$GDB` is available to use once SDK environment is setup
167* Debug symbols are located in `.debug/` directory of each executable

--- 26 unchanged lines hidden ---