GD32F350CBT6 Support

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • GD32F350CBT6 Support

      Hi,

      Just trying to flash a GD32F350CBT6 but there doesn't seem to be that specific device in the selection.I tried the similar part numbers with similar specifications but all failed.

      I went searching and found the following "GD32F3x0.FLM" from GD and added it to the Jlink XML device list and could then select the specific device but i just get various errors and can't even seem to connect to the device (unlike with the other mismatched devices which do connect)

      Am I missing something obvious? I'm very much a beginner here so please go easy on me. If providing the above mentioned files helps let me know and i'll upload.

      Thanks.
    • Hello,

      Thank you for your inquiry.
      Such an issue is not known to us.
      The GD32F350CB is supported by J-Link:
      segger.com/downloads/supported-devices.php


      Could you provide your J-Link S/N for reference?

      What softwaretool did you use to try flashing?

      The FLM is not needed. We do not recommend to change anything in the XML files.
      Are you using an eval boar? If yes which one?

      Best regards,
      Nino
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/

      Or you can contact us via e-mail.
    • I'm using J-Flash

      I see.... the GD32F350CB selection only lists 64KB size and See no option of changing this, whereas the GD32F350CBT6 is 128KB, so suppose this doesn't matter?


      If I use the default settings after selecting GD32F350CB and attempt to read it reports the following ,

      - Device "GD32F350CB" selected........
      Display Spoiler

      - Target interface speed: 4000 kHz (Fixed)
      - VTarget = 3.293V
      - Found SW-DP with ID 0x2BA01477
      - DPv0 detected
      - Scanning AP map to find all available APs
      - AP[1]: Stopped AP scan as end of AP map has been reached
      - AP[0]: AHB-AP (IDR: 0x24770011)
      - Iterating through AP map to find AHB-AP to use
      - AP[0]: Core found
      - AP[0]: AHB-AP ROM base: 0xE00FF000
      - CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
      - Found Cortex-M4 r0p1, Little endian.
      - FPUnit: 0 code (BP) slots and 0 literal slots
      - CoreSight components:
      - ROMTbl[0] @ E00FF000
      - ROMTbl[0][1]: E000E000, CID: 05E00D00, PID: 0BB00C00 ???
      - ROMTbl[0][2]: E0001000, CID: 05E00D00, PID: 3BB00205 ???
      - ROMTbl[0][3]: E0002000, CID: 05E00D00, PID: 2BB00305 ???
      - ROMTbl[0][4]: E0000000, CID: 05E00D00, PID: 3BB00105 ???
      - ROMTbl[0][5]: E0040000, CID: 05900D00, PID: 0BB9A105 ???
      - Executing init sequence ...
      - Initialized successfully
      - Target interface speed: 4000 kHz (Fixed)
      - Found 1 JTAG device. Core ID: 0x2BA01477 (None)
      - Connected successfully
      Reading entire flash chip ...
      - 64 sectors, 1 range, 0x8000000 - 0x800FFFF
      - Start of preparing flash programming
      - ERROR: Verification of RAMCode failed @ address 0x20000000.
      Write: 0xA801BE00 F0009900
      Read: 0x00030003 A801BE00
      - ERROR: Failed to prepare for programming.
      Failed to download RAMCode!
      - End of preparing flash programming
      - Start of restoring
      - End of restoring
      - ERROR: Failed to read back target memory
      Disconnecting ...
      - Disconnected



      This isn't a generic dev/eval board
    • Don't know if this means anything or gives a clue, but I adjusted the speed to 200Khz in the same project and the following changed as compared with the above in the log

      - CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
      - Found Cortex-M4 r0p1, Little endian.
      - FPUnit: 6 code (BP) slots and 2 literal slots
      - CoreSight components:
      - ROMTbl[0] @ E00FF000
      - ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
      - ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
      - ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
      - ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
      - ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
      - Executing init sequence ...
      - Initialized successfully

      Edit: I've been told Read protect is enabled on the target, no idea if this is the possible issue here.... Checking Jflash and the options to unsecure appear to be greyed out for GD32F350CB device.

      Going through Jcommander and reading the (presumed) option bytes (?) regarding this and suggests it's not read protected
      IE: mem 0x1ffff800 10 which returns the first two bytes as A5 5A


      ...... but if i select a comparable STM32 device in J-Flash it claims witha popup that it is indeed protected ?(

      The post was edited 3 times, last by Severence ().

    • So i set everything up in Keil uVision5 and programmed the .hex file their, it was sucsessful and i was then able to read back the entire flash within J-Flash (though i had to specify the range)

      I'm still unable to do the programming via J-Flash though..... bit mythed about this ?(

      The post was edited 1 time, last by Severence ().

    • Hi,
      Sorry for the delay in response.
      This is odd.

      Could you please provide us with a sample .hex file and a J-Flash project for reproduction purposes?

      Best regards,
      Fabian
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/


      Or you can contact us via e-mail.
    • Hi Fabian,

      Thanks for the help.

      I'm not sure this is an issue with my bin/hex files as it doesn't matter what I'm attempting to write, it could be anything and it will fail, nevertheless I've attached it.

      The Project is just all defaults after selecting GD32F350CB and I've tried various versions of the software.

      I can consistently and repeatably write or erase via Keil.
      Files
      • bootloader.hex

        (26.86 kB, downloaded 33 times, last: )