diff --git a/README.md b/README.md
index 183e233..531f9a9 100644
--- a/README.md
+++ b/README.md
@@ -65,20 +65,6 @@ Device information:
            PC : 002f
 ```
 
-However, if you see something like this, something is wrong and you should probably check your wiring and/or reset the arduino board or the CC board.
-
-```
-Chip information:
-      Chip ID : 0x4113
-   Flash size : 16 Kb
-    SRAM size : 1 Kb
-          USB : No
-
-Device information:
- IEEE Address : 000000000000
-           PC : 0000
-```
-
 ### 3. Using the software
 
 The python utilities provide a straightforward interface for reading/writing to your CCxxxx chip:
@@ -109,6 +95,14 @@ _NOTE:_ If you don't want to use the `--port` parameter with every command you c
 ~$ export CC_SERIAL=/dev/ttyS0
 ```
 
+## Troubleshooting
+
+You wired everything up, you double-checked that your pin assignments are correct and you are still not able to flash your device? Then try the following:
+* Try using 50k/100k resistors instead of 100k/200k. [#27](https://github.com/wavesoft/CCLib/issues/27)
+* Try to check if voltage at expected level, e.g. if you disconnect `CC_DD_O` from the Arduino and connect to a 5V power rail instead, you should read about 3.3V at `DD`. If not – probably you have wrong wiring or bad resistors.
+* If `cc_info.py` tool reports `DEBUG_LOCKED` flag, you will have to erase chip during flashing. Put the `--erase` option. [#29](https://github.com/wavesoft/CCLib/issues/29)
+* If flashing begins but stops with a message `Progress 0%...  ERROR: Could not read from the serial port!` – try to lower down the baudrate to 9600: in the Arduino file around [line 94](https://github.com/wavesoft/CCLib/blob/13ebd0878a8a691d1336b96609eb44d535021964/Arduino/CCLib/Examples/CCLib_proxy/CCLib_proxy.ino#L94), in the Python [ccproxy.py around line 85](https://github.com/wavesoft/CCLib/blob/13ebd0878a8a691d1336b96609eb44d535021964/Python/cclib/ccproxy.py#L85) replace to `self.ser = serial.Serial(port, baudrate=9600, timeout=3.0, write_timeout=3.0)`. 
+
 ## Compatibility Table
 
 In order to flash a CCxxxx chip there is a need to invoke CPU instructions, which makes the process cpu-dependant. This means that this code cannot be reused off-the-shelf for other CCxxxx chips. The following table lists the chips reported to work (or could work) with this library:
@@ -130,7 +124,7 @@ In order to flash a CCxxxx chip there is a need to invoke CPU instructions, whic
         <td>CC2531</td>
         <td><strong>0xb5</strong>..</td>
         <td>CC254X</td>
-        <td>:large_orange_diamond: Looking for testers</td>
+        <td>:white_check_mark: Works with 50k/100k resistors</td>
     </tr>
     <tr>
         <td>CC2533</td>
@@ -148,7 +142,7 @@ In order to flash a CCxxxx chip there is a need to invoke CPU instructions, whic
         <td>CC2541</td>
         <td><strong>0x41</strong>..</td>
         <td>CC254X</td>
-        <td>:large_orange_diamond: Looking for testers</td>
+        <td>:white_check_mark: Works with 50k/100k resistors</td>
     </tr>
     <tr>
         <td>CS2510</td>