Hi Everybody!
I' received few time ago a Rock64 2G I'll like o use as media server
I'm also trying to connect GPIO to a prototyping board through a ribbon cable 28AWG 40wires (similar to the ones once used for ATA disk) but as soon as I try to connect this cable I have loads of error
Code: Apr 23 09:19:55 rock64 kernel: [ 68.768983] mmcblk1: error -84 transferring data, sector 1723920, nr 32, cmd response 0x900, card status 0x0
Apr 23 09:19:55 rock64 kernel: [ 68.784147] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.817032] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.818136] mmc1: tried to reset card
Apr 23 09:19:55 rock64 kernel: [ 68.819089] mmcblk1: error -5 transferring data, sector 1723920, nr 32, cmd response 0x900, card status 0xb00
Apr 23 09:19:55 rock64 kernel: [ 68.820177] mmcblk1: retrying using single block read
Apr 23 09:19:55 rock64 kernel: [ 68.821655] mmcblk1: error -84 transferring data, sector 1723921, nr 31, cmd response 0x900, card status 0x0
Apr 23 09:19:55 rock64 kernel: [ 68.837149] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.870031] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.871150] mmc1: tried to reset card
Apr 23 09:19:55 rock64 kernel: [ 68.874435] mmcblk1: error -110 sending status command, retrying
Apr 23 09:19:55 rock64 kernel: [ 68.875149] mmcblk1: error -84 transferring data, sector 1723927, nr 25, cmd response 0x900, card status 0x0
Apr 23 09:19:55 rock64 kernel: [ 68.891146] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.924033] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.925152] mmc1: tried to reset card
Apr 23 09:19:55 rock64 kernel: [ 68.928530] mmcblk1: error -110 sending status command, retrying
Apr 23 09:19:55 rock64 kernel: [ 68.929225] mmcblk1: error -84 transferring data, sector 1723935, nr 17, cmd response 0x900, card status 0x0
Apr 23 09:19:55 rock64 kernel: [ 68.945150] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.978031] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 68.979163] mmc1: tried to reset card
Apr 23 09:19:55 rock64 kernel: [ 68.980039] mmcblk1: error -84 transferring data, sector 1723935, nr 17, cmd response 0x900, card status 0x0
Apr 23 09:19:55 rock64 kernel: [ 68.981151] blk_update_request: I/O error, dev mmcblk1, sector 1723935
Apr 23 09:19:55 rock64 kernel: [ 68.990404] mmcblk1: error -5 transferring data, sector 1723920, nr 8, cmd response 0x900, card status 0x0
Apr 23 09:19:55 rock64 kernel: [ 69.006146] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 69.039027] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Apr 23 09:19:55 rock64 kernel: [ 69.040152] mmc1: tried to reset card
the wired thing is that nothing is connected on the other side of ribbon cable when I get this error....
Thanks for any help or advice
has anybody encountered this problem?
(05-03-2018, 03:49 AM)viguzzz Wrote: has anybody encountered this problem?
I have a rpi gpio extention cable and breadboard adapter I can try, so will try this later today. Does this happen when you *ONLY* plug in the ribbon to the rock64, or when you connect the ribbon to the "prototyping board" (is that a breadboard by any chance, and if so, how does it connect. Via a adapter that straddles the middle seperator of the breadboard? Just chacking that you're not shorting the two columns of the header together accidentally...
Thanks pfeerick,
I'm going to use a kind of breadboard with adapter (adafruit cobbler).
This issue happens as soon as i connect the ribbon *ONLY* with no adapter and nothing else on the other side.
I've already checked insulation on cable's wires (are all about Mega ohms one each other) and I've tried with several cables with same result.
Sounds suspiciously like a short in the actual connector going to the GPIO pins. If you haven't connected the other end to a breadboard all you doing is extending the actual GPIO pins so any reading should be the same with or without the ribbon cable connector at the Rock64 board. Try a different cable just to rule it out.
Have you tested voltages at the GPIO pins with and without the ribbon cable attached.
05-04-2018, 05:42 PM
(This post was last modified: 05-04-2018, 05:44 PM by pfeerick.)
(05-04-2018, 02:48 PM)Rocklobster Wrote: Sounds suspiciously like a short in the actual connector going to the GPIO pins. If you haven't connected the other end to a breadboard all you doing is extending the actual GPIO pins so any reading should be the same with or without the ribbon cable connector at the Rock64 board. Try a different cable just to rule it out.
Have you tested voltages at the GPIO pins with and without the ribbon cable attached.
I'm getting the same results on my setup. https://pastebin.com/JXg8mCc4 The only (!!) difference is I plugged in the adapter plate to the ribbon as I needed to be able to disable the SPI Flash as there is a bug in the uboot currently loaded on it.
I think it can only be one of three things... something connected/shorted on the adapter board, something going on in the ribbon, or it could perhaps be adding noise or capacitance or something to the lines used for the SD card, as the pins 32.32,35,36,37,38,40 on the 40 pin Pi-2 bus are shared with the SD card. I'm inclined to think the latter, as there is nothing visibly wrong with the adapter or ribbon.
All you can do is check voltage ans resistance on the GPIO pins before and after you have the ribbon cable inserted. A dry solder joint on the board can cause this too as soon as any pressure is applied ie the pressure of the ribbon cable connector plugged in.
(05-04-2018, 05:42 PM)pfeerick Wrote: (05-04-2018, 02:48 PM)Rocklobster Wrote: Sounds suspiciously like a short in the actual connector going to the GPIO pins. If you haven't connected the other end to a breadboard all you doing is extending the actual GPIO pins so any reading should be the same with or without the ribbon cable connector at the Rock64 board. Try a different cable just to rule it out.
Have you tested voltages at the GPIO pins with and without the ribbon cable attached.
I'm getting the same results on my setup. https://pastebin.com/JXg8mCc4 The only (!!) difference is I plugged in the adapter plate to the ribbon as I needed to be able to disable the SPI Flash as there is a bug in the uboot currently loaded on it.
I think it can only be one of three things... something connected/shorted on the adapter board, something going on in the ribbon, or it could perhaps be adding noise or capacitance or something to the lines used for the SD card, as the pins 32.32,35,36,37,38,40 on the 40 pin Pi-2 bus are shared with the SD card. I'm inclined to think the latter, as there is nothing visibly wrong with the adapter or ribbon.
just to update tests:
Double checked the cable connected to the adaptor and the impedence between contacts is about Mohms
Verified voltage on Rock64 PI-2 contact with nothing connected and later voltage on adaptor edges connected to Rock64 only: no changes
now a question: may using eMMC solve this avoiding noise on contacts pfeerick mentioned?
Thanks all!!
As a last resort could use individual connectors along these lines http://www.google.ie/search?q=gpio+cable...5519375744
Could help to isolate the possibility of interference as you can test individual pins in your projects without having all the pins connected on the ribbon cable at the same time.
I assume GPIO is correctly configured at boot time. I do recall a blob file that could be used in the Raspberry Pi board to configure GPIO and a firmware configuration that could be called from sudo raspi-config but I'm not sure how it's handled with the Rock64.
Maybe finding a Distro that handles this might be the answer here.
(05-05-2018, 05:38 AM)Rocklobster Wrote: I assume GPIO is correctly configured at boot time. I do recall a blob file that could be used in the Raspberry Pi board to configure GPIO and a firmware configuration that could be called from sudo raspi-config but I'm not sure how it's handled with the Rock64.
Think the GPIO stuff is handled by overlays, borrowed from the Raspberry Pi. Prior to 0.6.27, I'm pretty sure the GPIOs were all enabled for simple input/output stuff via sysfs.
Rocklobsters single wire connectors suggestion is good... you can get them easily on places like eBay, Aliexpress and Amazon really cheaply... good search keywords are "dupont breadboard"... as they are dupont style connectors and commonly used on prototyping breadboards.
i.e. https://www.ebay.com/itm/40X-Breadboard-...3115552438 where you can choose the length and connector type... the male to female type mean you don't even need the adapter plate to connect to breadboard. It's always handy to have a set of each combination if you're actively doing stuff on breadboards... they always come in handy! 
|
