Pi Zero Serial Terminal : stucked at waiting for UART ?

[Grégory Paul]

Hello,

I built a Pi Zero Serial Terminal for my RC2014 but I’ve got problem to make it work.

I copied the following files on the SD card :
- kernel.img from https://github.com/fbergama/pigfx/tree/RC2014/bin (branch rc2014),
- start.elf and bootcode.bin from https://github.com/raspberrypi/firmware/tree/master/boot

It boots but is stucked with the message "Waiting for UART data", see picture attached.
1/ What could be wrong ?

Also, I don’t see the "PIGFX Ready!" logo as explained in https://github.com/fbergama/pigfx/tree/RC2014#how-to-run
So I do not know if I’ve copied the right files on the SD card...

Another problem is that, at almost each boot, the message "No keyboard found" is shown. When disconnecting / reconnecting the keyboard and rebooting, it may print "Keyboard found".
I tried 2 different keyboards with same results.
2/ What can cause that ?

Best regards,
Grégory

[Spencer Owen]

Hi Grégory,

You've got the right files on the SD Card, because otherwise you wouldn't get as far as you have :-)

The early version of the PIGFX software only showed "PIGFX Ready!" when it started up.  The latest version has more debugging info (Like keyboard status) and the RC2014 logo, so you won't see the "PIGFX Ready!" message now.

The "Waiting for UART data" message means that the RC2014 hasn't sent any data out of it's serial port yet.  Push the reset button on the backplane to kick it in to life.

I have tried several different keyboards with the Pi software, and only 1 of them fails.  I really don't know what the difference is with that one, as it works fine on other machines - even on a Pi Zero running the Raspian OS.  I've not heard of any that sometimes work or sometimes fail.  Do you have another one to try?

Let us know how you get on.

Spencer

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/febf8af3-2f39-4a28-ba1d-b90b71877b93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Filippo Bergamasco]

Hi all,

I'm the PiGFX developer, sorry for the late reply. 

The readme is a little bit outdated so it's normal you don't read pigfx ready but some debug text on the keyboard status and so on.

The keyboard malfunction may be related to the specific type of keyboard you are using. Unfortunately the USB implementation is quite naive so it can fail if the keyboard doesn't behave exactly as expected by the protocol. It will be nice to see if another keyboard works properly to ensure that your issue is not related to the Pi hardware.

It is stuck at the "waiting for uart data" because it's effectively waiting for some data that is probably not arriving. Please double check your connections and try (if possible) with an oscilloscope or a uart dongle if your rc2014 is outputting something to the uart line. Also try to reset the CPU a couple of times without resetting the Pi. If everything fails please open an issue on GitHub so we can try together to fix the bug.

Good luck

- Filippo

To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAO93Pten5FTxoe0jTi5NJBjxQ2mOtoYi4nkvQXe13%2BxY3ymW1g%40mail.gmail.com.

[Grégory Paul]

Hello Spencer,
Thanks for the quick reply.

Pressing the "reset" button on the RC2014 causes the screen to go black with what seems a cursor at top of the screen (see attached picture).
Pressing keys on the keyboard doesn’t do anything (cursor is not moving at all).

I haven’t other keyboard to try but one isn’t working at all while another isn’t working at first boot but after disconnecting / reconnecting it, it works almost all times. It may be a USB connection issue...

Grégory

[Spencer Owen]

Hi Grégory,

One of the things I forgot to ask earlier is if you have a USB FTDI type adapter (Looks like you have from the photo you posted on Twitter).  If so, remove the Pi Module and plug the FTDI adapter in to the Serial Module, then run some terminal software (PuTTY, Minicom, Teraterm etc), to ensure that the RC2014 itself is running.

If the RC2014 come up with the Microsoft BASIC message and you can type programs in, then we need to troubleshoot the RC2014 to Pi connectivity.

If the RC2014 doesn't come up, then we need to do more fundamental troubleshooting.

Spencer

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/8173c4b7-5a81-4c89-b312-844a68d8c572%40googlegroups.com.

[Grégory Paul]

Hi Spencer,
Hi Filippo,

Yes, indeed, I’ve connected the FTDI adapter to the Pi terminal (with jumper to Pi when I tried to use the Pi).
I was able to use the Z80 when using the FTDI adapter connected on the Pi terminal when changing jumper to FTDI.

I tried as you said : by removing the Pi terminal and connecting the FTDI directly to the Z80 and launched minicom, it works as expected :

Z80 SBC By Grant Searle

Memory top?
Z80 BASIC Ver 4.7b
Copyright (C) 1978 by Microsoft
32382 Bytes free
Ok
10 print "Hello World"
list

10 PRINT "Hello World"
Ok
run
Hello World
Ok

I checked the connectivity from the RX / TX pin on the "motherboard" to the RX / TX pin on the Pi board and it seems ok...
What could I check ?

Thanks again for the support.

Grégory

[Spencer Owen]

Hi Grégory,

Well, it sounds like it all *should* work!  There really isn't much more to check.

Are the 10k and 22k resistors in the correct place?

It could be worth trying the Pi Module as a stand alone serial terminal.  Remove the module from the backplane, connect to the FTDI connector and run a couple of cables as shown on the very poor looking image attached.

Launch Minicom and you should be able to type on your computer and it'll show up on the monitor connected to the Pi, and if you type on the keyboard connected to the Pi, it should show up on your computer.

If that doesn't work, then there's only a few solder joints or the Pi itself that could be at fault.

Let us know how you get on.

Spencer

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/cbe04a6a-7877-4a50-ad74-c732c5f688a2%40googlegroups.com.

[Grégory Paul]

Hello Spencer,

I unplugged the Pi board, connect 2 cables from RX to TX and RX to TX like on the picture, plugged hdmi and keyboard, plugged the FDTI adapter to my computer, launched minicom but the result it didn’t worked.
I saw the same "waiting for UART".

So I unplugged everything and check the connection from pin board to jumper and then to Pi.

When putting back the jumper to "pi", the board pin 36 (RX from [1]) is connected to Pi GPIO 14 (from [2]) according to my multimeter.
However, the pin board 35 (TX from [1]) was not connected to Pi GPIO 14 (from [2]).

I thought it was an error so I unsoldered then resoldered the pin on both the jumper and the pi support but that didn’t fixed the connection.

Then I saw on [1] that GPIO 15 is not directly connected to pin 35 but pass thought the 10 KOhm resistor.
That may give bad result on my multimeter.

I stopped my investigation there, I’ll need to check it more deeply after a good night sleep :-)

[1] http://rc2014.co.uk/wp-content/uploads/2016/07/Pi-Zero-Terminal.pdf
[2] https://www.element14.com/community/servlet/JiveServlet/previewBody/68203-102-6-294412/GPIO.png

[Grégory Paul]

I’m continuing my investigation.
When setting RX/TX jumper to pi, the board pin 36 (RX from [1]) is connected to the pi GPIO 14
The board pin 35 (TX) is connected to 10 kOhm resistor and I can test a link from 22 kOhm resistor to GPIO 15.
So it seems connected as expected in [1].

I’ll add some pictures of my board into that post, if, by any chance, you may spot an obvious problem that I may have missed...

When trying again to connect the board directly to my computer using minicom, I’ve now got the same result as on my PI :
1/ the screen is printing "Waiting for UART...",
2/ when pressing a key on my computer, which sends a character to the Pi board, the screen goes black with a cursor sign on the top of the screen (like on the previous screenshot showing that problem when I tried it on the Z80),
3/ others key press doesn’t do anything and typing on the keyboard connected to the Pi board is also doing nothing at all (no "echo" on my computer)

I don’t understand what are the implication of that behavior...

Should I buy another Pi board in order to give another try on a fresh start ? (Pi board are not expensive and I bought more components than I need on the first board so...)

[1] http://rc2014.co.uk/wp-content/uploads/2016/07/Pi-Zero-Terminal.pdf

[Filippo Bergamasco]

Are you sure that your UART is set to 115200 8 N 1?

- Filippo

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/dead29ce-0aef-4f71-8d84-0c2ef6a6b453%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

<IMG_20161201_080101~01.jpg>

<IMG_20161201_080045~01.jpg>

<IMG_20161201_080034~01.jpg>

[Grégory Paul]

Yes, I think to.
Here’s a "screenshot" from configuration menu in minicom :

------------------------------------------------------------------------------------------------
Welcome to minicom 2.7                                                                                                                    
                                                                                                                                          
OPTI+-----------------------------------------------------------------------+                                                             
Comp| A -    Serial Device      : /dev/ttyUSB0                              |                                                             
Port| B - Lockfile Location     : /var/lock                                 |                                                             
    | C -   Callin Program      :                                           |                                                             
Pres| D -  Callout Program      :                                           |                                                             
    | E -    Bps/Par/Bits       : 115200 8N1                                |                                                             
    | F - Hardware Flow Control : No                                        |                                                             
    | G - Software Flow Control : No                                        |                                                             
    |                                                                       |                                                             
    |    Change which setting?                                              |                                                             
    +-----------------------------------------------------------------------+                                                             
            | Screen and keyboard      |                                                                                                  
            | Save setup as dfl        |                                                                                                  
            | Save setup as..          |                                                                                                  
            | Exit                     |                                                                                                  
            +--------------------------+    
------------------------------------------------------------------------------------------------

[Spencer Owen]

Everything looks ok in those photos - except for the missing jumpers, but I know you know about those. So it *should* work.

One other thing that might be worth trying before buying another Pi is to install Raspian and install Screen and use the Pi as a Linux terminal to prove if the hardware is working ok.  You will need an 8gb SD card and a WiFi dongle. See my Hackaday.io page for more info; https://hackaday.io/project/9567-5-graphics-card-for-homebrew-z80

If it works via Raspian then there is a problem with the PIGFX software on the SD card. If it doesn't work, then it could be a hardware problem with the Pi.

As you say, though, buying another Pi Zero is cheap... and you can never have too many Pi Zeros! :)

Spencer

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/dead29ce-0aef-4f71-8d84-0c2ef6a6b453%40googlegroups.com.

[Grégory Paul]

Hello Spencer,

Yes, I know about jumpers and have set them on FTDI or PI positing according my trial.

I already bought a second Pi zero because I thought I burned the first one when soldering (nothing worked at first).
However, the brand new Pi zero (without anything soldered on it) didn’t worked too so I found out it was the SD card which was malfunctioning.
I used another SD card and the brand new Pi worked (with Raspbian), as the one I soldered (that you see on the picture).
So I assume both Pi were functional.

It’s a good idea to test the Pi with screen program and I’ll try that this week-end.

I can also solder pins on the new Pi zero (not sure I have thoses parts in stock) and try this one.

But I talked in my previous post to buy another "Raspberry Pi Zero Serial Terminal for RC2014" PCB and try again to built a second one, if by any chance I broke something during soldering (not likely).

Thanks again for the support, I appreciate it (and I really want a standalone Z80 that I can connect on any TV !)
I’ll post my next status in following days.

[Filippo Bergamasco]

I'm trying to figure out what may be wrong with your setup. It's hard to think that is software related as all the pi zeros have exactly the same hardware (right?).

Anyway, when you eventually get the screen cleared with the cursor visible it means that at least one character has been received (maybe is not alphanumeric so it's not displayed). If you type something with the USB keyboard attached you should see the echo of what you are typing. Is it so? Otherwise it may be the software stucked at some point wating for USB interrupts.

If everything else fails, I can try to build a simpler version of PiGFX just to test the UART (no usb, no timer interrupts etc)

Filippo

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/7a1d703d-7db1-46d0-97a9-5b587ca418db%40googlegroups.com.

[Grégory Paul]

Hello Spencer,
Hello Filippo,

I installed raspbian on a SD card, configured a wifi dongle, installed screen, disabled default serial port on the pi ([1] is a great resource about that), connected my FTDI to the Pi (it had a jumper to select 3v3 or 5V for the TX port), launched screen on the Pi and `minicom -b 115200 -o -D /dev/ttyUSB0` on my laptop and it worked !

Character typed from my computer were printed on the screen connected to the pi and what I typed on the Pi was printed on minicom !

A picture of the setup is attached.

So it is definitively not a problem with the Pi hardware !

I’ll try to reformat my SD card and reinstall PiGFX with a kernel.img from branch rc2014 from [2] and start.elf and bootcode.bin from [3].
Is there a special version of those file for the Pi Zero (or is it the same files for all raspberry) ?

[1] http://raspberrypi.stackexchange.com/questions/47671/why-my-program-wont-communicate-through-ttyama0-on-raspbian-jessie
[2] https://github.com/fbergama/pigfx/tree/RC2014/bin
[3] https://github.com/raspberrypi/firmware/tree/master/boot

[Grégory Paul]

Yes, using that same setup with the SD card containing the kernel.img, start.elf and bootcode.bin, and using minicom as I did previously with raspbian, the same problem occurs :
1/ "Waiting for UART",
2/ when typing a character on my laptop, the screen connected to the PI goes black except what seems a cursor (but only the bottom of it).
3/ when pressing more characters, nothing changes...

So it seems there’s a problem with PiGFX.
Did I took the correct file (kernel.img from rc2014 branch) ?
May I try a previous version from an older commit ?

Grégory

[Spencer Owen]

Hi Gregory,

Attached is the 3 files I use on the SD cards that I ship out with the Pi Zero Module.  They should be the same as you are using, but give it a try to see if it gives different results.

Let us know how you get on.

Cheers

Spencer

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/5ce83ce6-8645-41ca-a5c1-8cbe9e514e2f%40googlegroups.com.

[Grégory Paul]

It worked !!!

Using the same setup (pi connected to FTDI, then to my laptop), I was able to type character that were printed on the screen connected to my Pi.

The kernel.img is the same as mine but bootcode.bin and start.elf where not, see md5sums below :

  Pi Zero RC2014 Master md5sum kernel.img  
9650a80833ea61e2258322afa139126d  kernel.img
➜  Pi Zero RC2014 Master md5sum /media/paulgreg/B3AE-D0C6/kernel.img
9650a80833ea61e2258322afa139126d  /media/paulgreg/B3AE-D0C6/kernel.img
➜  Pi Zero RC2014 Master md5sum bootcode.bin       
6cc6560c0178c10928d14b8768969dab  bootcode.bin
➜  Pi Zero RC2014 Master md5sum /media/paulgreg/B3AE-D0C6/bootcode.bin
5bbb5f25dfe16f2871d5defcc48ac9ff  /media/paulgreg/B3AE-D0C6/bootcode.bin
➜  Pi Zero RC2014 Master md5sum start.elf
30dcad553d1ea0aeb9f8604fd573fbd8  start.elf
➜  Pi Zero RC2014 Master md5sum /media/paulgreg/B3AE-D0C6/start.elf
186b36fccec077a2da1a1185d507e91e  /media/paulgreg/B3AE-D0C6/start.elf

I got my files from https://github.com/raspberrypi/firmware/tree/master/boot, isn’t it the right place ?

It’s a little late now but I’ll mount tomorrow the Pi into the Serial monitor board and give a (final I hope) try with the RC2014 !

Thanks a lot for your patience and support (and theses precious files !).

[Spencer Owen]

Excellent!  That's great news :-)  Also, slightly worrying news :-/

I guess the Raspberry Pi Foundation have changed something in their files that's stopped our code from working.  Filippo is going to be the best guy to work out what's different and what we need to do to catch up, but the easy option is for us to just supply the earlier revision if that works.

Anyway, thanks for your patience and fingers crossed that it all works as planned tomorrow.

Spencer

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/0947cdd3-a001-42dd-a1bb-eef83dc65eba%40googlegroups.com.

[Filippo Bergamasco]

Hi all,

I'm so sorry that I've been busy in the recent past so I haven't spotted this bug before. I'm still following this great community (unfortunately by just reading what all the amazing people is doing with the rc2014).

As Spencer said, there must be something different in the supplied firmware files. I particularly fear the GPU related parts but who knows, maybe they have just changed some default values that I'm not setting explicitly.

I'll definitely need to debug this with a JTAG dongle but it may take some time. In the meanwhile, I'll add the currently working files in the repository to avoid confusion to the new users (I don't think this breaks any copyright of the raspi foundation).

One last question: do you have any config.txt file inside the sd card? Maybe we can just solve by providing a pre-defined config file that explicitly sets all the possible options to some tested safe values.

- Filippo

To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAO93PtfJG-P2iC3BwSUt9P%3DrtnrLkMXQ1tPqq06Dtv0uUvU_Lg%40mail.gmail.com.

[Grégory Paul]

No problem Filippo, I’m happy you help me spot the problem !
No, I don‘t have any config.txt file on the SD card.

I updated my project page on hackaday and posted a picture of the Pi terminal working.
I’m really happy to have a stand alone RC2014.

My 8 years old kid is currently typing a simple BASIC programs (which is really cool) :-)

Thanks to both of you for that great project (rc2014 and PiGFX).
I hope to go a little further later (like learning and programming in z80 assembly) but first, I have a third arcade bartop to finish :-)

[Spencer Owen]

Thanks for the update, and I'm glad your RC2014 is now working as it should :-)

Sorry it's taken so long in working out what was wrong, but hopefully it will help others in the future.

Great write up on Hackaday too.  It always gives me a warm fuzzy feeling seeing photos of an RC2014 on there!  [Note to self: I should put more of my own stuff on there too!]

I love the arcade bartops too.  Which reminds me that I need to start work on my arcade table soon.  Soon... 

Spencer

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/e2b2cfdc-5ca5-4c78-bdae-bede58ae0584%40googlegroups.com.

[Filippo Bergamasco]

Sorry for reopening this thread. I've verified that something is wrong with the new raspi firmware files. Since it would take time to sort out the problem I've committed the old working files in the bin subdirectory of pigfx:

https://github.com/fbergama/pigfx/tree/RC2014/bin

In practice, by copying all the files from bin directory to the SD card should produce a full working pigfx system

Filippo

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAO93PtcR_AmDD7uB%3DZ%2B-xyBEZLEkgZKx_aHY1YEmm%2Bs6S4P-2Q%40mail.gmail.com.

[Spencer Owen]

Thanks for looking in to this Filippo,

Yeah, if the old firmware works, and the new one doesn't then it seems like a simple solution :-)  Besides, I'm guessing that the latest firmware doesn't add any features that PiGFX is likely to take advantage of.

Cheers

Spencer

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAK%2B%3DWr-qidQtNEUgQNEfZpZXsNeO_wmdPwDm5ymkGqyBen0YpA%40mail.gmail.com.

[Filippo Bergamasco]

The problem is that debugging would be time consuming as it's not a critical failure but just the UART not behaving as expected. 

Anyway, I'm working on reading the SD card files right now so expect some interesting improvements in the near future :)

- Filippo

To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAO93PtdHdYKezi7sWruKaoUg9%3DNfVXgVGNNU4aUFHJbZXntjAQ%40mail.gmail.com.

[D.J. Walker-Morgan]

I'd put my RC2014Mini on the side a while back as I'd been banging my head on this problem for ages. I kept thinking it was my kackhanded building that was the problem.

Thanks for the old firmware - That reduced another winterval project down to copying files and boom, working!...

Dj

[Spencer Owen]

Excellent to hear that you're all up and running!

I appreciate how frustrating it can be when things aren't working, but isn't it satisfying when you discover that it isn't your fault :-)

Cheers

Spencer

Dj

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/9c2ff2c0-5a12-406b-9865-9571f9781020%40googlegroups.com.

[graham...@aol.com]

I have a very similar problem. I've just finished putting some modules together (including the pi zero), and decided to hook them up for a quick test. I am also getting the 'waiting for UART' message using the pi official start.elf and bootcode.bin. When I tried the alternatives from Filippo Bergamasco, I get nothing at all. I've tried every combination I can, and found that the pi only gives me a screen output with the official files, the older of the 2 kernal files and no config.txt file (I'm using the composite output, BTW). I don't currently have an FTDI cable to check that, but wondered if anyone has any ideas? I should add that I'm using one of the very early zeros. Obviously I can do some more testing when I get a suitable cable, but if anyone knows of a set of files that works with an early pi zero, I would be grateful.

Thanks

Graham

On Tuesday, November 29, 2016 at 7:09:42 AM UTC, Grégory Paul wrote:

Hello,

I built a Pi Zero Serial Terminal for my RC2014 but I’ve got problem to make it work.

I copied the following files on the SD card :
- kernel.img from https://github.com/fbergama/pigfx/tree/RC2014/bin (branch rc2014),
- start.elf and bootcode.bin from https://github.com/raspberrypi/firmware/tree/master/boot

It boots but is stucked with the message "Waiting for UART data", see picture attached.
1/ What could be wrong ?

Also, I don’t see the "PIGFX Ready!" logo as explained in https://github.com/fbergama/pigfx/tree/RC2014#how-to-run
So I do not know if I’ve copied the right files on the SD card...

Another problem is that, at almost each boot, the message "No keyboard found" is shown. When disconnecting / reconnecting the keyboard and rebooting, it may print "Keyboard found".
I tried 2 different keyboards with same results.
2/ What can cause that ?

Best regards,
Grégory

[Filippo Bergamasco]

Hi Graham,

you can check if the PiGFX code is running properly by observing if the pi status led is blinking roughly once per second. Anyway, you are probably see nothing because the new config.txt I'm providing forces the HDMI output.

Try using all the files listed here: https://github.com/fbergama/pigfx/tree/RC2014/bin 

WITHOUT the config.txt (the pi should use the internal defaults if no config.txt is found).

Let me know if that solves the problem

Filippo

--

You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+unsubscribe@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/51ac559b-96a9-4f5a-b19c-771cea7050f2%40googlegroups.com.

[graham...@aol.com]

Thanks Filippo. I won't have time to try for a few days, but I'll let you know what happens as soon as I can.