Installing Code for PiFace Real Time Clock

Swap SD cards and if the problem moves, then the problem is on that card and is not identical!

Clem

Looking at the rest of the scripts output you just posted, it would appear that the installer did complete successfully, have you checked to see if the service is enabled sudo systemctl is-enabled pifacertc or you could try to find it in the list of services sudo systemctl -a even just trying to start the service manually might give some clues if it returns an error sudo systemctl start pifacertc

Dear Ms tozer,

Thanks for your speedy comments and otherwise approaches I had no knowledge of.

No- I did not check these commands but I will do so in the near future. If in fact the installation was successfull, I still am getting a Failed line: Failed to Add PiFace RTC  during the boot phase but this may have been resolved within the remaining lines. To be honest when I have a returned response that I must create another init pifacertc script, I may not have proceeded successfully with the date verification and i2c-dev checking.  I'll continue to eperiment and thanks or you help. Frank.

Dear Clem Martins,

Thanks or your continuing interest.
Yes- I swapped SD cards and BOTH RPi Zero systems failed. The SD cards are identical in brand, model, and capacity. However, I certainly may have proceeded slightly different in their installations. I should mention that installed on each system are also a WiPi network adapter, a Flash drive, and an ENC28j60 Ethernet module on a poered hub but all these components are performing admirably.

In the future, I may recode Failed SD card from the beginning and install all the components rom scratch again. I would appreciate if you can recommend a specific Rasbpian Jessie version and also comment on the initial commands other than:   

sudo apt-get update
sudo apt-get upgrade

In addition, there are a multitude of additional "switches" like,  sudo apt-get upgrade -y
What are the current standards that I should use ?

I also plan on cloning the successfull SD card on my windows laptop using notepad ++ and also examining each and every file to determine the differences from the failed SD card. You are certainly correct that something is different with these cards.

Dear Sir, I promise I won't continue bothering you and Ms tozer with these seemingly simple problems
Thans or your consideration.

Dear Ms. Tozer

After attempting to get PiFace Real Time Clock to install on Raspberry Pi Zero over the last two months, I've to the possibility that the INSTALL PROGRAM at:  http://github.com/piface/PiFace-Real-Time-Clock does not address the Zero Model. The following is an extraction from the install code:

#=======================================================================
# NAME: start_on_boot
# DESCRIPTION: Load the I2C modules and send magic number to RTC, on boot.
#=======================================================================
start_on_boot() {
    echo "Create a new pifacertc init script to load time from PiFace RTC."
    echo "Adding /etc/init.d/pifacertc ."

    if [[ $RPI_REVISION == "3" ]]; then
        i=1  # i2c-1
    elif [[ $RPI_REVISION == "2" ]]; then
        i=1  # i2c-1
    else
        i=0  # i2c-0
    fi

    cat > /etc/init.d/pifacertc  << EOF

(end of code)

Are these revisions referring to Software Revisions 2 and 3 or the Hardware Models 2 and 3 ?

Does anyone know if Piface RTC can be installed on to a RPi ZERO model or not. ?

Sorry for the persistence in my requests to you and the community but I'm running out of ideas but not patience.

Am I am able to accomplish this task or not.

Thank you.

PS. The commands that you suggested,, such as:

sudo systemctl is-enabled pifacertc

sudo systemctl -a

sudo systemctl start pifacertc

all return the statements "PiFace RTC "not added, "failed to be added", "cannot be started" or generally notfound.

Thanks for your help and hope someone out there will continue to respond.

Frank

A word on PI Revisions

if you run the command  " cat  /proc/cpuinfo" you will get a bunch on information returned including the revision value

Here is what I get on a Quark 1000 based Intel Galileo

processor       : 0

vendor_id       : GenuineIntel

cpu family      : 5

model           : 9

model name      : Quark SoC X1000

stepping        : 0

cpu MHz         : 399.088

cache size      : 16 KB

fdiv_bug        : no

f00f_bug        : no

coma_bug        : no

fpu             : yes

fpu_exception   : yes

cpuid level     : 7

wp              : yes

flags           : fpu vme pse tsc msr pae cx8 apic pbe nx smep

bugs            :

bogomips        : 798.17

clflush size    : 32

cache_alignment : 32

address sizes   : 32 bits physical, 32 bits virtual

power management:

if I run this on a PI i get this

processor       : 0

model name      : ARMv7 Processor rev 4 (v7l)

BogoMIPS        : 76.80

Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x0

CPU part        : 0xd03

CPU revision    : 4

 

 

processor       : 1

model name      : ARMv7 Processor rev 4 (v7l)

BogoMIPS        : 76.80

Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x0

CPU part        : 0xd03

CPU revision    : 4

 

 

processor       : 2

model name      : ARMv7 Processor rev 4 (v7l)

BogoMIPS        : 76.80

Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x0

CPU part        : 0xd03

CPU revision    : 4

 

 

processor       : 3

model name      : ARMv7 Processor rev 4 (v7l)

BogoMIPS        : 76.80

Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x0

CPU part        : 0xd03

CPU revision    : 4

 

 

Hardware        : BCM2709

Revision        : a02082

Serial          : 00000000a1243900

You can see the repeated parts for the 4 processor cores but also the revision statement near the end, you can see this does not match any of the test statements that simply expect a 2 or 3.... the reason for this is that Raspberry PI's made by sony have the 2, 3 style revision numbers, but the PI's made by Embest have the style above "a02082",

now this also seems to have moved to the later style for both. here is a table I found

Revision	Release Date	Model	PCB Revision	Memory	Notes
Beta	Q1 2012	B (Beta)	?	256 MB	Beta Board
0002	Q1 2012	B	1.0	256 MB
0003	Q3 2012	B (ECN0001)	1.0	256 MB	Fuses mod and D14 removed
0004	Q3 2012	B	2.0	256 MB	(Mfg by Sony)
0005	Q4 2012	B	2.0	256 MB	(Mfg by Qisda)
0006	Q4 2012	B	2.0	256 MB	(Mfg by Egoman)
0007	Q1 2013	A	2.0	256 MB	(Mfg by Egoman)
0008	Q1 2013	A	2.0	256 MB	(Mfg by Sony)
0009	Q1 2013	A	2.0	256 MB	(Mfg by Qisda)
000d	Q4 2012	B	2.0	512 MB	(Mfg by Egoman)
000e	Q4 2012	B	2.0	512 MB	(Mfg by Sony)
000f	Q4 2012	B	2.0	512 MB	(Mfg by Qisda)
0010	Q3 2014	B+	1.0	512 MB	(Mfg by Sony)
0011	Q2 2014	Compute Module	1.0	512 MB	(Mfg by Sony)
0012	Q4 2014	A+	1.1	256 MB	(Mfg by Sony)
0013	Q1 2015	B+	1.2	512 MB	?
0014	Q2 2014	Compute Module	1.0	512 MB	(Mfg by Embest)
0015	?	A+	1.1	256 MB / 512 MB	(Mfg by Embest)
a01040	Unknown	2 Model B	1.0	1 GB	Unknown
a01041	Q1 2015	2 Model B	1.1	1 GB	(Mfg by Sony)
a21041	Q1 2015	2 Model B	1.1	1 GB	(Mfg by Embest)
a22042	Q3 2016	2 Model B (with BCM2837)	1.2	1 GB	(Mfg by Embest)
900092	Q4 2015	Zero	1.2	512 MB	(Mfg by Sony)
900093	Q2 2016	Zero	1.3	512 MB	(Mfg by Sony)
a02082	Q1 2016	3 Model B	1.2	1 GB	(Mfg by Sony)
a22082	Q1 2016	3 Model B	1.2	1 GB	(Mfg by Embest)

As you can see most current boards don't have what the script is looking for.

To make this work for you, you can modify the script to just work for your board or change it to look for these additional identifiers.

Now technically this should still work even without modification on most latest boards as it will default t I2C-0 if the revision is not matched.

See the procedure just above start_on_boot i.e.

#=======================================================================

# NAME: set_revision_var

# DESCRIPTION: Stores the revision number of this Raspberry Pi into

#              $RPI_REVISION

#=======================================================================

set_revision_var() {

    revision=$(grep "Revision" /proc/cpuinfo | sed -e "s/Revision\t: //")

    RPI2_REVISION=$((16#a01041))

    RPI3_REVISION=$((16#a02082))

    if [ "$((16#$revision))" -ge "$RPI3_REVISION" ]; then

        RPI_REVISION="3"

    elif [ "$((16#$revision))" -ge "$RPI2_REVISION" ]; then

        RPI_REVISION="2"

    else

        RPI_REVISION="1"

    fi

}

It is only recognizing RPi CPUs for hardware models 2 and 3.  I cannot see what the "Revision" value at the bottom of /proc/cpuinfo is because I do not have an RPi zero.  You might be able to modify these two procedures and make it work.

Whether you are successful or not, I would suggest filing an issue at the github site if you have not yet already done so.  It would be great if you can develop a mod for the Pi Zero.  Good luck.

Agreed, if the Pi zero doesnt have a compatable revision that the install script can use, it should be easy enough to do the install manually.

Off the top of my head, I think the script was trying to work out the standard i2c port to register the real time clock with, different pi models must have different standard ports i2c-0, i2c-1 etc... I'll have a closer look when theres time unless someone else beats me to it!

If someone finds a way to do it manually, it should be easy enough to make a new script or suggest a modification to the standard script for other people to use.

-----------------------------

I can see me having to get a pi zero in the near future (just wish they had onboard wifi...)

Just realized my PI3 is using an I2C-1, not -0 so it would fail with this script.....

simply run i2cdetect -l to see what is available to you

Can you enable the i2c port using the raspi-config command and then do ls /dev

You should see either i2c-0 or i2c-1 in the list, could you let us know which one it is please.

Im going to try and re-write this script, rather than trying to determine the revision of the raspberry pi to workout which i2c port to address,

it can be simplified to ls /dev | grep "i2c" This should get the device directly rather than guessing based on the model.