can't use toolbox to program DA14585 development kit basic

Hello,

1. Trying to use SmartSnippets Toolbox v5.0.22 to program my DA14585 development kit, able to connect but can't flash or read:

2. How do I configure my development kit basic + toolbox to program an external device (ISM14585)? 

Parents
  • Hi Joe,

    Thank you for posting your question online.
    You are trying to program your DA14585 Daughterboard via JTAG or UART?

    How do I configure my development kit basic + toolbox to program an external device (ISM14585)? 

    By external device you are referring on the DA14585 Daughterboard or another custom board?

    Kind Regards,
    OV_Renesas

Reply
  • Hi Joe,

    Thank you for posting your question online.
    You are trying to program your DA14585 Daughterboard via JTAG or UART?

    How do I configure my development kit basic + toolbox to program an external device (ISM14585)? 

    By external device you are referring on the DA14585 Daughterboard or another custom board?

    Kind Regards,
    OV_Renesas

Children
  • Hi,

    I believe I am programming via JTAG.

    By external device I mean another custom board. But I'm also interested in why I couldn't use Toolbox to program the dev kit's DA14585 (the one on the dev kit itself).

    Thanks.

  • HI Joe,

    Thank you for the reply.
    Regarding the DA14585 Development Kit Basic:
    Please refer on UM-B-048, on chapter 4.2 Configuring the Basic Kit Board by Jumper Settings, on page:6. 
    Have you set the Jumper for SWD interface and in order to boot from External SPI memory?

    Regarding your custom board:
    The DA14585 Development Kit Basic has an MCU with SEGGER License, so by connecting the SWD pins (SWDIO, SWDCLK) along with Vcc and Ground you should be able to program your custom board as well.


    Kind Regards,
    OV_Renesas

  • Hi OV_Renesas,

    Thank you so much for your prompt response. I very much appreciate the quick responses, and hope you can help me and resolve these issues.

    1. In regards to programming the dev kits DA14585 via toolbox:

    I've tried to adhere to the datasheet, but I still cannot read or erase: Perhaps there's very specific pinouts I need for the board setup?

    [INFO Flash Code@23-05-17 15:27:51] Started erasing from 0x00 to 0x6474 (7 sectors)
    [ERROR Flash Code@23-05-17 15:27:51] Memory erasing failed.
    [INFO Flash Code@23-05-17 15:29:17] Started burning memory with 25716 bytes of data at address 0x00.
    [ERROR SPI Flash Programmer@23-05-17 15:29:18] Adddittional error info at JTAG address 0x7FC7C0C. (MSB first): FF FF FF F8.
    [ERROR Flash Code@23-05-17 15:29:18] Fail write 16384 bytes at offset 0x00
    [ERROR Flash Code@23-05-17 15:29:18] Failed burning memory.

    2. As regard to flashing an external board:

    Thank you for the assistance. I've been able to flash the device using the following pinout. My subsequent issue is that I cannot see any logs. The logs I have below me does not look like the logs from my external device, as it does that even when I unplug. How do I use Tera Term to see the log printouts from my external device?

    Thank you

  • I should add that since my external device is ISM14585, I have a different board setup for programming external devices:

  • Hi Joe,

    Thank you for the reply.
    Which version of the ISM14585 device you got? Does it have any SPI Flash? If yes, which part number?
    1. In regard to programming the DA14585 Development Kit Basic via toolbox:
    Have you programmed the Development Kit before? Does the DA14585 which is on board actively running any code? 
    From the image you shared, I believe you have the correct dip switch placed in order to burn your SPI Flash.
    Are you able to download code into the SRAM or is this an issue only with SPI Flash?
    2. In regard to programming the ISM14585 board:
    Glad you were able to program your ISM14585 board via the Development Kit Basic SWD interface. 
    In order to use the Tera Term Terminal you will have to use a Serial to USB module. The DA14585 Development Kit Basic has a FTDI which communicates from Serial to USB to PC.
    Please refer on UM-0-48 on chapter 5:

    The dip switches you have set on your Development Kit board for UART implementation is for the DA14585 which is integrated on board, you will have to connect those pins with the ones on your ISM14585 board in order to see the output on tera term or work with any other USB to Serial Module.
    From my understanding the ISM14585 board was designed to work with Development Kit Pro. 

    Kind Regards,
    OV_Renesas

  • Hi, the module's part number is: ISM14585-L35-P8. it contains 8mb flash.

    1. I have used the debugger on KEIL uVision to flash on the blink before, and I could see on tera it doing the blink messages. Was testing with toolbox to see if hex/bin's would work. I am not trying to use SRAM because I was encountering an issue there the device would halt instead of reboot, and I'd like to see the logs of that happening, and I was told that SRAM would not reboot when crashed.

    2. I see, so with a basic development kit and just the power + swd pins, I cannot debug? Is it possible to debug using those 4 pins but a dev kit pro?

  • Just to clarify, I'd like to debug external boards without using uVision.

    For the ISM14585-L35-P8, if we do need additional pins for debugging (referring to the uart), are there specific pins I would need?

  • Hi Joe,

    Thank you for the reply.

    I should add that since my external device is ISM14585, I have a different board setup for programming external devices:


    Were you able to download your FW into the SPI Flash with this configuration? This are the PINs used for the SPI Flash on the ISM14585-L35-P8.
    On ISM14585-L35-P8-EVB, page: 14:

    1. I have used the debugger on KEIL uVision to flash on the blink before, and I could see on tera it doing the blink messages. Was testing with toolbox to see if hex/bin's would work. I am not trying to use SRAM because I was encountering an issue there the device would halt instead of reboot, and I'd like to see the logs of that happening, and I was told that SRAM would not reboot when crashed.

    With Keil uVision you were downloading your FW into the SRAM. Via the SST (SmartSnippets Toolbox) you are trying to download your FW into the SPI Flash. 
    When you had downloaded the fw into the SRAM you did not have your debugger attached to see where the halt was occuring?

    2. I see, so with a basic development kit and just the power + swd pins, I cannot debug? Is it possible to debug using those 4 pins but a dev kit pro?

    The ISM14585-L35-P8 board was designed to work with the Development Kit Pro, it is clearly stated on page:5

    However, you could probably use the Vcc, GND, SWDIO and SWCLK to program your board via JTAG. This has not been tested by us. However we have a small guide on how you can do that on the DA1453x Development Kit Pro: 19. Serial Wire Debug Probe — DA145XX Tutorial SDK Getting started (renesas.com)

    Just to clarify, I'd like to debug external boards without using uVision.

    For the ISM14585-L35-P8, if we do need additional pins for debugging (referring to the uart), are there specific pins I would need?

    On the ISM14585-L35-P8 schematic, it is shown that P0_4 and P0_5 are being used for UART_TX and UART_RX respectively. 


    Kind Regards,
    OV_Renesas

     

  • Were you able to download your FW into the SPI Flash with this configuration? This are the PINs used for the SPI Flash on the ISM14585-L35-P8.

    Yes, clk0 cs7 miso5 mosi6. I've been flashing code onto the ISM14585 using that format.

    When you had downloaded the fw into the SRAM you did not have your debugger attached to see where the halt was occuring?

    Unfortunately, the MDK license is held on a remote desktop, which I've been using to code and compile, but the physical device is flashed and debugged with me. It is possible as somewhat of a last resort to debug on the remote device, but if there is no way to debug locally then it'll be a even more tedious process.

    Will the UART pins display crash logs, or will it only print out our printf's? We'll pull out the 0_4 0_5 pins on the PCB and test out the logging. Are there any software settings we'll need to set to allow it to print out crash logs?

  • Hi Joe,

    Thank you for the reply.

    Will the UART pins display crash logs, or will it only print out our printf's? We'll pull out the 0_4 0_5 pins on the PCB and test out the logging. Are there any software settings we'll need to set to allow it to print out crash logs?

    Yes, you can configure your project so it prints out the crash logs. 
    Please refer on this thread here: How to store stack info into flash for DA14585 when hard-fault or NMI happens? - Bluetooth Low Energy - Wireless Connectivity - Renesas Community
    It is explained which modifications you will need to do in order to print out any Hard Fault or NMI exceptions in your project.

    Kind Regards,
    OV_Renesas