Frequently Asked Questions |ROHM Semiconductor

If we start the debugger with LEXIDE-U16 while the program that incorporates the data flash driver is written to the microcontroller, all sectors in the data flash area will be erased (0xFF).
- The cause may be that the data flash erase processing in the program was executed.
  The program starts running when the microcontroller is powered on.
  After that, when the debugger is started with LEXIDE-U16, the debugger stops the program.
  If the program executed before starting the debugger includes data flash erase processing, the data flash area will be erased.
  As a result, it appears that the data flash area is initialized when the debugger is started.

We are developing derivative products by copying the project using LEXIDE-U16.
When we change the source files and debug again, all files are included in the build, including the unchanged files.
How can we configure it to build only the files that have changed?
- This is because the information of the copy source remains in the project.
  Please follow the steps below to delete the copy source information and set it again.
  
  Right click on the project > [Properties] > [C/C++ Build] > [Refresh Policy]
  (1) Delete the copy source project displayed in "a" with the [Delete] button in "b"
  (2) Click the "c" [Add Resource] button to add the current project
  Fig. 1

Please tell me how to allocate program codes and variables collectively for each function.
- Please refer to the application note "How to Allocate Functions and Variables to Specific Areas".
  It describes how to allocate functions and RAM variables in specific areas.
  The application note can be downloaded from our support site.
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

I am using LEXIDE-U16 to refer to the sample programs in the reference software.
Please tell me how to check the definition contents of driver functions, etc.
- With the name of the function you want to find selected on the LEXIDE-U16 edit screen (not including parentheses), select "Open Declaration" from the pop-up menu that appears when right-clicked, and the contents of the defined function will be displayed.
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

Please tell me how to display with decimal in the [Expression] view when debugging LEXIDE-U16.
- Select the variable you want to display in decimal, right-click, and select [Number Format] > [Decimal] from the pop-up menu to display in decimal.
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

When I try to AddList the software in MWU16, I get the following error message and cannot proceed.
"Data record having duplicate address was found include in ..."
Please tell me how to resolve with this issue.
- This error indicates that an address is duplicated.
  The following are possible causes.
  (1) Duplicate addresses exist in a single file.
  (2) When multiple files are AddListed, data with the same address exists in each file.
  
  The following is a description of the workaround.
  (1) The vector address 00h to 7Fh of the interrupt may have overlapping definitions.
  First, refer to the map file (*.map) and check which addresses overlap.
  The overlapped area will be marked with *OVL* on the left side as shown below.
  *OVL* S CODE* 00:0010 00:004F 0040(64) (absolute)
  
  Please search "#pragma interrupt" and check if there are any duplicate vector address definitions.
  If there are any, delete one of them.
  Enable the option "Stop by warning occurrence" to stop the build when a warning occurs during linking to ensure that this problem is detected.
  
  (2) Check if the addresses are duplicated between the files to be AddListed.
  Also, when adding separately created files such as audio data and table data, it is possible that they are AddListed without offsets being set.
  In this case, set the offset and add the file when performing AddList.
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

Is it possible to debug on the DTU8 the program built by LEXIDE-U16 ?
- It is possible.
  With the project selected on the [Project Explorer] of LEXIDE-U16, select [LAPIS]>[Debugger (DTU8)].
  DTU8 will start and the program will be loaded and ready for debugging.
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

Please tell me how to save the contents of all SFR to a file when debugging.
- To save the contents of all SFR to a file, use DTU8.
  The SFRSAV command of DTU8 allows you to save SFR data to a Motorola S2 format file.
  Select [Tools] > [Execute script command] of DTU8, and in the dialog, specify the folder and file name to save, such as SFRSAV C:\\temp\\SFR1.
  In the above case, SFR1.ram will be saved in the C:\\temp folder.
  Please note that the SFR data file is in Motorola S2 format, so the SFR name is not output.
  
  For the Motorola S2 format, refer to "9.5.4 Motorola S2 Format" in "MACU8 Assembler Package User's Manual".
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

When I open a source file on LEXIDE-U16, comments in the program may be garbled.
Please tell me how to resolve with this problem.
- It is possible to change the character encoding by selecting "Resource" in the [Properties] dialog and selecting Other in [Text file encoding].
  Please check if any of the six codes listed in the pull-down list will not eliminate the garbled characters.
  If the garbled characters are resolved, that is the corresponding code, so save the file with that code.
  If the garbled characters are not resolved by any of the codes, set the code (default is MS932) and retype the comment.
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx

Is it possible to display multiple source files on the DTU8?
- It is possible.
  Refer to "5.1.4 Displaying a Different File" in the "DTU8 User's Manual".
  Related Products: ML610(Q)40x, ML610(Q)42x, ML610(Q)47x, ML610(Q)48x, ML610Q10x, ML610Q11x, ML610Q17x, ML610Q30x, ML610Q35x, ML610Q36x, ML610Q38x, ML610Q41x, ML610Q43x, ML610Q46x, ML620Q13x, ML620Q15x, ML620Q416/ML620Q418, ML620Q503H/ML620Q504H/ML620Q506H, ML62Q12xx, ML62Q13xx, ML62Q14xx, ML62Q15xx/ML62Q18xx, ML62Q16xx, ML62Q17xx