rsu files

I am attempting to resurrect an RX65N Envision kit.  I downloaded standard.zip from the downloads tab at renesas.com/envision.

When it unzips there are two *.rsu files.  What am I supposed to do with those? 

  • Dale,

    Some more information about your project might help our community to answer your question.

    Which file did you download?
    Are you trying to reflash the firmware?
    What tools are you using?

    Mike Clements
    RenesasRulz Moderator
  • In reply to Mike Clements:

    Mike, go ahead and ax this. I'll figure it out when I get a chance to get back to it. Basically, thought I had a virgin kit but it didn't light up so I was looking for a QnD way to light it back up. I expected a mot file if not a default e2 project. To my surprise the "standard.zip" file on the renesas.com/envision page contained 2 files with an rsu extension. I opened one up and it looks like an encrypted mot .

    sha1 d35xxOc0mS9vmYCiewjwDcU+SGU=
    iv AAAAAAAAAAAAAAAAAAAAAA==
    sessionkey0 AAAAAAAAAAAAAAAAAAAAAA==
    sessionkey1 AAAAAAAAAAAAAAAAAAAAAA==
    max_cnt 3c004
    checksum AAAAAAAAAAAAAAAAAAAAAA==
    upprogram fff00000 AAAAAAAAAAAAAAAAAAAAAA==
    upprogram fff00010 AAAAAAAAAAAfHB8eHx4fHw==
    upprogram fff00020 Hh8eHwD//////////////w==
    upprogram fff00030 AAD///8A//8A/+8A7swAzA==
  • In reply to Dale Drinkard:

    Dale,

    The Renesas Flash Development Toolkit can be used to re-flash the factory image.
    www.renesas.com/.../flash-development-toolkit-programming-gui.html

    Mike Clements
    RenesasRulz Moderator

  • In reply to Dale Drinkard:

    rx65n_envisionkit_demo_readme.txt
    ----------------------------------------------
    RX65N Envition Kit Demo Firmware (20171113)
    ----------------------------------------------
    -release data
     rx65n_envisionkit.zip
      benchmark         ("Benchmark Demo" e2 studio workspace)
      rx65n_secure_boot ("Secure Boot" e2 studio workspace)
      standard          ("Standard Demo" e2 studio workspace)
      convert           (Converter for from motrola file to renesas secure update (*.rsu))
       exe
        convert.exe
    
    -environment
     Board: RX65N Envision Kit.
     IDE: e2 studio 6.1.0 or later (please use: https://www.renesas.com/en-eu/software/D4000508.html)
     Compiler: v2.07.00 or later
     Devices: USB cable(power supply/debug) - 1pcs
              USB memory - 1pcs
              Windows PC or mobile battery (power source) - 1pcs
    
    -Setup:
     (1)import the "/rx65n_envisionkit/rx65n_secure_boot" project using e2 studio.
     (2)set board SW1-1 ON and, compile, start debug(downloading), disconnect the debugger, set board SW1-1 OFF.
    
     (3)import the "/rx65n_envisionkit/standard" project using e2 studio.
     (4)compile
     (5)execute "/rx65n_envisionkit/convert/exe/convert.exe"
     (6)specify "/rx65n_envisionkit/standard/RX65N_EnvisionKit/HardwareDebug/RX65N_EnvisionKit.mot" to "User Program File Path" using Browse button.
     (7)select "RX65N(ROM 2048KB)" to Select MCU.
     (8)push Generate button. "userprog.rsu" is generated. Please rename to "std.rsu". Please input this file into USB Memory. 
    
     (9)import the "/rx65n_envisionkit/benchmark" project using e2 studio.
     (10)compile
     (11)execute "/rx65n_envisionkit/convert/exe/convert.exe"
     (12)specify "/rx65n_envisionkit/benchmark/rx65n_envision_kit_demo/HardwareDebug/rx65n_envision_kit_demo.mot" to "User Program File Path" using Browse button.
     (13)select "RX65N(ROM 2048KB)" to Select MCU.
     (14)push Generate button. "userprog.rsu" is generated. Please rename to "bench.rsu". Please input this file into USB Memory. 
    
     (15)connect USB Memory to the CN11 on board. Secure Boot would write Standard Demo firmware to temporary area. (filename: std.rsu)
     (16)When write succeed, display shows the message like "swap bank ...", 
     (17)After 3 seconds, Secure Boot executes bank swap and reset. Standard Demo will start.
     (18)Please push "Bank Swap" Button. Display Shows Bank Swap Demo. 
     (19)(on board) Keep pushing SW2 in 3 seconds. Starts download and writes Benchmark Demo firmware to temporary area. (filename: bench.rsu)
     (20)When write succeed, Please push "Swap!!" button. Standard Demo will swap bank and software reset.
     (21)Benchmark Demo will start.
     
    -Notice
     Current project includes the code that over ROM size more than 128KB.
     Please use product verson compiler or none-expired(within 60 days from the use beginning)
     evaluation version compiler.
    
    -How to debug user program (standard/benchmark)
     User program (standard/benchmark) are allocated into 0xfff00000-0xffff0000,
     because of secure boot is allocated into 0xffff0000-0xffffffff includes reset vector
     to verify the user programs.
     User program's reset vector (RESETVECT) is allocated into 0xfffefffc,
     and User program's excepted vector (EXCEPTVECT) is allocated into 0xfffeff80.
     Therefore, distributed user programs source code cannot debug current allocation.
     User can debug when changing allocation as below using Linker setting.
     RESETVECT 0xfffefffc -> 0xfffffffc
     EXCEPTVECT 0xfffeff80 -> 0xffffff80
    
    -Technical Info
     RX65N Envition Kit Demo has following memory map.
    
     +---------------------------------+ 0xFFE00000 -
     |   temporary area                |            |
     +---------------------------------+ 0xFFEF0000 | bank1
     |   Secure Boot area(mirror)      |            |
     +---------------------------------+ 0xFFF00000 -
     |   execute area                  |            |
     +---------------------------------+ 0xFFFF0000 | bank0
     |   Secure Boot area              |            |
     +---------------------------------+ 0xFFFFFFFF -
    
     Phase Setup-(2) status <just download secure boot>:
     +---------------------------------+ 0xFFE00000 -
     |   blank                         |            |
     +---------------------------------+ 0xFFEF0000 | bank1
     |   blank                         |            |
     +---------------------------------+ 0xFFF00000 -
     |   blank                         |            |
     +---------------------------------+ 0xFFFF0000 | bank0 <start bank>
     |   Secure Boot                   |            |
     +---------------------------------+ 0xFFFFFFFF -
    
     Phase Setup-(2) status <after first execution of Secure Boot>:
     +---------------------------------+ 0xFFE00000 -
     |   blank                         |            |
     +---------------------------------+ 0xFFEF0000 | bank1
     |   Secure Boot(mirror)           |            |
     +---------------------------------+ 0xFFF00000 -
     |   blank                         |            |
     +---------------------------------+ 0xFFFF0000 | bank0 <start bank>
     |   Secure Boot                   |            |
     +---------------------------------+ 0xFFFFFFFF -
     
     Notice:
      Secure Boot copies itself to Secure Boot area(mirror) in first execution phase.
    
     Phase Setup-(14) status <installing Standard Demo>:
     +---------------------------------+ 0xFFE00000 -
     |   Standard Demo                 |            |
     +---------------------------------+ 0xFFEF0000 | bank1
     |   Secure Boot(mirror)           |            |
     +---------------------------------+ 0xFFF00000 -
     |   blank                         |            |
     +---------------------------------+ 0xFFFF0000 | bank0 <start bank>
     |   Secure Boot                   |            |
     +---------------------------------+ 0xFFFFFFFF -
    
     Phase Setup-(15) status <after swap bank>:
     +---------------------------------+ 0xFFE00000 -
     |   blank                         |            |
     +---------------------------------+ 0xFFEF0000 | bank0
     |   Secure Boot                   |            |
     +---------------------------------+ 0xFFF00000 -
     |   Standard Demo                 |            |
     +---------------------------------+ 0xFFFF0000 | bank1 <start bank>
     |   Secure Boot(mirror)           |            |
     +---------------------------------+ 0xFFFFFFFF -
    
     Phase Setup-(19) status <installing Benchmark Demo>:
     +---------------------------------+ 0xFFE00000 -
     |   Benchmark Demo                |            |
     +---------------------------------+ 0xFFEF0000 | bank0
     |   Secure Boot                   |            |
     +---------------------------------+ 0xFFF00000 -
     |   Standard Demo                 |            |
     +---------------------------------+ 0xFFFF0000 | bank1 <start bank>
     |   Secure Boot(mirror)           |            |
     +---------------------------------+ 0xFFFFFFFF -
    
     Phase Setup-(20) status <after swap bank>:
     +---------------------------------+ 0xFFE00000 -
     |   Standard Demo                 |            |
     +---------------------------------+ 0xFFEF0000 | bank1
     |   Secure Boot(mirror)           |            |
     +---------------------------------+ 0xFFF00000 -
     |   Benchmark Demo                |            |
     +---------------------------------+ 0xFFFF0000 | bank0 <start bank>
     |   Secure Boot                   |            |
     +---------------------------------+ 0xFFFFFFFF -
    
    
    
    
    

    Dale,

    The .rsu files are intended to be loaded from USB stick using a secure boot loader application that's running on the Envision kit.

    Follow the instructions in the file: "rx65n_envisionkit_demo_readme.txt" that is included in the Envision Kit software download from the Envision Kit web page.

    I have attached the file for your convenience.

    -Gerald

  • Dale,

    Have you been able to reflash your RX65N Envision kit?

    Mike Clements
    RenesasRulz Moderator
  • In reply to Mike Clements:

    I'm using convert.exe to try to convert the RX65N NES emulator written by rvf-rc45. when I choose the .mot file and press 'Generate', I get the following error:

    0: mismatch motorola file top address and selected MCU top address.

    Any idea what that means?

    edit: I haven't solved this problem, but I got around it by using the Renesas Flash Programmer to upload the program. RFP accepts .mot files.

  • In reply to stylus:

    Stylus,

    The RSU files are intended to be loaded by the secure boot loader application into specific regions of flash memory. So the application software must be memory mapped accordingly. The secure boot loader remains in a specific flash address range, and the application is loaded elsewhere so that it does not overwrite the loader.
    The sample projects that can be download from Renesas for the Envision Kit are set up for this, so use them as reference if you want to use this method of flash programming.

    For non-secure applications that are flashed to wherever they have been mapped by the developer, then just use RFP as you did.

  • This thread will be archived due to inactivity.

    Mike Clements
    RenesasRulz Moderator