Installing a Debug Token in your PlayBook

This note describes how to configure a PlayBook with a Debug Token so it can be used to install applications like TunnelTilt.

Steps Required

• Request a Code Signing Key
• Register the signer with the RIM servers
• Create a (Debug) Token
• Put the PlayBook in Development Mode
• Install the Debug Token in the PlayBook

Let’s go through these in sequence

Request a Code Signing Key
Point your browser to blackberry.com/SignedKeys.  Provide the following information:

• First Name and Last Name for requester
• Company
• Email address
• Country
• A CSJPIN (to be used when using the Code Signing Keys)

You will get a quick response mail acknowledging the request ()

Some time after that (around 2 hours) you will get one or two emails (depending on whether you asked for BB, for PB, or for both) each with one CSJ attached ()

The CSJ files have a name of the form: client-PBDT-CLIENTNUMBER.csj (client-RDK-CLIENTNUMBER.csj for the BB) where CLIENTNUMBER identifies “you”, the author that requested the Code Signing Keys.

Next save the CSJ files somewhere:

bash-3.2$ pushd ~/Software/Keys/
~/Software/Keys /Developer/SDKs/Research In Motion/BlackBerry WebWorks SDK for TabletOS 2.2.0.5/bbwp ~/tmp

bash-3.2$ ls
client-PBDT-CLIENTNUMBER.csj client-RDK-CLIENTNUMBER.csj

Register the Signer
Now register the signer with RIM using the blackberry-signer application.  You need the CSJPIN to use the keys, and you will create a local STOREPASSWORD for later.

bash-3.2$ blackberry-tablet-sdk/bin/blackberry-signer -register \
 -csjpin CSJPIN -storepass STOREPASSWORD \
~/Software/Keys/client-RDK-CLIENTNUMBER.csj  \
~/Software/Keys/client-PBDT-CLIENTNUMBER.csj
Info: CSK file created.
Info: Developer certificate created in /Users/epelegri/Library/Research In Motion/author.p12
Info: Successfully registered with server.
Info: Successfully registered with server.

Next you will get Emails indicating the CLIENTNUMBER was successfully registered with Signing Servers (ID RDK and/or ID PBDT) ()

We can now use this store to do multiple operations, including:

Create the Debug Token
The Debug Token is created specifically for a given PlayBook; you can get its DEVPIN from the Options panel, under About/Hardware.  We use the blackberry-debugtokenrequest application

bash-3.2$ blackberry-tablet-sdk/bin/blackberry-debugtokenrequest \
-storepass STOREPASSWORD -devicepin DEVPIN \
~/Software/Keys/MyDebugToken.bar
Info: Debug token created.

Put the PlayBook in Development Mode
Before actually installing the debug token, you need to set the PlayBook in Development Mode. That is under Options/Security. That will show the IP for your device and will also give you an opportunity to set the password. Note that your device may have more than one IP address, e.g. one for WiFi and one for USB, if connected physically that way.

• Get the device IP (DEVICEIP)
• Set and record the password for the device (DEVICEPASS)

Install the Debug Token
And finally we are ready to install the debug token. The PlayBook should (still) be in Development Mode, and connected with the same IP as above, now use the blackberry-deploy application as follows:

bash-3.2$ blackberry-tablet-sdk/bin/blackberry-deploy \
-installDebugToken ~/Software/Keys/MyDebugToken.bar \
-device DEVICEIP -password DEVICEPASS
Info: Sending request: Install Debug Token
Info: Action: Install Debug Token
Info: File size: 2252
result::success

More links

• Code Signing Keys
• Configure signing for tablet applications