PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 8:57 am

Ah - I think I understand now. This bit of the command line:

Code: Select all

root=/dev/mmcblk0p6
tells me that this is a NOOBS card. The rest of the log shows me that your dtparam=spi=on is not being processed, because the config.txt you are editing is not the one that your OS firmware is using.

A standard OS distribution (e.g. Raspbian) comes with two partitions - VFAT for the firmware, and something else (ext4 for Linux) for the OS itself. NOOBS supports multiple OS's by dividing the card up into slices. NOOBS itself uses 4 partitions, the first of which is a VFAT firmware partition (called RECOVERY), while Raspbian installed under NOOBS is likely to use partitions 5 and 6. When your Pi boots, the firmware in the RECOVERY partition allows you to select an OS then triggers a reboot, leaving just enough information to allow the bootcode.bin to load the correct firmware for the selected OS.

When you put the NOOBS card in a PC it may only recognise the first VFAT partition, and any changes there will not affect the main OS (provided they don't stop the Pi from booting). NOOBS itself allows you to edit the config.txt for each of the OS installations, so that is one solution. Alternatively you can edit /boot/config.txt from within Linux (but keep reading...)

The above explanation doesn't fit the case where you have been editing /boot/config.txt from within Linux and it isn't making any difference. If that is your situation then there is another problem. /etc/fstab lists the filesystems and their mount points, and you should find an entry in there for /boot. For your NOOBS card the mount point for /boot should be /dev/mmcblk0p5, but there was a batch of NOOBS cards made for which that entry ends up saying /dev/mmcblk0p1, which is the partition for NOOBS's own firmware. If this is the case for you, the easiest way to repair this is to update to the latest Raspbian:

Code: Select all

sudo apt-get update
sudo apt-get upgrade

Soulafein
Posts: 14
Joined: Thu Jul 23, 2015 9:35 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 10:22 am

In my /etc/fstab
proc /proc proc defaults 0 0
/dev/mmcblk0p5 /boot vfat defaults 0 2
/dev/mmcblk0p6 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, so no using swapon|off from here on, use $
So it' seems to be fine.
How can I change config.txt that it will be processed?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 10:25 am

Weird. Can you post /boot/config.txt, so I can read it all?

Soulafein
Posts: 14
Joined: Thu Jul 23, 2015 9:35 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 10:38 am

My /boot/config.txt
# For more options and information see
#http://www.raspberrypi.org/documentatio ... fig-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800


# NOOBS Auto-generated Settings:
hdmi_force_hotplug=1
config_hdmi_boost=4
overscan_left=24
overscan_right=24
overscan_top=16
overscan_bottom=16
disable_overscan=0
dtparam=spi=on
Last edited by Soulafein on Fri Jul 24, 2015 11:23 am, edited 1 time in total.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 10:40 am

@jojopi - I've pushed the i2c-rtc patch to all current branches, and it will be in the next release. It's a bit surprising this one hasn't been reported before.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 12:16 pm

@Soulafein I'm stumped. Your config.txt looks fine, but I would suggest you don't put any modifications after the "NOOBS Auto-generated Settings" line just in case they get lost.

Let's try to establish for certain which config.txt is being used. Reboot into recovery mode (hold down Shift during boot), select each installed in turn and use the "Edit config" option, then add a line at the top of the file saying something like "dtparam=raspbian", using a different string for each file. The idea is that "sudo vcdbg log msg" should then show an error message matching one of these files.

Let me know what you find.

Soulafein
Posts: 14
Joined: Thu Jul 23, 2015 9:35 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 12:57 pm

I ran recovery Mode, added the line dtparam =raspian at the top of config.txt and sudo vcdbg log msg results in:
000884.856: gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined
000884.880: gpioman: gpioman_get_pin_num: pin LEDS_NAND_ACTIVITY not defined
000884.903: gpioman: gpioman_get_pin_num: pin LEDS_USB_ACTIVITY not defined
000884.924: gpioman: gpioman_get_pin_num: pin LEDS_FATAL_ERROR not defined
000884.944: gpioman: gpioman_get_pin_num: pin LEDS_APP_OK not defined
000884.964: gpioman: gpioman_get_pin_num: pin LEDS_APP_FAILED not defined
000884.985: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_AUTH not defined
000885.006: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_UNAUTH not defined
000885.026: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_ON not defined
000885.045: gpioman: gpioman_get_pin_num: pin LEDS_DVI_ON not defined
000885.065: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_HPD_UP not defined
000885.087: gpioman: gpioman_get_pin_num: pin LEDS_REMOTE_CONTROL not defined
000885.109: gpioman: gpioman_get_pin_num: pin LEDS_ARM_CONTROLLED not defined
000938.950: *** Restart logging

000939.862: Read command line from file 'cmdline.txt'
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait

000944.387: Loading 'kernel7.img' from SD card
001175.322: Kernel trailer DTOK property says yes
001175.451: Loading 'bcm2709-rpi-2-b.dtb' from SD card
001200.716: dtparam: raspian=true
001201.698: Unknown param 'raspian' - ignored
001202.283: dtparam: spi=on
001205.067: dtparam: arm_freq=900000000
001259.604: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
003381.474: vchiq_core: vchiq_init_state: slot_zero = 0xfa800000, is_master = 1
003385.016: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
003388.894: gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined
003388.917: gpioman: gpioman_get_pin_num: pin LEDS_NAND_ACTIVITY not defined
003388.939: gpioman: gpioman_get_pin_num: pin LEDS_USB_ACTIVITY not defined
003388.959: gpioman: gpioman_get_pin_num: pin LEDS_FATAL_ERROR not defined
003388.981: gpioman: gpioman_get_pin_num: pin LEDS_APP_OK not defined
003389.003: gpioman: gpioman_get_pin_num: pin LEDS_APP_FAILED not defined
003389.023: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_AUTH not defined
003389.045: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_UNAUTH not defined
003389.066: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_ON not defined
003389.089: gpioman: gpioman_get_pin_num: pin LEDS_DVI_ON not defined
003389.110: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_HPD_UP not defined
003389.132: gpioman: gpioman_get_pin_num: pin LEDS_REMOTE_CONTROL not defined
003389.152: gpioman: gpioman_get_pin_num: pin LEDS_ARM_CONTROLLED not defined
003389.525: TV service:host side not connected, dropping notification 0x00000002, 0x00000002, 0x00000039
After that lsmod shows spi_bcm2708 and in /dev/ I found spidev0.0 and 0.1.
I assumed that's a good sign ;)
You are magician !!
I am truly grateful, thank You!!! till next time ;)

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Jul 24, 2015 1:02 pm

That's unexpected - going into recovery mode and editing config.txt must have fixed something. You should now be able to go back and remove the "dtparam=raspian" line.

nebula
Posts: 5
Joined: Mon Dec 02, 2013 6:04 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Wed Jul 29, 2015 2:04 am

I've run into a weird SPI issue after switching to spi-bcm2835 from 2708. Don't have a scope, but it feels like the behavior of CE0 is not correctly set when you change spidev mode from 1 to 0 without reloading the driver. Reverting to 2708 fixes it.

Run Program B (SPI_MODE_0). OK.
Run Program A (SPI_MODE_1). OK.
Run Program B (SPI_MODE_0). Communication error.
Reload spi_bcm2835 via modprobe, Program B works again!

capesp
Posts: 1
Joined: Tue Jul 28, 2015 10:14 pm

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Wed Jul 29, 2015 5:14 pm

@Soulafein and @PhilE

The same problem presented itself to me with identical symptoms. The problem exists solely with Raspbian on the NOOBS included with the Raspberry Pi2.

Code: Select all

cat /proc/version
Linux version 3.18.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015
The latest Rapsbian OS was downloaded and copied to another SD card. Booting into Raspbian and configuring the system through 'sudo raspi-config' successfully loaded the SPI and I2C drivers.
https://www.raspberrypi.org/downloads/

Code: Select all

cat /proc/version
Linux version 3.18.11-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #781 SMP PREEMPT Tue Apr 21 18:07:59 BST 2015
The output from 'lsmod' also shows the I2C and SPI drivers are properly loaded:

Code: Select all

lsmod
Module                  Size  Used by
cfg80211              386508  0
rfkill                 16651  1 cfg80211
snd_bcm2835            18649  0
snd_pcm                73475  1 snd_bcm2835
snd_seq                53078  0
snd_seq_device          5628  1 snd_seq
snd_timer              17784  2 snd_pcm,snd_seq
snd                    51038  5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device
i2c_bcm2708             4990  0
spi_bcm2708             5137  0
evdev                   9950  3
uio_pdrv_genirq         2958  0
uio                     8119  1 uio_pdrv_genirq
A post on another site provides information about SPI clock problems when the RPi2 is overclocked. The solution is included with the complete description of the problem at the link below:
https://pi-plates.com/the-problem-with- ... e-spi-bus/

capesp
--

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Mon Aug 10, 2015 3:37 pm

@capesp: When I saw @Soulafein's post I thought it might be one of the first Pi 2 NOOBS cards, but if that were the case then /etc/fstab would still have /boot pointing at /dev/mmcblk0p1, which it didn't. Plus, the build date of his kernel - "Tue Apr 21" - is much too late, and an rpi-update to a newer kernel would have fixed it. But you are right that you can get similar symptoms from such a NOOBS card.

Dart
Posts: 10
Joined: Thu Aug 07, 2014 10:59 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Mon Aug 10, 2015 7:10 pm

I understand what is being done here, however why not make available the previous Raspbian releases and older kernel releases. Support is not needed for them since they were working perfectly for those of us that designed projects around them

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4752
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Mon Aug 10, 2015 7:37 pm

Dart wrote:I understand what is being done here, however why not make available the previous Raspbian releases and older kernel releases. Support is not needed for them since they were working perfectly for those of us that designed projects around them
http://downloads.raspberrypi.org/raspbian/images/

User avatar
JohnBeardmore
Posts: 196
Joined: Thu Nov 15, 2012 11:03 pm
Location: Derbyshire UK.
Contact: Website

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Aug 28, 2015 4:48 pm

Given that the message at the top of this post says

>What about "w1-gpio"?
>Slightly more complicated. If you require the external pullup enable pin, use:
>"dtoverlay=w1-gpio-pullup,gpiopin=<x>,extpullup=<y>"
>otherwise use:
>"dtoverlay=w1-gpio,gpiopin=<x>"

Presumably then you can now use any GPIO pin for one wire connections, but can you add multiple lines so that you can use more than one pin at a time for one wire buses ?

Thanks, J/.
Author of oBeMS open source Building energy Management System.
Automatic Meter Reading (AMR), Building Management System (BMS),
Building Energy Management System (BEMS), Infrastructure Control System (ICS).
See: http://t4sustainability.co.uk/oBeMS/

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Aug 28, 2015 8:10 pm

Perhaps eventually, but not yet. As it stands today, the second overlay will overwrite the first. Think of overlays as zip files containing files (Devices Tree properties) in directories (DT nodes). Overlay parameters let you change the property (file) contents, but not the file or folder names, so you can see why using an overlay twice doesn't do anything useful.

It's my aim to create a more flexible overlay mechanism that will allow nodes to be renamed, but in the meantime you could try by creating a second overlay that uses a different node name. Try this:

Code: Select all

sudo apt-get update
sudo apt-get install device-tree-compiler
curl https://raw.githubusercontent.com/raspberrypi/linux/rpi-4.0.y/arch/arm/boot/dts/overlays/w1-gpio-overlay.dts | sed "s/onewire@0/onewire@1/g" | sed "s/w1_pins/w1_pins_1/g" | sudo dtc -@ -I dts -O dtb -o /boot/w1-gpio-1-overlay.dtb
Then try using w1-gpio-1 in parallel with w1-gpio. Note - I haven't tried this, but it's worth a try.

User avatar
JohnBeardmore
Posts: 196
Joined: Thu Nov 15, 2012 11:03 pm
Location: Derbyshire UK.
Contact: Website

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Aug 28, 2015 8:22 pm

Thanks ! I'll give it a go when I've rebuilt the system.

Cheers, J/.
Author of oBeMS open source Building energy Management System.
Automatic Meter Reading (AMR), Building Management System (BMS),
Building Energy Management System (BEMS), Infrastructure Control System (ICS).
See: http://t4sustainability.co.uk/oBeMS/

sheriff
Posts: 13
Joined: Thu Jul 16, 2015 2:20 pm
Location: Warsaw

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Fri Sep 04, 2015 9:57 pm

I have installed a newest version of kernel: 4.1.6-v7+ yesterday and now I have a problem with 1wire.
I am using DS2482 +DS18B20, I have tested diff configs in config.txtx and modules. When I switch off DT I just can see w1_bus_master1 and no sensors. When I switch on DT I can see strange addresses with all "0"s
Which parameters in config and modules do I need to use to be able to see sensors ?

Previously I use such modules:

Code: Select all

snd-bcm2835
i2c-bcm2708
i2c-dev
rtc-ds1307
w1-gpio
w1-therm
ds2482
and config:

Code: Select all

dtparam=i2c_arm=on
dtparam=i2c1=on
dtparam=i2c0=on
dtparam=spi=on
dtoverlay=w1-gpio
device_tree=

User avatar
DougieLawson
Posts: 30501
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Sat Sep 05, 2015 8:02 am

Get rid of that

Code: Select all

device_tree=
line, it's causing your problems.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

Since 2012: 1B*5, 2B*2, B+, A+, Zero*2, 3B*3

Please post ALL technical questions on the forum. Do not send private messages.

sheriff
Posts: 13
Joined: Thu Jul 16, 2015 2:20 pm
Location: Warsaw

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Sun Sep 06, 2015 12:54 pm

I have tried with DT (so I have commented "device_tree=") and without. I just copy-paste last config when I tied without DT.

z1s
Posts: 4
Joined: Sun Sep 20, 2015 5:29 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Sun Sep 20, 2015 5:49 am

I am using a relatively new Raspberry Pi2 and trying to follow the Adafruit Tutorial found here:
https://learn.adafruit.com/adafruit-16- ... on-library

I seem to be having i2c address difficulties.

I've tried to follow the device tree advice but I'm probably missing something. Any advice would be greatly appreciated. Reading through this thread today has been intense. Many thanks for your consideration!



With /boot/config.txt additions:

overscan_top=16
overscan_bottom=16
disable_overscan=0
dtparam=spi=on
dtparam=i2c_arm=on

dtparam=i2c0=on
dtparam=i2c=on
dtparam=i2c_vc

#device_tree_param=i2c=on0=on

#device_tree=



Addresses look like this:


pi@raspberrypi ~ $ sudo i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
pi@raspberrypi ~ $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --





With /boot/config.txt additions:

overscan_top=16
overscan_bottom=16
disable_overscan=0

dtparam=spi=on
dtparam=i2c_arm=on

dtparam=i2c1=on

#dtparam=i2c=on
#device_tree_param=i2c=on0=on
#device_tree=

Addresses look like this:

pi@raspberrypi ~ $ sudo i2cdetect -y 0
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory
pi@raspberrypi ~ $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Sun Sep 20, 2015 6:12 pm

Your settings are a bit confused, which is understandable having read the Adafruit guide, but I think you have done enough to be able to see the HAT if it is connected and working. The fact that you can scan i2c-1 using i2cdetect shows that your system is correctly configured. The fact that nothing is appearing suggests that the HAT is absent, incorrectly plugged in or faulty.

For the record, all you need to enable i2c1 on a Pi2 is:

Code: Select all

dtparam=i2c_arm=on
The named versions of the interfaces (i2c_arm and i2c_vc) are preferred because they do the right thing on all Pi's (original Pi Model B's have the roles reversed).

It is better not to enable the kernel's use of i2c_vc (i2c0 on a Pi2) unless you are sure you need it because it will interfere with any camera you have attached.

z1s
Posts: 4
Joined: Sun Sep 20, 2015 5:29 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Tue Sep 22, 2015 3:23 pm

Thank you. I greatly appreciate your advice. Glad to know I didn't do anything egregious with the config file and the library installation.

I will check the soldering on the hat but visually it looks fine. argh!

cheers!

z1s
Posts: 4
Joined: Sun Sep 20, 2015 5:29 am

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Wed Sep 23, 2015 3:58 pm

Well I looked at the soldering and it looks fine I tested the gpio pins with a breakout stacked on top of the motor hat and could get an led to to light on all of them (even though I can't get the led to light on gpio 23 without the motor hat!)

I find that if I hold the hat perfectly straight above the pins and apply a bit of pressure
I can get addresses from sudo i2cdetect -y 1:

40: 40
70: 70

which is what I think is correct.

So now the question is why the connection requires such physical finessing. Is this normal or is this just a faulty hat connector or raspberry pi physical pin?

Thanks again for any advice.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1420
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Wed Sep 23, 2015 8:52 pm

It does sound like a poor contact, either in the connector or on the HAT. I'm discounting the Pi because you were able to light the LED from the GPIO pins (and Sony's quality control).

I think you should contact Adafruit.

David Blythman
Posts: 1
Joined: Sat Oct 03, 2015 2:57 pm

Re: I2C, SPI, I2S, LIRC, PPS, stopped working? Read this.

Sat Oct 03, 2015 3:22 pm

+1 for the recovery mode edit of config.txt

My problem with I2C was no devices in /dev. lsmod showed the two i2c modules were present. The entries in /boot/config.txt looked fine. I upgraded the firmware and went from 3.18.7 to 4.1.7. I did the apt-get update / upgrade and got a shed load of stuff. I even added a device to the i2c bus. None of this made any difference. No i2c device ever turned up in /dev.

More in desperation than hope I followed the procedure above given to @soulafein. On the first boot after the edit in recovery mode the i2c1 device turned up in /dev. I took the dtparam=raspbian line out again by editing in raspbian. On reboot, the i2c1 device was still present. It was still there after a power cycle.

My setup is a brand new B+ and prepared NOOBS card first used today. It seems to me that as supplied, something is not quite right and the only way to fix it is to use the recovery config editor which does something subtle and unseen which fixes the problem.

Return to “Troubleshooting”

Who is online

Users browsing this forum: BangoSkank46290, TrantorT and 51 guests