January-31st-2020, 03:49 PM
Roy,
approach 1 in my eyes is impossible. netPI boots a secured Linux that is bound to the serial number the kernel was deployed on during production time of netPI. It checks a signed certificate and then continues the boot process all the underlying kernel components like the simple "dpkg" command need packages for post-installation that are signed by hilscher root key ... which of course nobody have except we. And the FAT32 partion you see ... contains not the netPI software. There are more partitions named BACKUP, RESTORE and SYSTEM containing netPIs software and kernel.
And yes netPI schematics are 100% the same as original Raspberry Pi 3B. It is coming from the same fab in China. If "/dev/spi" is missing then you have to enable it using the raspi-config to enable the SPI device in general. This is not under control of the driver.
Each netX hardware has an internal security memory telling the firmware which firmware can be loaded. netHAT has a differnet signature that netPI concerning netX. This is why the netPI samples come with a firmware named Rxxxxx.nxf while netHAT come with Xxxxxx.nxf. So your netHAT sample will not run directly with the netX controller used on netPI.
The only possibility I see is using option b.) only.
The driver we provide are simply said SPI drivers and are not in conflict with the RT patch.
Thx
approach 1 in my eyes is impossible. netPI boots a secured Linux that is bound to the serial number the kernel was deployed on during production time of netPI. It checks a signed certificate and then continues the boot process all the underlying kernel components like the simple "dpkg" command need packages for post-installation that are signed by hilscher root key ... which of course nobody have except we. And the FAT32 partion you see ... contains not the netPI software. There are more partitions named BACKUP, RESTORE and SYSTEM containing netPIs software and kernel.
And yes netPI schematics are 100% the same as original Raspberry Pi 3B. It is coming from the same fab in China. If "/dev/spi" is missing then you have to enable it using the raspi-config to enable the SPI device in general. This is not under control of the driver.
Each netX hardware has an internal security memory telling the firmware which firmware can be loaded. netHAT has a differnet signature that netPI concerning netX. This is why the netPI samples come with a firmware named Rxxxxx.nxf while netHAT come with Xxxxxx.nxf. So your netHAT sample will not run directly with the netX controller used on netPI.
The only possibility I see is using option b.) only.
The driver we provide are simply said SPI drivers and are not in conflict with the RT patch.
Thx
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
