Module is present, but NOT CONFIGURED!!!

[Boris Crismancich]

using /homepi/demo/piTest -d I get this but piCtory seems to be ok. Only one DIO and one Core 1.2.
Any ideas if this is harmful? Dio counters work fine.

Found 3 devices:

Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present, but NOT CONFIGURED!!!
input offset: 0 length: 6
output offset: 6 length: 5

Address: 31 module type: 96 (0x60) RevPi DIO V1.3
Module is present
input offset: 0 length: 70
output offset: 70 length: 18

Address: 0 module type: 32863 (0x805f) RevPi Core V0.0
Module is NOT present, data is NOT available!!!
input offset: 113 length: 1
output offset: 114 length: 1

[volker]

Hi Boris,
this is not really documented well but you have several options for the core module in piCtory. Your -d screen shows the following:
a) you have configured a core v 0.0
b) the system checked modules during driver reset but could only find v 1.2

The most likely scenario is a change of the core 1 to a core 3 in a system and you copied the saved configuration file onto the newer core 3.

The difference between the versions is nothing realy serious so you won't find difficulties in running you system until you try to access any IOs belonging to the core (LED, CPU temerature, CPU clock, cycle time, etc.) check it out and change the core in piCtory and you will find the differences. This said I strongly recommend the use of a correct configuration in order to get a correct functionality of the overlapping bytes between core and right side modules.

The version is a sw dependend version and not simply a question of CM1 versus CM3. We delivered CM1 with version 0.0 for a long time so on most CM1 devices you will need to run 0.0. However, a piTest -d will always show which version is found by the system so please check using this command. in your case it says:

Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present, but NOT CONFIGURED!!!

Your RevPi Core uses 11 Bytes of IO whereas v 0.0 has used only 2 Bytes...