AD2PI with R Pi 3?

[mflembeck]

I have downloaded the pre-built (3-17-16) image from your website and used sdformatter and Win32DiskImager (run as administrator) to create an image on an SD card. I then put the SD card into a new R Pi 3 and get no joy, just a steady red LED, and 4 slow green LED blinks, followed by 4 rapid blinks and a 4 color rectangle on the HDMI monitor. I know the R Pi 3 is ok as I have loaded a stock Raspbian image successfully via NOOBS. Besides bringing wifi and bluetooth to the table, is there anything else about the 3 that might keep your pre-built image from working? Any other suggestions? Thanks for any help.

[mathewss]

Just a stab in the dark as we dont have one yet. You did UnZip the image you downloaded?

I think if it were formatted correctly reinsert to windows will show a small fat partition with some text files and part of the boot loader.

YOu see any of this?

Re
Sean M

[kevin]

Unfortunately since we do not have a pi3 we are unable to test this - but if it continues to have trouble, you may have to boot our image on a different pi such as a pi2, and do an update and upgrade before it will work on a pi3.

Alternatively, you can try replacing the start.elf from here https://github.com/raspberrypi/firmware ... aster/boot on the sdcard

[berkinet]

I believe the Pi3 requires Jessie and the AD2* image is Wheezy. But, then again, I could be completely wrong.

[kevin]

Newest image from 3-17 should be Jessie Lite

[mflembeck]

Thank you for the suggestions. Yes, I did unzip the image and used Win32DiskImager to flash the SD card. When viewed from Windows the small partition is seen. After replacing the start.elf as suggested, some progress was made. The system now boots, but nginx fails to start. Also, have to figure out how to start wifi, so the board can be accessed remotely. I'm computer savvy, but a unix noob...

[kevin]

Well, until we happen to get one in our hands and figure it out, our image only supports up through the pi2 as per documentation - happy to help diagnose if you post some logs as to why nginx etc isn't starting.

[mflembeck]

So I have successfully accessed the AD2PI on a R Pi 3 via wifi using the following steps. I can't vouch that every step is required, but at the end of the path, things are working. Thanks to all for various clues that got me there. I did a sudo reboot after almost every step below, but I don't think its really required until the end...

1. Start with the AlarmDecoder modified Raspbian build on SD card (via SDFormater and Win32DiskImager) connected directly to hardwire ethernet (would not boot on my system)
2. Replace start.elf with the version at the link provided above (https://github.com/raspberrypi/firmware ... aster/boot) - now boots to command line.
3. Resize the partition using the raspi-config utility to take advantage of entire SD card space.
4. sudo apt-get update -to get package list updates (it did take multiple tries to get complete set of updates to 4.1.20 files (as of 3/30/16))
5. sudo rpi-update - to get firmware update
6. added missing files brcmfmac43430-sdio.txt and brcmfmac43430-sdio.bin to /lib/firmware/brcm - did this by copying files to SD card on Windows machine, and then sudo mv to /lib/firmware/brcm
7. sudo iwconfig wlan0 power off (stops wifi from shutting down when unused to save power)
8. sudo nano /etc/wpa_supplicant/wpa_supplicant.conf - to edit wifi config file:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network ={
ssid="your network name here"
psk="your network password here"
}
9. sudo nano /etc/network/interfaces - make sure wlan0 is available with following lines in the file:
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
10. sudo reboot
11. sudo ifconfig - to verify wlan0 is now listed
12, access https://alarmdecoder.local from another machine on the network
SUCCESS!

[twodeeman]

I see exactly this same problem with a Pi 2 model B v 1.2

Very disappointing.

--
n