RX850

Is it possible that OS processing will be executed during maskable interrupt servicing?

Unless a system call is issued, OS processing will not be executed during maskable interrupt servicing.

How long does it take from the occurrence of a RX850 hardware interrupt source until the startup of the interrupt handler.
The CPU is the V850/SA1 (17MHz).

The interrupt handler startup time for the V850E/MS1 (25MHz operation) with internal ROM/RAM was 2.7 to 2.9μs.
Since these CPUs have the same architecture, convert the operating frequency to obtain the desired number.
This is an actually measured value and thus should be used carefully.

The stack size of each task is specified in the configuration file.
Is it possible to release the stack area of a non-operating task for another task stack?
Or must the stack be secured continuously and independently regardless of the operating state of each task?

Basically, it must be secured for each task.
We are not sure what you mean by the operating state of each task but for a task in the sleep state, the stack is used to retain that status.

In the RX850, if tasks that do not operate at the same time are grouped together, the stack area can be reduced.
In this case, the user must manage tasks carefully (ensure that these tasks do not operate at the same time).

(Refer to 3.2, "Task Execution Right" in the Basics User's Manual.)

The size of "intstk" is specified in the configuration file.
Is this stack only used for the interrupt handler?

This is used for the interrupt handler and timer handler.

Is it necessary to make the start address a multiple of 4 to link the RX850 Pro?
Are there any other limitations?

As long as the start address is multiple of 4, it is OK.
There are no other limitations.

I'm using the GHS compiler.
The contents of ISP (r2) differ from the expected value in the OS and the OS jumps to an unexpected location.
ISP seems not to be saved within the OS.
Are there any cautions pertaining to compiling and linking I should be aware of?

r2 and r5 cannot be used when using the GHS compiler.
Specify the -reserve_r2 and -reserve_r5 options.

Even if there is enough space available, when get_blk is executed, the system enters the wait status.
Is there any way of analyzing the cause of this?

Use the task debugger (RD850 Pro) in a case like this.
You can check the wait status of the memory pool using the RD850 Pro.

Are the first 4 bytes of an area acquired with get_blk user-accessible? When data is written to the start address, the area cannot be released using rel_blk.

It is OK to use from the start of a memory block but you have to clear the first 4 bytes of the memory block to zero when you release the memory block.
From RX850 Pro V3.15, some libraries do not require the first 4 bytes to be cleared.

Is there any processing other than using the clock handler to perform DI, such as using an OS system call?
In this case, how many clocks does it take to perform DI ?

DI processing is performed in various places within the OS such as task scheduling.
However, it is generally expressed in units of time limited to the CPU and operating clock (not calculated by the number of clocks).

Control shifts to the initial block of the nucleus and the HALT status is entered.
Are there any conditions under which this will happen other than memory shortage?

The OS enters the HALT status when a management table cannot be created for some reason, rather than due to memory shortage.
In addition, check to make sure there is no program lockup or memory error.

Can PSW ID flag control be performed by the user?
Is a system call provided to operate the PSW ID flag?

This is managed by the OS. Do not manipulate this within the OS.

Which has the higher priority, task 0x01 or task 0x02 ?

The smaller the value, the higher the priority (0x01 is higher in this case).

How is system clock processing called?

System clock processing starts when a clock interrupt is generated.
That is, it is handled as an indirectly started interrupt handler.

What does a sample program do?

Four tasks are created and they execute timeout waiting, resource waiting (semaphore, event flag waiting) and resource capture.
Refer to task.c where task1 to task4 are described.
We are sure this will help you understand the program.

Does the sample program run on a standalone PC ?

No, it cannot be executed as is.
If a simulator is also running on the PC, the program runs as well.
Otherwise, it cannot be operated on a standalone PC.

If "Undeclared function call" is checked using a compiler option specification,
is output in response to an OS (RX850 Pro) system call or _rcopy().

For RX850 Pro system calls, include stdrx85p.h.
The _rcopy function is not a system call and thus describe a prototype declaration in the source data as follows:

Is it possible to jump even if the distance between the interrupt table (V850: starting from address 0) and the OS object is 0x1FFFFF or more?

If the distance assigned is 0x1FFFFF or more, branch cannot be performed.
Make sure that the distance is within the range that can be branched with jr.

In addition, when using the device address wraparound, an address branched from a negative direction such as address FFFFE000 instead of address 3FFE000 can be considered.
(Address FFFFE000 is simply the higher address set as 1 and thus another value is required in an actual case.)

Do RTOS (uITRON standard) products include a TCP/IP protocol stack area?

The V850 Series supports TCP/IP (product name: AP703100-B17).
The following third-party products are also provided:

Can RTOS : pSOS or μITRON be mounted on the V850 ?

Our product RX850 conforms to μITRON3.
In addition, regarding pSOS, a product that supports the V850E is available from a third-party company.

Contact the following company for details:

Integrated Systems Japan
TEL	: 03-3492-3171
FAX	: 03-3492-3066
E-mail	: info@isi.co.jp
HP	: http://www.isi.com/

The RX850 is available in two types: the RX850 and the RX850 Pro.
What are the differences between the RX850 and RX850 Pro?

The RX850 is a product designed to facilitate transfer from 8/16-bit 78K Series products and has been made more compact.
The RX850 Pro is an RX850-enhanced type and has almost the same specifications as the RX830.

For more details, please see below.

OS	Performance	Description
RX850	[Conditions] - V853 (25MHz) - Program: Internal ROM - Data/stack: Internal RAM <>Maximum interrupt disable time: 7μs <>Task switching time: 11μs (wup_tsk) <>Code size: 3 to 7 KB	This OS is easy to port from the 78K Series. It has a compact design to enable operation from the on-chip ROM and RAM of the V850.
RX850   Pro	[Conditions] - V850E/MA1 (50MHz) - Program: External ROM   (external bus width: 16bits/2waits) - Data/stack: Internal RAM <>Maximum interrupt disable time: 8μs <>Task switching time: 20μs (wup_tsk) <>Code size: 5 to 13KB	This is the RX850 OS but with enhanced functions.

What is your yearly maintenance charge and support fee for the RX850 Pro?

We do not provide a fee-based yearly maintenance service.
Basically we offer independent contents support and a one-year free upgrade service.
See the purchase contract for details.

What kind of support is provided at the time of initial installation?

We do not provide support at the time of initial installation.
If any kind of support is required, contact your local distributor.