Häufig gestellte Fragen (FAQ) |ROHM Semiconductor

FAQ Category

CPU

Programming,General

Memory

Reset

Development tools

Electrical characteristics

FAQ's

Alle Antworten anzeigen

Alle Antworten verbergen

showing 1 to 4 of 4

When I expand the LEXIDE-U16 workspace compressed in a ZIP file and use it, the window position information etc. will be reset.
What should I do?
- LEXIDE-U16 window position information is stored in the workspace ".metadata\.plugins" folder.
  If you use the Windows standard ZIP function ([Right-click] > [Send to] > [Compressed (zipped) folder]) in Explorer to compress a ZIP file, some parts of the Linux format folder starting with a dot are not compressed.
  In this case, extracting the ZIP file and opening it with LEXIDE-U16 will reset the window position information.
  If you want to compress the workspace, please use a compression application that supports Linux format folders such as 7-Zip or Lhaplus.

If I check "Use this as the default and do not ask again" in the "Select a directory as workspace" dialog that appears when you start LEXIDE-U16, this dialog will not be displayed after that. Please tell me how to display the "Select a directory as workspace" dialog.
- The method to redisplay the "Select a directory as workspace" dialog is as follows.
  1. Select [Window] > [Preferences] from the LEXIDE-U16 main menu.
  2. Select [General] > [Startup and shutdown] > [Workspaces] from the left panel of the [Preferences] dialog.
  3. Enable the [Prompt for workspace on startup] checkbox.

We are developing software using IDEU8. When I start the debugger of DTU8 from IDEU8, the error dialog "Source file not found" is displayed. I can see the assembly code but not the C source code.
- It is assumed that no debug information is included.
  Please check "Compile/Assemble Options" and "Target Options" in IDEU8.
  
  [Compile/Assemble Options]
  Check "Print debug information" in the "General" tab.
  
  [Target option]
  Check "Print debug information" in the "General" tab.
  
  After setting the above, build again and restart DTU8.

We are considering changing from a microcontroller with a ROM capacity of 64K bytes or less to a microcontroller with a ROM capacity of over 64K bytes.
When the memory model changes from Small to Large, are there any points to be aware of with pointers, arrays, etc.?
- As the memory model goes from Small to Large, the size of pointers to functions changes from 2 bytes to 3 bytes.
  Please note that when using an array of pointers to functions.
  The sizeof operation result for a single pointer to a function in the Large model is 3, but in the case of an array of pointers to functions, a 1-byte padding is inserted after each element.
  So with 5 elements, the size of the array is
  ((pointer size 3 bytes) + (padding 1 byte)) * (number of elements 5) = 20 bytes.
  For details, see "1.5.2.2 Arrays other than char type" in "CCU8 Programming Guide".
  
  Also, when calculating the number of elements in an array, it is generally calculated by dividing the size of the entire array by the size of the elements in the array.
  Therefore, the following macro may be defined as a macro for calculating the number of array elements.
  #define ARR_NUM(array) (sizeof(array)/sizeof(array[0]))
  If the pointer size is 3 bytes, the total array size includes 1 byte padding for each element, so the number of elements is calculated incorrectly. In this case, you need to change it as follows.
  #define ARR_NUM(array) (sizeof(array)/(sizeof(array[0]) == 3 ? 4 : sizeof(array[0])))

showing 1 to 4 of 4

Items per Page

First Previous Next Last