As of August 2020 the site you are on ( is deprecated, and content is now at


Jump to: navigation, search
Testing the Serial Connection & Observing Power
These steps differ from previous steps, as we are not going to be using a built-in target. However you can refer to tutorialcomms for general information on using the ChipWhisperer-Capture Interface.
<ol style="list-style-type: decimal;"><li>#Start ChipWhisperer-Capture</li><li>#As the ''Scope Module'', select the ''ChipWhisperer/OpenADC'' option</li><li>#As the ''Target Module'', select the ''Simple Serial'' option</li><li>#Switch to the ''Target Scope Settings'' tab, and as the ''connection'', select the ''ChipWhispererRev2'' option</li>(assuming you are using the Capture-Rev2)<li><p>Run #Switch to the scope connect (click the button labeled ''Scope: DISTarget Settings''). Only tab, and as the scope should switch to ''CONconnection'' and be green circles. , select the ''Do not press the master button like last time.ChipWhisperer'':</p><p>[[File:connectscope_1.png|image]]</p><p>When option (assuming you are done using the Capture-Rev2)#Press the software ''Master Connect'' button again (or scope+target separately). You should look as followsend up with BOTH the scope and target connected:</p><p>#:[[File:connectscope_2cwcr2_status.png|image400px]]</p><p>#:We do not connect will later manually adjust the 'target' as that would cause data to be sent to it, whereas we just want to listen on the power line while we manually send datatarget.</p></li><li><p>#From the ''Tools'' menu select ''Open Terminal'', and press ''Connect'' on the terminal:</p><p>#:[[File:termconn.png|image]]</p></li><li>#<p>Switch back to the ''Target Settings'' tab, without closing the terminal window. Set the baud rate for both TX &amp; RX to <code>9600</code> baud. Once you start using the terminal these values will switch to the actual baud rates in use (the hardware can only generate certain baud rates). You cannot use higher bauds for this tutorial as the combined error from the AVR code &amp; ChipWhisperer serial port causes communications failures.</p><p>[[File:termbaud.png|image]]</p></li><li>#In the ''ChipWhisperer-Serial Terminal'', change the ''TX on Enter'' to ''None'', as we don't want to send any character to terminate a string.</li><li>#<p>In the ''ChipWhisperer-Serial Terminal'', check the ''Show non-ASCII as hex'' if not clicked.</p><blockquote><p>[[File:term_settingssimple.png|image]]</p></blockquote></li><li>#Finally send the command <code>@@@</code>, which is the login sequence for the TinySafeBoot bootloader. Simply type this in the input line, and press 'enter' to send. You will see the <code>@@@</code> echoed on the received data in a blue font.</li><li>#<p>The objective is to get the login response. You may have to send <code>@@@</code> a few times for this to be successful, the following figure shows an example where the the login worked after sending a second round of <code>@@@</code>. You might get an invalid response your first time for example. The response should start with <code>TSB</code>:</p>
<p>Note the red bytes are hexadecimal responses, which were converted since they were outside of valid range for ASCII data. The response from TinySafeBoot has the following meaning, with example values given for our implementation, note certain values may change if you use different versions of TSB:</p>
Approved_users, bureaucrat, administrator

Navigation menu