No Output on DGT3000

[BrianL]

I converted the DGT3000 to a DGTPI, but I don't get an output  using  DGTPI31.

I know it's not the image because I got the same problem with other earlier images.

I also know it's not the wiring  because if I comment out the RP4 section in config.txt it works ok, but is this limiting the performance of picochess.?

I'm using a Raspberry PI 4b.

Thanks

[RandyR]

Brian,

Which image are you using?

Randy

[BrianL]

DGTPI31 from this link  https://drive.google.com/file/d/10wbhRnu3FqPRVdwvbsB7LvbJFlTPMuvX/view?usp=sharing

[Randy Reade]

Let's try this again:

That's the PicoChessWeb version. Perhaps DirkS or someone using that image with the DGTPi can assist.

Randy

--
You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/sHx3t7yF-UU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/21a747a3-73d2-4acb-b4d8-a0f6fe9d7438n%40googlegroups.com.

[BrianLoxton]

OK, I don't know what the difference is between versions. I assumed because it was 31, it was the latest.

I downloaded and tried this image PicoV3DGTPiDesktop_Bullseye.

I get the same symptoms.

To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/CAE5WduuUGrSRphDFJOqDPRumwfJiHcpJNuDcUwn5r7LiHgbkEg%40mail.gmail.com.

[Randy Reade]

Can you paste your config.txt?

Randy

[BrianLoxton]

Attached is the one from the image. without any changes.

and the version that works after I comment out the Pi4 section has just these changes

#[pi4]
# Run as fast as firmware / board allows
#arm_boost=1
#core_freq=500
#core_freq_min=500

--

You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/sHx3t7yF-UU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/CAE5Wduth1iZaVpbQ0_No5BwHDfnmX4wZhD4VZ4uVu2R7TDv-Tg%40mail.gmail.com.

[Randy Reade]

OK. Remove the first [All] and the blank line below it, in the original file.

You received this message because you are subscribed to the Google Groups "PicoChess" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/CAGc%2Bgc85jsaMckHT59ofLUmLBzgPQCq2YiqO0S02EnoGB8aFTA%40mail.gmail.com.

[Dirk Sommerfeld]

I use a pi3B+ in my dgtpi31. This one works from the scratch. I think that Alan has also a Pi4 in his scallypi. His first version runs also before I convert him a web version to a dgtpi. Did you can confirm that your powersupply is strong enough for a Pi4? 5V3A? That is one of the master issues for all pi4 users. I know it looks like it runs also with a 2A Powersullpy but this brings some negative effects.

Dirk

[BrianLoxton]

Ok. I tried that but it made no difference. so I reverted back to commenting the PI4 section out. and it works again.

It's not a major problem, I just thought it strange that given the exact same image and hardware as everyone else, I seem to be the only one with this issue.

Thanks anyway.

To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/CAE5WduuvZCqfY-w%3DAQashcARd6skvgXNOMBSof_HXd7dJURACw%40mail.gmail.com.

[BrianLoxton]

Mine also worked when I used a PI3b+

I only had this issue since upgrading to a PI4b. I am using an authentic Raspberry PI 3A PSU, so should be ok.

But everything works great if I comment out the PI4 section.

I Was just interested if anyone else had similar symptoms.

Thanks

To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/4a67aa93-de92-4e62-a1b3-b7e5968533e8n%40googlegroups.com.

[Randy Reade]

Perhaps something has changed in the RPi4b firmware. I only have the original RPi3b in my DGTPi. There is an old thread on here from Lucas where he determined you needed the RPi4b core freq at 500 MHz. Maybe that doesn't work any more. I'll be interested if you don't run into any issues with the clock display or buttons.

Randy

[Randy Reade]

Can you run a test? Uncomment the Pi4 section and in a terminal type:

cd /opt/picochess/etc

sudo ./dgtpicom "Hello" 1

Do you have an error?

You received this message because you are subscribed to the Google Groups "PicoChess" group.

To unsubscribe from this group and stop receiving emails from it, send an email to picochess+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/CAGc%2Bgc8o7ypNNbez208xXXV5hRga5qeqfs4Td7bt0cWepSJwFA%40mail.gmail.com.

[Dirk Sommerfeld]

Brian, could you please test this without the pi4 section?

#core_freq=250

#core_freq_min=250  

core_freq=500 

core_freq_min=500

[Scally]

Hi all,

Using DirkS image, my settings are as DirkS last post with my RPi 4 inside my DGT Pi.

Al.

[RandyR]

So I did some reading. The two [all] sections in config.txt is correct and good practice. See here.

Randy

[BrianL]

Thanks for the help on this. I tried removing the PI4 section and adding lines 

#core_freq=250

#core_freq_min=250  

core_freq=500 

core_freq_min=500

but it made no difference.

 so I changed it to 

#core_freq=250

#core_freq_min=250  

core_freq=400 

core_freq_min=400

and that works. so It appears to be an I2c timing issue.

[Randy Reade]

Once again:

Go back the original config.txt (where it's failing) and in a terminal type:

cd /opt/picochess/etc

sudo ./dgtpicom "Hello" 1

Do you have an error?

Randy

[BrianL]

Ok, I tried that using putty.

I didn't get any error. (or any message) just returned command prompt

[Randy Reade]

That's probably because you aren't using the debug build. It will give much more useful info. To test the debug version, carry out the following steps:

Copy the attached file to your home folder (/home/pi). It contains the source code for the 32-bit version of dgtpicom. Then:

unzip dgtpicom.zip

cd dgtpicom

make debug2

Then try the previous test:

sudo dgtpicom "hello" 1

You should see some info now.

Randy

[BrianL]

I've attached the output  from the debug version of dgtpicom. Lots of error but I don't know how to interpret them.

Thanks

[Randy Reade]

Thanks, Brian.

It's definitely a communication problem between the Pi and the clock. I guess running at 500 MHz is too fast in your case. There's an old thread on here where Lucas (from DGT at the time) determined that the RPi4 could run at 500 MHz core frequency and still work with the clock. Perhaps that's not always the case as there may be slight differences between devices.

But I'm not really sure as I don't know the hardware in the clock or why the i2c communication isn't always working. I don't know C programming enough to know where to modify the dgtpicom code. At least not yet. In 64-bit (arm64), there are further issues (related to clock button detection) that I'm trying to figure out but it requires learning C and the i2c interface. It may take me a while. 😁

At least you know how to fix your issue.

Randy

--

You received this message because you are subscribed to a topic in the Google Groups "PicoChess" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/picochess/sHx3t7yF-UU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to picochess+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/a7b0604c-1427-4f24-8433-24538067a13en%40googlegroups.com.

[BrianLoxton]

I'm pretty sure it is just timing, so an easy fix.

Thanks for the help.

To view this discussion on the web visit https://groups.google.com/d/msgid/picochess/CAE5WdutgGErJnEyRbRFXvbhQe2Sr%2BXf90tS_Mt6phxSbdR%3DbCQ%40mail.gmail.com.

[Cordial Iter]

I had the same problem with a DGT 3000 Limited Edition and RPi 3b+. BrianL is right. It is a timing problem. But the values that he used didn’t work for me.

I was successful with deactivating the [Pi4] section and 

core_frequ=300

core_frequ_min=300

The values 250, 400 and 500 didn’t work. 

If you run into the same issue it might be a good idea to experiment with different values.