Frequently Asked Questions |ROHM Semiconductor

Attention to Internet Explorer users: ROHM website does not recommend browsing in IE 11. Please use latest browser to ensure the best performance on ROHM website.

Company Sustainability R&D Careers Contact Us

Global - English
Americas - English
Europe - English
Europe - Deutsch
ASEAN/India - English
简体中文
繁體中文
한국어
日本語

- Search This Site
- ROHM Products
- Cross-Reference
- Dist. Inventory

Products
Technical Support
Applications
Sales
Buy or Sample

- Search This Site
- ROHM Products
- Cross-Reference
- Dist. Inventory

Products
Technical Support
Applications
Sales
Buy or Sample

myROHM Login

Company Sustainability R&D Careers Contact Us

Global - English
Americas - English
Europe - English
Europe - Deutsch
ASEAN/India - English
简体中文
繁體中文
한국어
日本語

Home
FAQ Search

Part Number Search

Product Category

ICs(348)
- Microcontrollers (MCUs)(348)
  - General-purpose MCUs (16bit)(348)
    - ML62Q1000 series (U16 Core)(348)
      - Normal type ML62Q1500 Group ROM Capacity : 32KB to 256KB(348)

FAQ Category

3rd party writer

A/D Converter

CPU

C Programming

FWuEASE+uEASE

GPIO/port

HTU8(Hex convert tool)

I2C Bus

LCD Driver

MWuEASE+uEASE

nanoEASE

PWM

RAM mapping

RC Oscillation type A/D Converter

ROMWINDOW

RTC

SSIO(SPI)

UART

uEASE

Assembling Programming

Watchdog Timer

opamp

On-chip Debug Emulator

gang writer

Clock

Code entry

CCU8(C Compiler)/RASU8(Assembler)/RLU8(linker)

Sample Program

Sample Program/SDK

Start Up File

Stack

Other Peripheral

Interrupt vector area

Timer

Time Base Counter

DTU8(Debugger)

Noise

Power on Reset

MCU Control Function

Flash Memory

Flash ROM writer

Full ICE

Programming,General

Memory

Memory Space

Library

Reset

Reference board

Safety

Development tools

external clock

Interrupts

Combination

Factory Programming

Multiplication/Division

Crystal oscillation

Function Timer

Successive Approximation Type A/D Converter

Serial communications

Low Power

Electrical characteristics

Power Supply Circuit

IDE(Integrated Development Environment・LEXIDE)

Built-in oscillation

Other general FAQs

FAQ's

Show All Answers

Hide All Answers

showing 1 to 10 of 348

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.

I've been using the LEXIDE-U16 until now, and I just installed the LEXIDE-Ω.
I don't see the Startup Config tool and Peripheral Config tool in the LAPIS menu.
Please tell me how to view these.
- Code Generation Tools (Startup Config tool/Peripheral Config tool) plug-ins are not compatible with LEXIDE-Ω.
  For this reason, LEXIDE-Ω does not appear in the selection items of the LAPIS menu.
  We apologize for the inconvenience, but please start each tool from the Windows start menu.
  
  [ML62Q1000 series]
  In the Windows start menu "LAPS Code Generation Tools",
  select "ML62Q1000 Startup Config tool" and "ML62Q1000 Peripheral Configuration Tool".
  
  [ML62Q2000 series]
  In the Windows start menu "LAPS Code Generation Tools",
  select "Startup Config tool" and "Peripheral Config tool".
  
  After creating a project with the above setting tool, it can be started by double-clicking the project file (*1) displayed in the LEXIDE-Ω project tree.
  
  *1: ML62Q1000: *.coprj/*.pcprj
  ML62Q2000: *.lucprj/*.lumprj

When running the program I created, for some reason, after branching at $$brk_reset,$$error in the startup file (*.ASM), it enters a WDT interrupt and eventually reset.
Why does it behave this way?
- Transition to $$brk_reset,$$error in the startup file (*.ASM) occurs when the BRK instruction (0xFFFF) is executed.
  Addresses to which no instruction is assigned are filled with 0xFFFF, so it seems that for some reason this address was executed and transitioned to $$brk_reset, $$error.
  As a possible cause,
  ・Interrupt vector is not defined
  ・A branch destination (function) such as an indirect call is not defined
  ・Interrupts are enabled within interrupt functions that disable multiple interrupts
  ・Stack overflow occurs
  And so on.
  Please check if any of the above apply.
  Transitions can be easily checked using the branch trace function of the on-chip emulator.

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])))

Is there a way to rewrite the flash memory of the ML62Q1000 series by connecting the ML62Q1000 series and PC with UART (RS-232C)?
- Connect ML62Q1000 series and PC with UART (RS-232C), there is an IAP function as a method of rewriting the flash memory.
  Details of IAP function are included in ML62Q1000S_ReferenceSoftware ”ML62Q1000 series IAP (In-Application Programming) Sample Program Ver2 AP Note” (FEXT62Q1000_IAPv2).

When I try to start debugging with LEXIDE-U16 on the ML62Q1000 series, ICE error: 6603H occurs and I cannot debug.
Since I have confirmed the following phenomenon, it does not seem to be a connection failure between the on-chip emulator and the microcontroller as described in FAQ No:_02130, or a malfunction of the microcontroller.

(1) The debugger can be started without an error only once immediately after erasing the target with MWU16.

(2) Regarding the reference software sample program, after erasing the target with the MWU16, I can debug it repeatedly without any problems.
- Check the mode setting P0MOD0 of the P00/TEST0 pin in your program.
  When using the on-chip emulator, use the P00/TEST0 pin as an input pin for on-chip debugging. If P0MOD0 is set to input disabled or output enabled, communication with the on-chip emulator will be disabled, and "ICE error: 6603H" will occur, making debugging impossible.
  Set P0MOD0 to the initial value 05H.

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.

When I click an operation button such as [Plug] on MWU16, the error "Cannot open log file,The present processing was canceled" occurs.
Please tell me what to do.
- The MWU16 saves a history of operations and results in log files. This error occurs when the log file cannot be written to.
  The storage location of the log file can be checked with [File] > [Set Log File ...] on the MWU16, and can be changed.
  Change the log file attribute to a rewritable attribute, or change the log file storage location to a rewritable folder.

showing 1 to 10 of 348

Items per Page

Page of 35

First Previous Next Last

ROHMsemi

Terms & Conditions for the usage of the website
Terms of Use of Social Networking Service
Privacy Policy
General Terms & Conditions of Contracts, Delivery & Services for Europe (English)
General Terms & Conditions of Contracts, Delivery & Services for Europe (German)
Impressum (Germany)
Standard Terms & Conditions for Sales

Sustainability
Research & Development
Patent Marking
Statement on UK Modern Slavery Act
ROHM UK Group Tax Strategy
Data Protection Information for Business Partners (Europe) [English]
Data Protection Information for Business Partners (Europe) [German]

Company
News
Investor Relations
Site Map
Contact Us

© 1997 - 2023 ROHM Co., Ltd. All rights reserved.

Back to Top

Please Wait...