
After selecting your kOS release to configure your device image, you must choose the hardware profile and node settings for the device on which you will run your image. The Hardware profile screen lets users set up port mappings and developer flags to facilitate quick debugging and device setup. This article walks through the steps to set up hardware settings for your image.
Hardware profiles provide images with details about the hardware on which you run the image. Hardware profiles are added by the administrator per project via Hardware management .
Log in to kOS Studio, and from My Images, click on Open Image Manager (in the upper right corner of the screen)
From the list of images, select the image you want to update and click on Settings for that image(on right hand side for image row)
Select the Configure tab from the top menu on the image configuration window.
From the Image Configuration window that opens, select Hardware Settings from the list of stacks displayed on the left-hand side.
Select the Hardware Profile tab to view available hardware profiles.
Select the appropriate hardware profile from the list by selecting the radio button.
Details about the profile are displayed once a profile is selected from the list. Consider following :
A default profile is added to your hardware profiles list by kOS Studio.
For child images, the Inherited hardware profile is indicated via an inherited label
Port mapping lets you access simulator data on various ports outside. kOS studio allows users to specify their ports per protocol via port mappings. You can find out more about port mapping here.
Log in to kOS Studio, and from My Images, click on Open Image Manager (in the upper right corner of the screen)
From the list of images, select the image you want to update and click on Settings for that image(on right hand side for image row)
Select the Configure tab from the top menu on the image configuration window.
From the Image Configuration window that opens, select Hardware Settings >> Configure port mappings tab
Log in to kOS Studio, and from My Images, click on Open Image Manager (in the upper right corner of the screen)
From the list of images, select the image you want to update and click on Settings for that image(on right hand side for image row)
Select the Configure tab from the top menu on the image configuration window.
From the Image Configuration window that opens, select Hardware Settings > Configure port mappings tab
Select the protocol you want to add port mappings for from the displayed list. Provide the internal simulator port, team mapping, and local override for the newly added port. Consider following :
Use ports higher than 1024 as port forwarding, where port numbers smaller than 1024 can only be created by software running as the root user.
If you have a Local Override Specified, it will take precedence over the Team Port. If no Local Override is provided, Team Port will be used.
kOS studio will always show an indicator next to the active port mapping.
For child images, inherited port mapping is indicated via grayed out text, which can be updated to a different value if needed.
Log in to kOS Studio, and from My Images, click on Open Image Manager (in the upper right corner of the screen)
From the list of images, select the image you want to update and click on Settings for that image(on right hand side for image row)
Select the configure tab from the top menu on the image configuration window.
From the Image Configuration window that opens, select Hardware Settings >Configure port mappings tab
Click the Add new port on the Configure port mapping tab. Here, provide the internal simulator port, team mapping, and local override for the newly added port. Consider following :
Use ports higher than 1024 as port forwarding, where port numbers smaller than 1024 can only be created by software running as the root user.
If you have a Local Override Specified, it will take precedence over the Team Port. If no Local Override is provided, Team Port will be used.
kOS studio will always show an indicator next to the active port mapping.