I noticed that the api endpoints https://api.my-open-balena.deployment/device-types/v1/ and https://api.balena-cloud.com/device-types/v1/ have a difference in supported devices.
specially the jetson-xavier-nx-devkit-emmc is missing:
{
"slug":"jetson-xavier-nx-devkit-emmc",
"version":1,
"aliases":[
"jetson-xavier-nx-devkit-emmc"
],
"name":"Nvidia Jetson Xavier NX Devkit eMMC",
"arch":"aarch64",
"state":"RELEASED",
"instructions":[
"Put the NVidia Jetson Xavier NX board in recovery mode",
"Unzip BalenaOS image and use <a href=\"https://github.com/balena-os/jetson-flash\">Jetson Flash</a> to provision the device.",
"After flashing is completed, please wait until the board is rebooted"
],
"gettingStartedLink":{
"windows":"https://docs.balena.io/jetson-xavier-nx-devkit-emmc/nodejs/getting-started/#adding-your-first-device",
"osx":"https://docs.balena.io/jetson-xavier-nx-devkit-emmc/nodejs/getting-started/#adding-your-first-device",
"linux":"https://docs.balena.io/jetson-xavier-nx-devkit-emmc/nodejs/getting-started/#adding-your-first-device"
},
"supportsBlink":false,
"yocto":{
"machine":"jetson-xavier-nx-devkit-emmc",
"image":"balena-image",
"fstype":"balenaos-img",
"version":"yocto-honister",
"deployArtifact":"balena-image-jetson-xavier-nx-devkit-emmc.balenaos-img",
"compressed":true
},
"options":[
{
"isGroup":true,
"name":"network",
"message":"Network",
"options":[
{
"message":"Network Connection",
"name":"network",
"type":"list",
"choices":[
"ethernet",
"wifi"
]
},
{
"message":"Wifi SSID",
"name":"wifiSsid",
"type":"text",
"when":{
"network":"wifi"
}
},
{
"message":"Wifi Passphrase",
"name":"wifiKey",
"type":"password",
"when":{
"network":"wifi"
}
}
]
},
{
"isGroup":true,
"isCollapsible":true,
"collapsed":true,
"name":"advanced",
"message":"Advanced",
"options":[
{
"message":"Check for updates every X minutes",
"name":"appUpdatePollInterval",
"type":"number",
"min":10,
"default":10
}
]
}
],
"configuration":{
"config":{
"partition":{
"primary":9
},
"path":"/config.json"
}
},
"initialization":{
"options":[
{
"message":"Select a drive",
"type":"drive",
"name":"drive"
}
],
"operations":[
{
"command":"burn"
}
]
},
"buildId":"2.88.4+rev10",
"logoUrl":"https://files.balena-cloud.com/images/jetson-xavier-nx-devkit-emmc/2.88.4%2Brev10/logo.svg"
},
Since the jetson-xavier lists partition 37 as the primary one, the behaviour is related to this. A temporary fix is to hardcode partition 9 in the balena-cli implementation 
#commands/os/configure.js
# line 75
const image = params.image;
console.info(image);
deviceTypeManifest.configuration.config.partition.primary = 9
console.info(deviceTypeManifest.configuration.config.partition.primary);
Still it would be great if some one could point me in the direction to add support to the open-balen-api, since i could not find the relevant files so far.
.