BDT reading flash memory

wes58

I am using BDT release_v5.9.4 and trying to read Flash memory - chip TLSR8258 and TL7218. When I use "Command Line Input" and use the following command to read 16 bytes and save data to a file: `B85 rf FF000 -s 16 -o "d:\\TelinkIoTStudio\\BDT\\Zg2_ff000.bin"` Result in BDT: **[10:18:14]: TC32 EVK: Swire ok 16 byte(s) have finished 000ff000: 32 00 e0 38 c1 a4 c6 9c ff ff ff ff ff ff ff ff Total time: 969 ms** The read data in only displayed on the screen and not saved to a file that I specified. If I want to read more data: `B85 rf F7000 -s 1k -o "d:\\TelinkIoTStudio\\BDT\\Zg2_f7000.bin"` Result in BDT; **[10:18:59]: TC32 EVK: Swire ok 1024 byte(s) have finished All 1024 byte(s) have been saved to config\user\Read.bin Total time: 978 ms** It tells me that the file was saved as Read.bin and saved in config\user folder. Which is not true. The file is saved with the name that I specified on the command line and in the folder specified. The displayed information is confusing. There was no such problems when I used BDT v5.7.9 in the past. Even when I tried to read 16bytes, the result was saved to the file specified. On BDT screen it always displayed that data has been saved to a file, not confusing with saying what was shown above. The second issue/question I have is: How do you read Flash Memory if you want to debug running program? For example if you have a variable displayed in the Debug tab which is a pointer to the memory, you want to read this memory. When you try to do it through BDT menu "Memory Access" and specify memory address and number of bytes to read, the program crashes - going to the loop at whatever address it currently is. I tried to pause the program before reading memory but the same thing happened. I haven't tried to use "Stall MCU" so I don't know if that would work. **So the question is how to access Flash Memory during debugging without program crashing?** I haven't tried reading any other areas of memory - core, analog etc. - so I don't know if it is the same issue as reading Flash. I am pretty sure that it was working in the past. It was a couple of year ago when I did it with TLSR8258

TL_MINGSEN

Hello, we have already noted the first issue you reported. We will fix it in the next version. Regarding the second issue, in BDT, the memory access for Flash is done through an indirect access method. That is to say, we will pre-download a SRAM program and make it run, and then interact with this SRAM program to achieve flash reading and writing. When you are running a flash program and try to access a flash memory again, BDT will disrupt your current running environment. If you access SRAM or Analog, there will be no such problem. You can try modifying BDT/config/system.ini's read_write_direct = True to operate the flash through the register method, thereby not affecting the current environment.

wes58

Thank you for your help. Changing read_write_direct to True works. I have another 2 questions. What setting in BDT or during compilation decides whether application can be "paused", "step", "run"? It is the first time I noticed that those option are grayed out and can't be used. I compiled an example "feature_test" and "TEST_EXT_ADV" in BLE SDK and TL7218 chip and I get what you can see below: [d](data/attachment/forum/202609/08/053607dvlhpwh79l5hynzz.png) As you can see the only option available is "PC" I just noticed that this happens when I select TL721x. When I choose B85 everhing is available. Does it mean that you can't pause/step the program with TL721x? Second question regarding config.ini in BDT I only use TLSR8258 and TL7218. How can I modify config.ini to have an option to choose only between those 2 chips? I tried to delete everything except those 2 MCU, but it doesn't work. `[MCU] ` `TYPE 0x22 0x0c = B85                \bin\dut_b85_flash_v0004.bin        40000         b010b010        End ` `TYPE 0x35 0x14 = TL721X  \bin\dut_tl721x_flash_v0005.bin 00040000 b005b010    \bin\dut_tl721x_otp_v0001.bin        End ` `default = B85  End` Even replacing 0x0c wiht 0x1 and 0x14 with 0x2 doesn't work either. <div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102356&ptid=98604" target="_blank"><font color="#999999">TL_MINGSEN 发表于 2026-9-7 15:34</font></a></font><br /> Hello, we have already noted the first issue you reported. We will fix it in the next version. Regar ...</blockquote></div><br /> <br />

TL_MINGSEN

Hi,for the first question,TL721X and other chips that use Risv-V MCU which don't support debugging via single wire, so the BDT tool interface grayscales the Run/Pause/Step functions, while the B85/B87 uses a TC Core that supports these functions. For the second question,you can use the config.ini file I sent as an attachment. I have tested it and found that it works properly.[](https://) [config.7z](https://forum.telink-semi.cn/forum.php?mod=attachment&aid=MjE0N3w4MGE1NTE5OHwxNzg4ODMyOTQwfDYwfDA%3D)

wes58

Thank you for your response but config.ini file didn't work for me. Here are results: **->Download** [16:53:30]: Error<0x1101>: DUT command execute error **->Activate** [16:53:36]: Activate MCU error Error<0x1002>: EVK command result error **->Unlock** [16:53:46]: Error<0x1207>: File not exist **->Reset** [16:53:59]: TC32 EVK: Swire ok Reset MCU ok [16:53:59]: Total time: 182 ms **->Activate** [16:54:03]: Activate MCU ok [16:54:05]: Total time: 1370 ms **->Download** [16:54:15]: Error<0x1101>: DUT command execute error What I found out in the past when I tried it, was that I can delete all MCUs after TL721x and it works. When I tried to delete even just one MCU from the beginning of the list it didn't work any more. <div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102367&ptid=98604" target="_blank"><font color="#999999">TL_MINGSEN 发表于 2026-9-8 10:02</font></a></font><br /> Hi,for the first question,TL721X and other chips that use Risv-V MCU which don't support debugging v ...</blockquote></div><br />

TL_MINGSEN

 I know where the problem lies. The Index of the chip must be from 0x01 to 0x02 (as shown in the box in the figure). Additionally, you need to find the dut bin names of B85 and TL721X in your BDT/config/bin directory, and then match them with the 2 name circled in the figure. This will ensure the normal operation. 

wes58

<div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102379&ptid=98604" target="_blank"><font color="#999999">TL_MINGSEN 发表于 2026-9-8 15:59</font></a></font>  I know where the problem l ...</blockquote></div> Thanks. I will try that.

TL_MINGSEN

😄 <div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102381&ptid=98604" target="_blank"><font color="#999999">wes58 发表于 2026-9-8 16:39</font></a></font><br /> Thanks. I will try that.</blockquote></div><br />