With the AMB82-Mini is there a way to silence all the log info that gets sent to the console?
Hi @GEdmunds ,
May I know what are the log info that you would like to disable? Are you using Arduino SDK or FreeRTOS SDK?
Hi Pammy - the output from the RTSP Streaming sample code. It’s useful when debugging but once things are working right it adds a bit too much chatter. Here is just some of it:
10:46:56.403 → inputRateNumer[10] < outputRateNumer[30], Set inputRateNumer → outputRateNumer
10:46:56.403 → [VOE]ext_in = 0 sync = 0
10:46:56.403 → [VOE]isp_device_probe had done
10:46:56.403 → [VOE]isp_soc_start already done
10:46:56.403 → [VOE]VOE MEM Size = 24029 Used= 20764 KB Free= 3264 KB (3342624)
10:46:56.403 → [VOE]stream 4 buffer 0: 0x71897900 size 921600
10:46:56.403 → [VOE]stream 4 buffer 1: 0x71978a00 size 921600
10:46:56.436 → [VOE]RGB3 640x480 1/10
10:46:56.436 → [VOE]scale down set_mcrop
10:46:56.436 → [VOE]status == 1718
10:46:56.146 → IQ:FW size (98342)
10:46:56.146 → sensor:date 2024/9/12 version:RTL8735B_VOE_1.5.7.0
10:46:56.146 → sensor:FW size (5412)
10:46:56.146 → sensor timestamp: 2024/09/12
10:46:56.146 → iq timestamp: 2023/05/15 14:48:54
10:46:56.146 → voe_heap malloc 0x70450560, size 24605696
10:46:56.146 → ISP:1 ENC:1 H265:1 NN:1
10:46:56.177 → hal_voe_ready 0x0 0xbf1208
10:46:56.177 → voe :RTL8735B_VOE_1.5.8.0
10:46:56.177 → sensor:RTL8735B_VOE_1.5.7.0
10:46:56.177 → hal :RTL8735B_VOE_1.5.8.0
10:46:56.177 → load time sensor:151us iq:2724us itcm:0us dtcm:0us ddr:0us ddr2:0us
10:46:56.177 → Set H264 default HIGH profile
10:46:56.177 → [video_pre_init_procedure] START
10:46:56.436 → hal_voe_send2voe too long 30517 cmd 0x00000206 p1 0x00000000 p2 0x00000004
10:46:56.436 → [VOE]release s4 isp buffer 0
10:46:56.436 → [VOE][WARN]useless release s4 slot0 status 0x00000000
10:46:56.436 → [VOE]release s4 isp buffer 1
10:46:56.436 → [VOE][WARN]useless release s4 slot1 status 0x00000000
Hi @GEdmunds, we are in the midst of testing and implementing the enable and disable of these logs. I will inform you once it is ready. Thank you
Hi @GEdmunds , As I look into this issue, I’d like to clarify the following:
- Could I confirm the exact example you’re running that shows this log?
I tested AmebaMultimedia → RTSPStreaming → VideoOnly, but my logs do not contain any [VOE] entries. VOE logs should be disabled by default.
My logs:
videoonly.zip (1.8 KB)
Thank you.
Hi - all of that console info comes from running: Multimedia – RTSP Streaming – Realtek IoT/Wi-Fi MCU Solutions
Thanks!
Hi @GEdmunds,
Thanks for the info, kindly try the newest SDK version or the prerelease version 4.0.9-build20250620, you should not be seeing [VOE] related logs. Meanwhile we will work on other logs. Thank you.
Input this to preference
https://github.com/Ameba-AIoT/ameba-arduino-pro2/raw/dev/Arduino_package/package_realtek_amebapro2_early_index.json
I’d really like to be able to disable all logs that come from drivers and includes other than things I’ve sent in particular. It’s really hard to pick out my own logs on the serial port when there are tens of thousands of “[ERROR] get_available Accept connection failed” messages to pick them out of. There are many more logs that I’d like to disable until I need them.
It’d be good to have both a “global disable RealTek logs” and have a method of enabling single logs.
I’ll second this - it would be great if there was a way to silence the messages, and what would really be great is to know what they mean.
An adjacent idea, that might be easier for RealTek to implement: Provide an include or other feature that will allow us to optionally globally channel all messages bound for Serial through a filter function of our own choice.
That would allow us to be very specific about what we let through, develop only-allow, only-reject or maybe even grep-like filtering for Serial messages.
Hi all,
Thanks for your feedbacks, we will look into this.
Dear all,
You may kindly try out the recent 4.1.0 pre-release version. We have include options to enable and disable some system logs.
Add to preference: https://github.com/Ameba-AIoT/ameba-arduino-pro2/raw/dev/Arduino_package/package_realtek_amebapro2_early_index.json
Note that we are currently still working on the log system to include more options for users to choose.
You may refer to these FAQ to enable or disable the logs.
- How can I control debug logs? — Ameba Arduino AIoT Documentation v1.1 documentation
- How do I disable the log UART by writing OTP? — Ameba Arduino AIoT Documentation v1.1 documentation
Thank you.
With 4.1.0-build20250924 and Arduino IDE Version: 2.3.6 Date: 2025-04-09T11:22:51.016Z
CLI Version: 1.2.0 for MacOS and Logs: Disable All - quite a bit of log information is still heading to the console. This happens on reboot. Do I need to do something differently?
10:44:22.524 →
10:44:22.524 → == Rtl8735b IoT Platform ==
10:44:22.524 →
10:44:22.524 → [Normal mode]
10:44:22.524 → BootFromNORFlash
10:44:22.524 → [Start Boot ROM…]
10:44:22.524 → === Load PARTBL ===
10:44:22.524 → === Load Done ===
10:44:22.524 → === Load ISP_IQ ===
10:44:22.524 → [fcs chk pass]
10:44:22.557 → ISP_IQ @ 0x8461080, 0x2ff80, 0x0
10:44:22.557 → mfcs_data version 0x00010001
10:44:22.557 → fcs_data version 0x00010101
10:44:22.557 → === Process ISP_IQ ===
10:44:22.557 → === Load Done ===
10:44:22.557 → === Load BL ===
10:44:22.557 → [Image Start Table @ 0x18200]
10:44:22.590 → === Load Done ===
10:44:22.622 →
10:44:22.622 → == Boot Loader ==
10:44:22.622 → Sep 5 2025:11:53:02
10:44:22.622 → === Load FCS Para ===
10:44:22.622 → === Load Done ===
10:44:22.622 → [crc pass]
10:44:22.622 → === Load ISP_IQ Sensor ===
10:44:22.622 → ISP_IQ @ 0x8461080, 0x2ff80
10:44:22.622 → === Process ISP_IQ ===
10:44:22.622 → === Load Done ===
10:44:22.622 → === Load FW1 ===
10:44:22.622 → FW_ISP_IQ @ 0x8061080, 0x31f80
10:44:22.622 → === Process FW_ISP_IQ ===
10:44:22.622 → DRAM_TYPE is DDR2 128MB.
10:44:22.622 → ddr_freq = 533
10:44:22.622 → VOE flash @ 0x8093080, 0x81f80
10:44:22.622 → FCS KM_status 0x00002081 err 0x0000200a
10:44:22.655 → Wait KM fcs done 0 us
10:44:22.655 → FCS TM_status 0x003f0000
10:44:22.655 → store fcs data for application
10:44:22.655 → It don’t do the sensor initial process
10:44:22.655 → RAM TM_STATUS 0x00bf1208 err 0x00001208
10:44:22.655 → read fcs_status 0x000000bf
10:44:22.688 → read fcs_status 0x000000bf
10:44:22.688 → === Process VOE IMG ===
10:44:22.688 → [Image Start Table @ 0x20106200]
10:44:22.688 → RAM Load @ 0x8115100->0x20106200, 0x5d44
10:44:22.787 → DDR Load @ 0x811b080->0x70100000, 0x1b38d8
10:44:22.787 → === FW Load Done ===
10:44:22.787 →
10:44:22.787 → Boot Loader <==
10:44:22.818 →
10:44:22.818 → == RAM Start ==
10:44:22.818 → Build @ 18:41:56, Sep 23 2025
10:44:22.818 →
10:44:22.818 → interface 0 is initialized
10:44:22.818 →
interface 1 is initialized
10:44:22.818 →
cfg_size_lib = 120, cfg_size_user = 120
10:44:22.818 →
10:44:22.818 →
Initializing WIFI …[Driver]: [HALMAC]
10:44:22.818 →
11692M HALMAC_MAJOR_VER = 1
10:44:22.818 →
HALMAC_PROTOTYPE_VER = 4
10:44:22.852 →
HALMAC_MINOR_VER = 20
10:44:22.852 →
HALMAC_PATCH_VER =
10:44:22.852 →
[Driver]: The driver include MP
10:44:22.885 →
[Driver]: Ver = libwlan:2025.09.23.19.07_b_afdf9ed0d9a9e321aa5af8032c118051a9588d3d
10:44:22.885 →
RFE type = 0
10:44:22.918 →
start_addr=(0x4000), end_addr=(0x8000), buffer_size=(0x4000), smp_number_max=(2048)
10:44:22.951 →
10:44:22.984 →
WIFI initialized
10:44:22.984 →
10:44:22.984 →
[Driver]: set ssid [Transport5]
10:44:22.984 →
[Driver]: rtw_joinbss_cmd MGMT_FRAME_PROTECTION_OPTIONAL no pmf.
10:44:27.074 →
[Driver]: Bcn (ie: 358, rsn: 0, wpa: 0) ch: 149, seq: 1877, ts: 261487718454
10:44:27.270 →
10:44:27.270 →
[Driver]: start auth to f0:09:0d:51:ad:a0
10:44:27.270 →
10:44:27.270 →
[Driver]: auth success, start assoc
10:44:27.270 →
[Driver]: listen_interval: 10, bcn_interval: 100
10:44:27.270 →
10:44:27.270 →
[Driver]: association success(res=4)
10:44:27.270 →
10:44:27.270 →
[Driver]: set pairwise key to hw: alg:4(WEP40-1 WEP104-5 TKIP-2 AES-4)
10:44:27.302 →
10:44:27.302 →
[Driver]: set group key to hw: alg:4(WEP40-1 WEP104-5 TKIP-2 AES-4) keyid:2
10:44:27.302 →
(0) Scan: 1, Auth: 1, Assoc: 1, 4way: 1, connect: 1, reason: 0
10:44:27.302 →
[Driver]: TSFValue = 261489459254, tsf = 0, shift_set= 0x8000, bcn int = 100
10:44:28.291 →
10:44:28.291 →
10:44:28.850 →
Interface 0 IP address : 192.168.1.121
10:44:28.850 →
[LwIP_DHCP] dhcp offered_t0_lease: 86400
10:44:30.863 →
RTSP[0] port: 554
10:44:30.863 →
connect successful sta mode
10:44:30.863 →
10:44:30.863 →
rtsp stream enabled
To turn off the following logs,
== Rtl8735b IoT Platform ==
Chip VID: 0, Ver: 0
ROM Version: v3.0[Normal mode]
BootFromNORFlash
[Start Boot ROM…]
=== Load PARTBL ===
=== Load Done ===
=== Load ISP_IQ ===
[fcs chk pass]
ISP_IQ @ 0x8461080, 0x2ff80, 0x0
mfcs_data version 0x00010001
fcs_data version 0x00010101
=== Process ISP_IQ ===
=== Load Done ===
=== Load BL ===
[Image Start Table @ 0x18200]
=== Load Done ===== Boot Loader ==
Sep 5 2025:11:53:02
=== Load FCS Para ===
=== Load Done ===
[crc pass]
=== Load ISP_IQ Sensor ===
ISP_IQ @ 0x8461080, 0x2ff80
=== Process ISP_IQ ===
=== Load Done ===
=== Load FW1 ===
FW_ISP_IQ @ 0x8061080, 0x31f80
=== Process FW_ISP_IQ ===
DRAM_TYPE is DDR2 128MB.
ddr_freq = 533
VOE flash @ 0x8093080, 0x81f80
FCS KM_status 0x00002081 err 0x0000200a
Wait KM fcs done 0 us
FCS TM_status 0x00000001
store fcs data for application
It don’t do the sensor initial process
=== Process VOE IMG ===
[Image Start Table @ 0x20106200]
RAM Load @ 0x8115100->0x20106200, 0x5cc4
DDR Load @ 0x811b080->0x70100000, 0x1b1f58
=== FW Load Done ===Boot Loader <==
You can refer to How do I disable the log UART by writing OTP? — Ameba Arduino AIoT Documentation v1.1 documentation
You can turn it off by applying otp_rom_log_message_disable(); in main. However, OTP has a limited number of writes. Avoid repeatedly toggling between enable and disable.
Navigate to main.cpp in cores/ambpro2:
Add the following,
Remove this function after it has been executed. You don’t need to include it every time you upload your code—just run it once. If logs still appear after uploading the code, reopen the Serial Monitor/IDE, then press the reset button on the board.
After you applied otp_rom_log_message_disable(); and choose Disable all (Soft Mute), you will expect the output. This is the first version of log systems which disable the multimedia’s logs, It is expected that you will still see the WiFi driver related logs.
== RAM Start ==Build @ 18:41:56, Sep 23 2025
$8735b>Attempting to connect to WPA SSID: Network_SSIDinterface 0 is initializedinterface 1 is initializedcfg_size_lib = 120, cfg_size_user = 120
Initializing WIFI …[Driver]: [HALMAC]11692M HALMAC_MAJOR_VER = 1HALMAC_PROTOTYPE_VER = 4HALMAC_MINOR_VER = 20HALMAC_PATCH_VER =[Driver]: The driver include MP[Driver]: Ver = libwlan:2025.09.23.19.07_b_afdf9ed0d9a9e321aa5af8032c118051a9588d3dRFE type = 0start_addr=(0x4000), end_addr=(0x8000), buffer_size=(0x4000), smp_number_max=(2048)
WIFI initialized
[Driver]: set ssid [Network_SSID][Driver]: rtw_joinbss_cmd MGMT_FRAME_PROTECTION_OPTIONAL no pmf.[Driver]: Bcn (ie: 331, rsn: 0, wpa: 0) ch: 11, seq: 783, ts: 201503027623
[Driver]: start auth to 7c:a1:77:9e:1e:20
[Driver]: auth success, start assoc[Driver]: listen_interval: 10, bcn_interval: 100
[Driver]: association success(res=2)
[Driver]: set pairwise key to hw: alg:4(WEP40-1 WEP104-5 TKIP-2 AES-4)
[Driver]: set group key to hw: alg:4(WEP40-1 WEP104-5 TKIP-2 AES-4) keyid:1(0) Scan: 1, Auth: 1, Assoc: 1, 4way: 1, connect: 1, reason: 0
Interface 0 IP address : 192.168.3.3[LwIP_DHCP] dhcp offered_t0_lease: 86400[Driver]: TSFValue = 201507635582, tsf = 0, shift_set= 0x8000, bcn int = 100
RTSP[0] port: 554connect successful sta mode
rtsp stream enabled
Hi all,
Kindly try another version of our Arduino SDK pre release version - AmebaPro2@4.1.0-build20250930.
Refer to Getting started to know more about the options.