<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックRe: IMX93 EVK UUU flash failed</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1906858#M226109</link>
    <description>&lt;P&gt;Hi Chavira,&lt;/P&gt;&lt;P&gt;can you clarify how I can detect if I have an "A0" revision of the silicon? The reason I'm asking is that I have trouble using uuu (either from Linux or Windows) on my IMX93EVK.&lt;/P&gt;&lt;P&gt;I checked all the docs that I can find, but I do not see how to do this.&amp;nbsp; The reference manual lists the DIGPROG_DEVICE_ID but no description of the values and in U-Boot I see that the info printed for the CPU version comes from EdgeLock Secure Enclave but also without any documentation as to what values refer to what version.&lt;/P&gt;&lt;P&gt;This is what U-Boot prints on my hardware with the 6.1.22 release which I can run from SD card (the 6.6.23 release does not even start):&lt;/P&gt;&lt;P&gt;U-Boot 2023.04-lf_v2023.04+gaf7d004eaf (Jun 06 2023 - 14:59:40 +0000)&lt;BR /&gt;&lt;BR /&gt;CPU: i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz)&lt;BR /&gt;CPU: Consumer temperature grade (0C to 95C) at 41C&lt;BR /&gt;Reset cause: POR (0x1)&lt;BR /&gt;Model: NXP i.MX93 11X11 EVK board&lt;BR /&gt;DRAM: 2 GiB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also in this release uuu (latest revision and I tested a few before that) hangs like this:&lt;/P&gt;&lt;P&gt;uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.182-0-gda3cd53&lt;/P&gt;&lt;P&gt;Success 0 Failure 0&lt;BR /&gt;&lt;BR /&gt;1:44-F0262AD 1/ 1 [=================100%=================] SDPS: boot -scanterm -f uuu.auto-imx93evk -scanlimi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, the package of my EVK says "MCIMX93-EVKCM".&amp;nbsp; What does that CM at the end mean?&amp;nbsp; I found only spurious hits on the internet, but no explanation to what the differences may be.&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jul 2024 08:24:37 GMT</pubDate>
    <dc:creator>laodzu</dc:creator>
    <dc:date>2024-07-12T08:24:37Z</dc:date>
    <item>
      <title>IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1825339#M221061</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am following the IMX93EVK getting started guide (&lt;A href="https://www.nxp.com/document/guide/getting-started-with-the-i-mx93-evk:GS-IMX93EVK?section=get-software" target="_blank"&gt;Getting Started with the i.MX93 EVK | NXP Semiconductors&lt;/A&gt;). But I am stuck at flashing BSP with UUU. I have downloaded the&amp;nbsp;LF_v6.1.55-2.2.0_images_IMX93EVK BSP which is available in NXP website and switched the boot mode to serial download.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am working with UUU in WSL. I have copied the BSP and unzip it in the mfgtools/uuu directory. Then I have executed the following command:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;sudo ./uuu -v uuu.auto-imx93evk&lt;/LI-CODE&gt;&lt;P&gt;But it fails, this is the error:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.165-9-gb407608

Build in config:
        Pctl     Chip            Vid     Pid     BcdVersion      Serial_No
        ==================================================
        SDPS:    MX8QXP          0x1fc9  0x012f  [0x0002..0xffff]
        SDPS:    MX8QM           0x1fc9  0x0129  [0x0002..0xffff]
        SDPS:    MX8DXL          0x1fc9  0x0147
        SDPS:    MX28            0x15a2  0x004f
        SDPS:    MX815           0x1fc9  0x013e
        SDPS:    MX865           0x1fc9  0x0146
        SDPS:    MX8ULP          0x1fc9  0x014a
        SDPS:    MX8ULP          0x1fc9  0x014b
        SDPS:    MX93            0x1fc9  0x014e
        SDPS:    MX95            0x1fc9  0x015d
        SDP:     MX7D            0x15a2  0x0076
        SDP:     MX6Q            0x15a2  0x0054
        SDP:     MX6D            0x15a2  0x0061
        SDP:     MX6SL           0x15a2  0x0063
        SDP:     MX6SX           0x15a2  0x0071
        SDP:     MX6UL           0x15a2  0x007d
        SDP:     MX6ULL          0x15a2  0x0080
        SDP:     MX6SLL          0x1fc9  0x0128
        SDP:     MX7ULP          0x1fc9  0x0126
        SDP:     MXRT106X        0x1fc9  0x0135
        SDP:     MX8MM           0x1fc9  0x0134
        SDP:     MX8MQ           0x1fc9  0x012b
        SDPU:    SPL             0x0525  0xb4a4  [0x0000..0x04ff]
        SDPV:    SPL1            0x0525  0xb4a4  [0x0500..0x9998]
        SDPV:    SPL1            0x1fc9  0x0151  [0x0500..0x9998]
        SDPU:    SPL             0x0525  0xb4a4  [0x9999..0x9999]
        SDPU:    SPL             0x3016  0x1001  [0x0000..0x04ff]
        SDPV:    SPL1            0x3016  0x1001  [0x0500..0x9998]
        FBK:                     0x066f  0x9afe
        FBK:                     0x066f  0x9bff
        FBK:                     0x1fc9  0x0153
        FB:                      0x0525  0xa4a5
        FB:                      0x18d1  0x0d02
        FB:                      0x3016  0x0001
        FB:                      0x1fc9  0x0152
        FB:                      0x0483  0x0afb
Wait for Known USB Device Appear...
New USB Device Attached at 1:1-00B5BA70F65142FA
1:1-00B5BA70F65142FA&amp;gt;Start Cmd:SDPS: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot
3%1:1-00B5BA70F65142FA&amp;gt;Fail HID(W):LIBUSB_ERROR_IO(0.077s)&lt;/LI-CODE&gt;&lt;P&gt;In the getting started guide it seems pretty straightforward, but I think I am missing something. What could cause the error?&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Gorka.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 16:10:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1825339#M221061</guid>
      <dc:creator>Gorka_3</dc:creator>
      <dc:date>2024-03-11T16:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1825402#M221063</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222802"&gt;@Gorka_3&lt;/a&gt;!&lt;/P&gt;
&lt;P&gt;Thank you for contacting NXP Support!&lt;BR clear="none" /&gt;&amp;nbsp;&lt;BR clear="none" /&gt;I think you are doing well with the download.&lt;BR clear="none" /&gt;&amp;nbsp;&lt;BR clear="none" /&gt;What version of Linux are you trying to flash on your evk?&lt;BR clear="none" /&gt;&amp;nbsp;&lt;BR clear="none" /&gt;Some boards have the A0 silicon version and this version of the silicon is not compatible with kernel 6.1.36 and later.&lt;BR clear="none" /&gt;&amp;nbsp;&lt;BR clear="none" /&gt;Please try to flash the kernel version 6.1.22 or 6.1.1&lt;BR clear="none" /&gt;&amp;nbsp;&lt;BR clear="none" /&gt;Sorry for the mistake!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 17:42:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1825402#M221063</guid>
      <dc:creator>Chavira</dc:creator>
      <dc:date>2024-03-11T17:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826096#M221120</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;thank your for your response.&lt;/P&gt;&lt;P&gt;I have just tried to repeat the process with both the "LF_v6.1.1_1.0.0_images_IMX93EVK.zip" and "LF_v6.1.22-2.0.0_images_IMX93EVK.zip" but the issue remains. I attach the output of serial debug if it helps.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;U-Boot SPL 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000)
SOC: 0xa0009300
LC: 0x40010
M33 prepare ok
Normal Boot
Trying to boot from BOOTROM
Boot Stage: USB boot
Find img info 0x&amp;amp;88000000, size 416
Download 1610752, Total size 1611776
NOTICE:  BL31: v2.6(release):android-13.0.0_1.2.0-rc1-4-g616a4588f
NOTICE:  BL31: Built : 10:31:38, Mar  1 2023


U-Boot 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000)

CPU:   i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz)
CPU:   Consumer temperature grade (0C to 95C) at 36C
Reset cause: POR (0x1)
Model: NXP i.MX93 11X11 EVK board
DRAM:  2 GiB
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x52]
SNK.Power3.0 on CC2
tcpc_pd_receive_message: Polling ALERT register, TCPC_ALERT_RX_STATUS bit failed, ret = -62
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x51]
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x50]
Core:  209 devices, 29 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from nowhere... OK
[*]-Video Link 0adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c
fail to probe panel device hdmi@3d
fail to get display timings
probe video device failed, ret -19

        [0] lcd-controller@4ae30000, video
        [1] dsi@4ae10000, video_bridge
        [2] hdmi@3d, panel
adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c
fail to probe panel device hdmi@3d
fail to get display timings
probe video device failed, ret -19
In:    serial
Out:   serial
Err:   serial

BuildInfo:
  - ELE firmware version 0.0.9-9df0f503

switch to partitions #0, OK
mmc1 is current device
UID: 0x70bab500 0xfa4251f6 0x75f56085 0xa3dff159
Detect USB boot. Will enter fastboot mode!
Net:   eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME]
Fastboot: Normal
Boot from USB for mfgtools
*** Warning - Use default environment for                                mfgtools
, using default environment

Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot auto; fi;
Hit any key to stop autoboot:  0

## Checking Image at 83800000 ...
Unknown image format!
Run fastboot ...
auto usb 0&lt;/LI-CODE&gt;&lt;P&gt;And the process gets stucked as in my original post.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ sudo ./uuu -v LF_v6.1.1_1.0.0_images_IMX93EVK.zip
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.165-9-gb407608

Build in config:
        Pctl     Chip            Vid     Pid     BcdVersion      Serial_No
        ==================================================
        SDPS:    MX8QXP          0x1fc9  0x012f  [0x0002..0xffff]
        SDPS:    MX8QM           0x1fc9  0x0129  [0x0002..0xffff]
        SDPS:    MX8DXL          0x1fc9  0x0147
        SDPS:    MX28            0x15a2  0x004f
        SDPS:    MX815           0x1fc9  0x013e
        SDPS:    MX865           0x1fc9  0x0146
        SDPS:    MX8ULP          0x1fc9  0x014a
        SDPS:    MX8ULP          0x1fc9  0x014b
        SDPS:    MX93            0x1fc9  0x014e
        SDPS:    MX95            0x1fc9  0x015d
        SDP:     MX7D            0x15a2  0x0076
        SDP:     MX6Q            0x15a2  0x0054
        SDP:     MX6D            0x15a2  0x0061
        SDP:     MX6SL           0x15a2  0x0063
        SDP:     MX6SX           0x15a2  0x0071
        SDP:     MX6UL           0x15a2  0x007d
        SDP:     MX6ULL          0x15a2  0x0080
        SDP:     MX6SLL          0x1fc9  0x0128
        SDP:     MX7ULP          0x1fc9  0x0126
        SDP:     MXRT106X        0x1fc9  0x0135
        SDP:     MX8MM           0x1fc9  0x0134
        SDP:     MX8MQ           0x1fc9  0x012b
        SDPU:    SPL             0x0525  0xb4a4  [0x0000..0x04ff]
        SDPV:    SPL1            0x0525  0xb4a4  [0x0500..0x9998]
        SDPV:    SPL1            0x1fc9  0x0151  [0x0500..0x9998]
        SDPU:    SPL             0x0525  0xb4a4  [0x9999..0x9999]
        SDPU:    SPL             0x3016  0x1001  [0x0000..0x04ff]
        SDPV:    SPL1            0x3016  0x1001  [0x0500..0x9998]
        FBK:                     0x066f  0x9afe
        FBK:                     0x066f  0x9bff
        FBK:                     0x1fc9  0x0153
        FB:                      0x0525  0xa4a5
        FB:                      0x18d1  0x0d02
        FB:                      0x3016  0x0001
        FB:                      0x1fc9  0x0152
        FB:                      0x0483  0x0afb
Wait for Known USB Device Appear...
Decompress file:uuu.auto
100%New USB Device Attached at 1:1-00B5BA70F65142FA
1:1-00B5BA70F65142FA&amp;gt;Start Cmd:SDPS: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot
Decompress file:imx-boot-imx93evk-sd.bin-flash_singleboot
100%1:1-00B5BA70F65142FA&amp;gt;Okay (5.064s)&lt;/LI-CODE&gt;&lt;P&gt;I want to remark again that I am working in WSL, and that whenever I want to attach the EVK USB to WSL I have to share it in PowerShell.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2024 10:41:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826096#M221120</guid>
      <dc:creator>Gorka_3</dc:creator>
      <dc:date>2024-03-12T10:41:16Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826238#M221134</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222802"&gt;@Gorka_3&lt;/a&gt;&amp;nbsp;!&lt;BR /&gt;&lt;BR /&gt;Try to unzip the file and put this command:&lt;BR /&gt;&lt;BR /&gt;Uuu -b emmc_all imx-boot-imx93evk-sd.bin-flash_singleboot imx-image-full.wic&lt;BR /&gt;&lt;BR /&gt;Notes:&lt;BR /&gt;You can change emmc_all for sd_all if you want to boot from SD Card.&lt;BR /&gt;Check the name of the .wic file&lt;BR /&gt;Use Powershell if you are on Windows&lt;BR /&gt;&lt;BR /&gt;Best Regards!&lt;BR /&gt;Chavira&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2024 13:24:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826238#M221134</guid>
      <dc:creator>Chavira</dc:creator>
      <dc:date>2024-03-12T13:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826260#M221138</link>
      <description>Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206761"&gt;@Chavira&lt;/a&gt;&lt;BR /&gt;I have realised about something. Inmediatly after executing uuu command and attaching the USB to WSL, if I check the USB status it shows as "attached" (which is good). But if I check it again once that uuu is clearly freezed (once that debug port has shown what I previously posted) the USB appears as not attached!&lt;BR /&gt;&lt;BR /&gt;It seems that uuu uses the USB, then it resets the USB or something, but since I am working in WSL and have to attach the USB manually, uuu doesn't find the USB and therefore freezes (I guess so).&lt;BR /&gt;&lt;BR /&gt;Maybe a solution would be to execute uuu from native Windows as you have said (in PowerShell).&lt;BR /&gt;&lt;BR /&gt;As far as I know UUU is for Windows 10 but no for Windows 11 (my current version). Is there a way to execute UUU from Windows 11 so that I don't have to manage the USB manually?</description>
      <pubDate>Tue, 12 Mar 2024 13:45:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826260#M221138</guid>
      <dc:creator>Gorka_3</dc:creator>
      <dc:date>2024-03-12T13:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826276#M221140</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222802"&gt;@Gorka_3&lt;/a&gt;!&lt;BR /&gt;Thank you for contacting NXP Support!&lt;BR /&gt;&lt;BR /&gt;You can use the uuu tool on Windows 11 without problems.&lt;BR /&gt;&lt;BR /&gt;I use Windows 11 too.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2024 14:03:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826276#M221140</guid>
      <dc:creator>Chavira</dc:creator>
      <dc:date>2024-03-12T14:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826280#M221142</link>
      <description>Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206761"&gt;@Chavira&lt;/a&gt;,&lt;BR /&gt;I have successfully executed UUU in PS. The flashing went without failure and the content in my home directory has been erased (so the image has been overwrited).&lt;BR /&gt;&lt;BR /&gt;Thank your very much for your support :smilyface:</description>
      <pubDate>Tue, 12 Mar 2024 14:09:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1826280#M221142</guid>
      <dc:creator>Gorka_3</dc:creator>
      <dc:date>2024-03-12T14:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: IMX93 EVK UUU flash failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1906858#M226109</link>
      <description>&lt;P&gt;Hi Chavira,&lt;/P&gt;&lt;P&gt;can you clarify how I can detect if I have an "A0" revision of the silicon? The reason I'm asking is that I have trouble using uuu (either from Linux or Windows) on my IMX93EVK.&lt;/P&gt;&lt;P&gt;I checked all the docs that I can find, but I do not see how to do this.&amp;nbsp; The reference manual lists the DIGPROG_DEVICE_ID but no description of the values and in U-Boot I see that the info printed for the CPU version comes from EdgeLock Secure Enclave but also without any documentation as to what values refer to what version.&lt;/P&gt;&lt;P&gt;This is what U-Boot prints on my hardware with the 6.1.22 release which I can run from SD card (the 6.6.23 release does not even start):&lt;/P&gt;&lt;P&gt;U-Boot 2023.04-lf_v2023.04+gaf7d004eaf (Jun 06 2023 - 14:59:40 +0000)&lt;BR /&gt;&lt;BR /&gt;CPU: i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz)&lt;BR /&gt;CPU: Consumer temperature grade (0C to 95C) at 41C&lt;BR /&gt;Reset cause: POR (0x1)&lt;BR /&gt;Model: NXP i.MX93 11X11 EVK board&lt;BR /&gt;DRAM: 2 GiB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also in this release uuu (latest revision and I tested a few before that) hangs like this:&lt;/P&gt;&lt;P&gt;uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.182-0-gda3cd53&lt;/P&gt;&lt;P&gt;Success 0 Failure 0&lt;BR /&gt;&lt;BR /&gt;1:44-F0262AD 1/ 1 [=================100%=================] SDPS: boot -scanterm -f uuu.auto-imx93evk -scanlimi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, the package of my EVK says "MCIMX93-EVKCM".&amp;nbsp; What does that CM at the end mean?&amp;nbsp; I found only spurious hits on the internet, but no explanation to what the differences may be.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 08:24:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX93-EVK-UUU-flash-failed/m-p/1906858#M226109</guid>
      <dc:creator>laodzu</dc:creator>
      <dc:date>2024-07-12T08:24:37Z</dc:date>
    </item>
  </channel>
</rss>

