xRDC - Xen

[Atkinson]

Hi @chenyin_h 

In the Xen Hypervisor whether it is possible to bring multiple domU ?
1.)Here i could able to trigger one configuration at a time having a file /etc/xen/domU1_mmc.cfg 
whether it is possible to create multiple like domU1,domU2,domU3 so for the should we need to create a separate file in the directory domU2_mmc.cfg , domU3_mmc.cfg ?? it shows some erro when i tried creating like this 

2.) when bringing up the /etc/xen/domU1_mmc.cfg its getting booted as a similar Linux BSP so whether it is possible to change it as Zephyr RTOS/FreeRTOS so how can we do it where this changes need to be done ?

[chenyin_h]

Hello, @Atkinson 

Thanks for your reply.

May I know what are the contents in partition6? If there are no data in it, I suggest trying copy all data from partition 5 to the partition6, and have another trial once reboot.

BR

Chenyin

[Atkinson]

Hi @chenyin_h 

I even tried that it doesn't help much same kernel issue.
In domU Creation whether it is possible only we can create Two instance domU1, domU2 
It will not be possible to create more than two instance ?

Regards
Atkinson

[chenyin_h]

Hello, @Atkinson 

Thanks for your reply.

1. From my understanding for Xen itself, it should support more than 2 DomUs

2. For actual implementation on S32G3BSP, I had tested BSP44 on my RDB3, and found that 2 DomUs could be supported, I did not test it further since it is beyond BSP's scope.

In summary, I could confirm at least 2 DomUs could be supported on RDB3 using latest BSP, theoretically, more DomUs could be supported, but it may need additional development/test effort.

BR

Chenyin 

[Atkinson]

Hi @chenyin_h 

Yeah, Thanks for sharing your opinion
In the Xen Hypervisor currently its coming up with Linux BSP ryt 
would that be possible to have it as a FreeRTOS based package instead LinuxBSP. How can we make that change 

Regards
Atkinson 

[chenyin_h]

Hello, @Atkinson 

Thanks for your reply.

As I mentioned previously, Xen is not product from NXP, but is maintained by https://xenproject.org/.

1. I have checked the document from Xen, it is not mentioned FreeRTOS is officially supported.

2. By checking it internally in NXP, I do not find plan for supporting FreeRTOS based on Xen on S32G platform.

So in summary, it is not supported currently. 

BR

Chenyin 

[Atkinson]

Hi @chenyin_h 

Yeah thanks for the reply!!
Couple of questions here 
1.) can you list down the other OS which will be getting supported in xen which i can use apart from Linux OS
2.)So when using the A-53 core to boot it from BSP package yocto build linux (BSP43.0) here whether we can use the Hardware CAN, ETHERNET and other physical ports how can we use the LLCE CAN directly its possible to access it directly or some steps need to be enabled ?
3.) so similarly how it can be done it in from the hypervisor ?

Regards
Atkinson

[chenyin_h]

Hello, @Atkinson 

Thanks for the reply.

1. From NXP BSP perspective, I do not see any plan to support other kind of OS except for current Linux BSP.

2. Currently, there are the following supported features for Xen as described in BSP UM:

chenyin_h_0-1758870069770.png

You may refer to the BSP UM for details.

I do not see any examples/documents related with LLCECAN from DomUs.

BR

Chenyin

[Atkinson]

Hi @chenyin_h 

In the xen hypervisor how can I make the CAN communication from external world to inside the RDB2 board inside domU users how can I make the CAN communication. I hope that will be possible ? 

I am trying to do a Separate CAN communication from domU1 and domU2 so how to handle this?

Regards

Atkinson

[chenyin_h]

Hello, @Atkinson 

Thanks for your reply.

1. Theoretically it may be supported.

2. But, to implement the function you mentioned, there would be additionally drivers/settings available, however, as I had mentioned in previous reply, from formal BSP perspective, I do not see any examples/documents related with LLCECAN from DomUs.

So in summary, this feature you mentioned is not supported from default BSP implementation.

BR

Chenyin

[Atkinson]

Hi @chenyin_h 

Thanks for the reply !!!

As you said that we need to make some changes in drivers in order to bring the CAN Communication can you give me the steps to bring up the CAN Communication would that be possible ?
Whether BSP44.0 will be supporting that ?
but if these are making it complex what are the test cases can be conducted under the Xen Hypervisor what need to be done were we have two isolated domU Users which has been brought up 

Regards
Atkinson 

[chenyin_h]

Hello, @Atkinson 

You are welcome.

1. Sorry that I am not able to provide such steps, since currently this feature is not implemented.

2. Latest BSP(BSP44) could not support it since it is not a feature that implemented in default BSP.

3. Regarding Xen examples in BSP, you may refer to the chapter 24.3.6 in BSP44 UM, to test for the network.

BR

Chenyin

[chenyin_h]

Hello, @Atkinson 

From my understanding

1. Multiple DomUs are supported by the Xen.

2. Commonly, the OSes running on the Xen are rich OS like Linux, for zephyr, it is mentioned from Xen official site that there are some initial supporting for it(https://wiki.xenproject.org/wiki/Xen_Project_4.16_Feature_List#Zephyr_RTOS)

But from NXP formal software view, I do not see this feature supported, the features supported for Xen could all be found in the BSP UM.

BR

Chenyin

[Atkinson]

Hi @chenyin_h 

1.) How to enable multiple Domu in the xen 
currently able to trigger only one domu which is done by 
trigger one configuration at a time having a file xlcreate /etc/xen/domU1_mmc.cfg 
so similarly how can i do for triggering multiple domu's can be more specific 

2.)Whether it is Possible to ring FreeRTOS and Nxp support that feature in Xen ?

Regards
Atkinson 

[chenyin_h]

Hello, @Atkinson 

Thanks for you reply.

1. As I mentioned, multiple DomU could be supported by Xen, but from BSP's side, there is not ready to use sample related, by default, only 1 DomU(DomU1) could be support.

Currently from BSP44, there is additional DomU2 configuration file existed, but it could not be directly used since lacking of corresponding partition on the SD card, you may add one partition to your default SD card and have another trial.

2. I feel sorry that it is not possible, for A53 side software(TFA/Uboot/Xen/Linux), these are not products from NXP, we provided corresponding drivers to them, and could use the combination packages to boot the board, generally, this kind of pure software support is done by the open-source. not us.

BR

Chenyin

[Atkinson]

Hi @chenyin_h 

When i tried of creating another partition and run it 
it showing the below error 
[ 2.814656] Run /sbin/init as init process
[ 2.814686] with arguments:
[ 2.814705] /sbin/init
[ 2.814721] with environment:
[ 2.814750] HOME=/
[ 2.814774] TERM=linux
[ 2.814980] Run /etc/init as init process
[ 2.815013] with arguments:
[ 2.815032] /etc/init
[ 2.815049] with environment:
[ 2.815081] HOME=/
[ 2.815107] TERM=linux
[ 2.815191] Run /bin/init as init process
[ 2.815220] with arguments:
[ 2.815238] /bin/init
[ 2.815253] with environment:
[ 2.815283] HOME=/
[ 2.815300] TERM=linux
[ 2.815380] Run /bin/sh as init process
[ 2.815414] with arguments:
[ 2.815432] /bin/sh
[ 2.815449] with environment:
[ 2.815479] HOME=/
[ 2.815506] TERM=linux
[ 2.815582] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[ 2.815649] Kernel Offset: disabled
[ 2.815679] CPU features: 0x1,20000008,00020000,1000420b
[ 2.815713] Memory Limit: none
[ 2.815738] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. ]---

So how can we overcome this issue whether it is possible to overcome in BSP43.0 


Regards
Atkinson 

[chenyin_h]

Hello, @Atkinson 

Thanks for your reply.

Would you mind sharing the log once running fdisk -l once booting the Dom0?

BR

Chenyin

[Atkinson]

Hi @chenyin_h 

Here is the log 

root@s32g274ardb2:~# fdisk -l
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfb1628fe

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 16383 8192 4M 83 Linux
/dev/mmcblk0p2 16384 147455 131072 64M c W95 FAT32 (LBA)
/dev/mmcblk0p3 147456 2768895 2621440 1.3G 83 Linux
/dev/mmcblk0p4 2777088 17231871 14454784 6.9G f W95 Ext'd (LBA)
/dev/mmcblk0p5 2785280 5406719 2621440 1.3G 83 Linux
/dev/mmcblk0p6 5408768 7948287 2539520 1.2G 83 Linux