Matrix Creator seems to be bricked (****Could not program FPGA)


#1

Hi there,
I could use some help over here.

I am trying to reinstall my Matrix Creator, but cannot access any of the sensors.

Going through all of the steps on the troubleshooting page, I realised, that I get the**** Could not program FPGAmessage.

When I run the fpga_info command, I get the following result:

    INFO: [/dev/matrixio_regmap] was opened
    MATRIX device has not been detected
    FPGA IDENTIFY = 0
    FPGA VERSION = 10c4c

Running the following says something about No JTAG chain:

     xc3sprog -c matrix_creator blob/system_creator.bit -p 1
     XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
     Free software: If you contribute nothing, expect nothing!
     Feedback on success/failure/enhancement requests:
     	http://sourceforge.net/mail/?group_id=170565 
     Check Sourceforge for updates:
     http://sourceforge.net/projects/xc3sprog/develop

     No JTAG Chain found

It’s a Raspberry Pi 3 B+ running Raspbian Stretch Desktop.

I am absolutely puzzled here. Is there any way to unbrick it?

Any help really appreciated.


#2

Few questions here Nils,

  1. Did you try the troubleshooting guide starting from a clean new Raspbian installation?
  2. Did you have access to sensors before this problem?

-Yoel


#3

Hi Yoel

  1. Yes, it is a clean installation.
  2. Yes, the sensors worked before. Matrix Creator was unused for a while.

#4

By the way: there are only some of the GPIO pins activated as listed on the troubleshooting page.

If this might be the reason for then Matrix creator not detected, then why aren’t those pins initiated correctly?


#5

Any ideas, which matrix software component activated or configures the GPIO pins?
That part seems to be disfunctional, so getting it running should lead to Matrix Creator being properly detected.


#6

No luck by today. Reinstalling everything without the Matrix One attached did not succeed.

Dear creators of Matrix Creator: on the troubleshooting page, there ist this link: " If you get **** Could not program FPGA , please contact us."

Here I am. Pls hlp. thx


#7

I would really like to see someone looking into this issue. It seems that this is a known issue, as there is a link reading " If you get **** Could not program FPGA , please contact us)." on the troubleshooting page.

I already started from a clean Raspbian installation, and the Matrix Creator was not detected from the beginning.

So, what are the steps to get the device detected again? Or is there a way to tell, if the thing is bricked and broken beyond chance of getting it back to life again?


#8

By the way: there are only some of the GPIO pins activated as listed on the troubleshooting page.

If this might be the reason for then Matrix creator not detected, then why aren’t those pins initiated correctly?

Hi Nils, sorry about the delayed response.

Can you share the terminal output when you tried the Hardware Test guide?. Why do you think the Creator has problems with the GPIO?

Another thing to note is that is this MATRIX Creator worked before, the F{GA programming was fine at some point. Do you have something currently connected to the external GPIOs like LEDs, servos, or other hardware? Have you before?

-Yoel


#9

Ok, well then, following Hardware Test Guide.

  1. Installed a fresh copy of
    Raspbian Stretch Lite
    Version: November 2018
    Release date:2018-11-13
    Kernel version:4.14

on a 32GB micro SD card

No, configuration, except enabled ssh and wifi.

Step 1:
matrixio-creator-init installed successfully and rebooted

Step 2: FPGA firmware status

$ sudo /usr/share/matrixlabs/matrixio-devices/matrix-init.bash
MATRIX device has not been detected
**** Could not program FPGA
MATRIX device has not been detected
sudo /usr/share/matrixlabs/matrixio-devices/fpga_info 
INFO: [/dev/spidev0.0] was opened
MATRIX device has not been detected
FPGA IDENTIFY = 0
FPGA VERSION = 10c4c
$ cd /usr/share/matrixlabs/matrixio-devices/
$ sudo ./fpga-program.bash 
MATRIX device has not been detected
**** Could not program FPGA
If you get **** Could not program FPGA, please contact us.

This is what I am doing right now.

Step 3: Test your MATRIX board
I actually skip this for now, as it does not seem to make sense, if the Matrix Creator is not detected.

Step 4: Raspberry Pi GPIO Status

sudo cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-53, parent: platform/3f200000.gpio, pinctrl-bcm2835:
 gpio-18  (                    |sysfs               ) out hi    
 gpio-26  (                    |sysfs               ) out hi    
 gpio-29  (                    |led0                ) out lo    

gpiochip1: GPIOs 128-135, brcmexp-gpio, can sleep:
 gpio-130 (                    |led1                ) out hi 

This is all I got, that is why I think that the GPIO configuration is not correct.

β€” end of hardware test β€”

If you get another result, you should configure your device with the rapsi-config command

Well, yes, please, … but how?


#10

No, there is nothing else connected to the external GPIOs, no LEDs, servos or whatsoever, and never have been.
It was only used for voice recognition before.


#11

so, doctor, any idea about the patient?


#12

So, currently my Matrix Creator seems to be, well, not dead (lights are blinking), but not detectable.

At least some support could actually help.


#13

My Matrix Creator is still not detectable.
Is ther any way I can rescue it?


#14

Hey Nils,

We are trying to replicate your GPIO output and will try to provide an update when we have more information.

Can you send us pictures of the front and back of your MATRIX Creator, the MATRIX Creator connected to your Pi, and let us know which blue LEDs are blinking when you power it? The LEDs have little numbers next to them.

Thanks,
Samreen


#15

Ok, here we go.

The LED blinking is on the left upper corner of the Atmel, labeled D48.


#16

Hi Nils,

Your MATRIX device looks okay.

What are the specs of your power source? The MATRIX Creator may not work properly if the power supply specs do not meet the requirements.


#17

Should there be more gpio devices shown in the gpio output?
Mine looks like:
sudo cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-53, parent: platform/3f200000.gpio, pinctrl-bcm2835:
gpio-4 ( |sysfs ) in hi
gpio-16 ( |sysfs ) out lo
gpio-17 ( |sysfs ) in hi
gpio-18 ( |sysfs ) out hi
gpio-19 ( |sysfs ) out hi
gpio-20 ( |sysfs ) out hi
gpio-21 ( |sysfs ) out hi
gpio-22 ( |sysfs ) in lo
gpio-23 ( |sysfs ) out hi
gpio-27 ( |sysfs ) in hi
gpio-29 ( |led0 ) out lo

gpiochip1: GPIOs 128-135, brcmexp-gpio, can sleep:
 gpio-130 (                    |led1                ) out lo   

Also, you can check the SPI devices are enabled by the following:
ls /dev/spi
/dev/spidev0.0 /dev/spidev0.1

And, to check the i2C devices that are enabled, install i2c-tools and run the following:
i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – 06 – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- 1c – -- –
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- 38 39 – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – 5f
60: 60 – -- – -- – -- – -- – 6a – -- – -- –
70: – -- – -- – -- – --

You can run raspi-config and then go to β€˜Interfacing Options’ to enable SPI and i2c if needed.


#18

Ok, currently I use simple 5V 1A power supply. I will try a bigger one.


#19

Yes, we generally use 5V 2.5A power supplies so that could definitely affect it. Let us know how it goes!