# RSB-4810 debug terminal

**URL:** <https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640>\
**Category:** Technical Supports\
**Created:** [November 17, 2023, 10:47am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640 "2023-11-17T10:47:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bart\_Ek](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Bart\_Ek](https://forum.aim-linux.advantech.com/u/Bart_Ek)\
**Post date:** [November 17, 2023, 10:47am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/1 "2023-11-17T10:47:28Z")

</div>

I’m working on updating android on RSB-4810 board. I’ve installed RKDevTool and Driver Assistant packages on my PC (Windows) and I’m able to connect my PC with the board and see my device as Maskrom device in RKDevTool.

Following these instructions [http://ess-wiki.advantech.com.tw/view/RSB-4810\_Android12\_OS\_User\_Guide#How\_to\_update\_images.3F](http://ess-wiki.advantech.com.tw/view/RSB-4810_Android12_OS_User_Guide#How_to_update_images.3F) I need to:

“4. Power on the RSB-4810 and press “Ctrl+c” in the debug terminal to stop at u-boot”.

How do I enter the “debug terminal”? Do I need to install some additional software? Will that debug terminal connect to the RSB-4810 board via the same USB cable that RKDevTool is using? Please provide instructions how to achieve this step.

---

<div class="post-metadata">

**Author:** ![Jems\_Cheng](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@Jems\_Cheng](https://forum.aim-linux.advantech.com/u/Jems_Cheng)\
**Post date:** [November 20, 2023, 1:48am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/2 "2023-11-20T01:48:40Z")

</div>

Hi~

Please prepare the debug cable.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/5ab0d516621fd9c4ed2b37f224237cf2da1b4189.png)  
And use Hyper terminal, Tera Term or Putty to communicate with the RSB-4810 through debug port.  
[RSB-4810\_User\_Manual\_ed.1.FINAL.pdf (advantech.com)](https://advdownload.advantech.com/productfile/Downloadfile1/1-28S26U4/RSB-4810_User_Manual_ed.1.FINAL.pdf)  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/9b700d0a4db1a00631d502fb16d851a527d51f82.png)

---

<div class="post-metadata">

**Author:** ![Bart\_Ek](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Bart\_Ek](https://forum.aim-linux.advantech.com/u/Bart_Ek)\
**Post date:** [November 20, 2023, 11:21am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/3 "2023-11-20T11:21:27Z")

</div>

Hi Jems Cheng.

Thanks for your reply.

Coud you please provide a pin schema for the debug port, similar to the below schema from [https://downloadt.advantech.com.cn/ProductFile/Downloadfile4/1-1ZJSAPW/RSB-4710\_User\_Manual\_ed.1\_FINAL.pdf](https://downloadt.advantech.com.cn/ProductFile/Downloadfile4/1-1ZJSAPW/RSB-4710_User_Manual_ed.1_FINAL.pdf)

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/2c9c31452de12a85813d9579663f9678bbe79703.jpeg)

Also could you please provide a connector name / type for the debug port, I can’t recognise it.

---

<div class="post-metadata">

**Author:** ![Jems\_Cheng](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@Jems\_Cheng](https://forum.aim-linux.advantech.com/u/Jems_Cheng)\
**Post date:** [November 23, 2023, 2:27am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/4 "2023-11-23T02:27:38Z")

</div>

Hi~

We will update this information to user guide. Please reference the debug connector below first.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/9775a33a4c0008215d08792d893dae6d675738fa.png)

---

<div class="post-metadata">

**Author:** ![Bart\_Ek](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Bart\_Ek](https://forum.aim-linux.advantech.com/u/Bart_Ek)\
**Post date:** [November 27, 2023, 3:38pm UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/5 "2023-11-27T15:38:31Z")

</div>

Hi Jems Cheng

After your last advice I was able to connect the board with my PC using the debug cable. But in order to do so I had to connect pins 2 and 3 on J1, not 1 & 2 as stated in [http://ess-wiki.advantech.com.tw/view/RSB-4810\_Android12\_OS\_User\_Guide](http://ess-wiki.advantech.com.tw/view/RSB-4810_Android12_OS_User_Guide) “Short pin 12 and power on the RSB-4810 to enter MASKROM mode. Change back to pin 23 before click “Run” to flash image”

Now I’m getting an error in step 8: “MiliLoaderAll is not existed, stop running!”. I’ve downloaded RKDevTool from [AIM-Linux/BSP/RK/Linux Android OS Release note/Android12/Internal - ESS-WIKI](http://ess-wiki.advantech.com.tw/view/AIM-Linux/BSP/RK/Linux_Android_OS_Release_note/Android12/Internal), tag RK3568\_S12\_AIV12001.xml.

 ![Issue1](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/c7d1f6767eb01a7278a0f6f52a3f40449274e709.png)

Please advice what should i do.  
Also please advice if I need to switch J1 back to pins 1 & 2 before flashing image, or should it stay on pins 2 & 3.

---

<div class="post-metadata">

**Author:** ![Jems\_Cheng](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@Jems\_Cheng](https://forum.aim-linux.advantech.com/u/Jems_Cheng)\
**Post date:** [November 28, 2023, 4:51am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/6 "2023-11-28T04:51:30Z")

</div>

Please reference here to connect a debug cable and install Hyper terminal, Tera Term or Putty to connect to the debug port of the RSB-4810.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/c4436e4293a9bf39dd5c051dd973d15b004858d9.jpeg)

---

<div class="post-metadata">

**Author:** ![Bart\_Ek](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Bart\_Ek](https://forum.aim-linux.advantech.com/u/Bart_Ek)\
**Post date:** [November 28, 2023, 7:41am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/7 "2023-11-28T07:41:20Z")

</div>

Hi Jems\_Cheng

I did connect to the board using debug cable and Putty and was able to reboot to MASKROM mode using rbrom command:

 ![Issue2](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/1adf306b4525484960a9a703e48dd8555a6db7a8.jpeg)

I have an issue with the step 8 of the procedure, where I’m getting the error I’ve described in my previous post. Please advice how I can fix this problem.

---

<div class="post-metadata">

**Author:** ![Jems\_Cheng](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@Jems\_Cheng](https://forum.aim-linux.advantech.com/u/Jems_Cheng)\
**Post date:** [November 29, 2023, 1:38am UTC](https://forum.aim-linux.advantech.com/t/rsb-4810-debug-terminal/640/8 "2023-11-29T01:38:43Z")

</div>

Hi~  
The J4 should change to pin1&2.  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/4863117f1a6a89e69a87c9af374805f3fd927d7b.jpeg)

Check the screenshot the RKDevTool are not select the correct the image file path.  
Please click the latest frame on each image file and select correct files and images.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/8ac8a93aca8473076729e7d2d2242c18251a67fe.png)  
Here is an Image files path on my system for reference:  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/d6e3fe51bef270bfcc0656a10075d2780a790263.png)

Alternatively, please download and repleace the RKDevTool\_Release\_v2.84 from the link below. It has added the path into the RKDevTool.

> **[Google Drive: Sign-in](https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F17ubb9vRBaYrE8ezxVrGH_ii8qNJnyBM3%2Fview%3Fusp%3Ddrive_link&followup=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F17ubb9vRBaYrE8ezxVrGH_ii8qNJnyBM3%2Fview%3Fusp%3Ddrive_link&ifkv=ASKXGp1SNdd2lpPzQTNMZxlRVJgT8jkAc7wiF8EwDTKe52N8IqJKOOzb34TukALJk-V_rh8Um6xGkw&osid=1&passive=1209600&service=wise&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S839368058%3A1701220504282813&theme=glif)**
>
> Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

 ![image](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/1X/8ccc638a338ae2aec404f1085e043426483ef54e.png)
