General Category > Discussion - EVE

UMFT4222EV with VM816C50A

(1/2) > >>

fluidcontrol:
Hello everyone,

Has anyone tried to use the UMFT4222EV - FT4222H Development Module (of course with a 10K pull-up resistor on SS pin) to communicate over QSPI/SPI with an BT81X board (ex.: VM816C50A) from EVE Screen Designer?

Thank you

fluidcontrol:
I've tested it myself and it works.
VM816C50A + UMFT4222EV = VM816CU50A

kumaichi:
Hello, I was wondering if you could share your wiring connections.  I'm struggling to get the UMFT4222EV to connect to a Riverdi BT817Q.  My connections are as follows:

UMFT4222EV     ->     BT817Q
JP5.9                ->     SCLK
JP5.8                ->     MISO
JP5.7                ->     MOSI
JP5.5                ->     IO.2
JP5.4                ->     IO.3

JP4.11              ->     -----     10k Resistor -> +3V3
JP4.9                ->     CS        4.7k Resistor -> +3V3
JP4.6                ->     INT
JP4.4                ->     RST/PD

When in EAB and I try to Detect, I mostly get the following:

Detecting flash...
Found device: FT4222 A (A)
Host: FT4222

Flash size: 64 MBytes

Blob is NOT present.

Flash can switch to full speed.
END

Detection fail!

Occasionally, I get this:

Detecting flash...
Found device: FT4222 A (A)
Host: FT4222

Flash size: 64 MBytes

Blob is NOT present.

Flash can switch to full speed.
END

BEGIN
Measure reading speed...

Reading speed: 17.88 MB/s
Reading 10 MBytes in 0.56 seconds
END

In either case, it never finds the blob.  I know the blob is present because I can program it perfectly fine with an FT232H.

Is something connected incorrectly?  I've been trying to use the ME817EV schematic to try and match things up, which I think I have (using the pin mapping above).

Any insight would be greatly appreciated.

Kindest regards.

BRT Community:
Hello,


--- Quote from: kumaichi on February 03, 2024, 02:57:57 AM ---Hello, I was wondering if you could share your wiring connections.  I'm struggling to get the UMFT4222EV to connect to a Riverdi BT817Q.  My connections are as follows:

UMFT4222EV     ->     BT817Q
JP5.9                ->     SCLK
JP5.8                ->     MISO
JP5.7                ->     MOSI
JP5.5                ->     IO.2
JP5.4                ->     IO.3

JP4.11              ->     -----     10k Resistor -> +3V3
JP4.9                ->     CS        4.7k Resistor -> +3V3
JP4.6                ->     INT
JP4.4                ->     RST/PD

When in EAB and I try to Detect, I mostly get the following:

Detecting flash...
Found device: FT4222 A (A)
Host: FT4222

Flash size: 64 MBytes

Blob is NOT present.

Flash can switch to full speed.
END

Detection fail!

Occasionally, I get this:

Detecting flash...
Found device: FT4222 A (A)
Host: FT4222

Flash size: 64 MBytes

Blob is NOT present.

Flash can switch to full speed.
END

BEGIN
Measure reading speed...

Reading speed: 17.88 MB/s
Reading 10 MBytes in 0.56 seconds
END

In either case, it never finds the blob.  I know the blob is present because I can program it perfectly fine with an FT232H.

Is something connected incorrectly?  I've been trying to use the ME817EV schematic to try and match things up, which I think I have (using the pin mapping above).

Any insight would be greatly appreciated.

Kindest regards.

--- End quote ---

Your ping assignments look correct for the connection from the FT4222 to the BT817.

EVE Asset Builder reporting on occasion that it can detect the flash indicates that your connections are correct but there may be a signal integrity issue.
Are you using long jumper wires to connect your FT4222 to the BT817 board?

Best Regards,
BRT Community

kumaichi:
The jumpers I'm using are the breadboard wires, maybe 10-12in long.  I'll try the short ones and see if that makes a difference.  Thanks for the response.

Shortest breadboard wires I have still produce the same results.

I also tried changing the clock speed from 1-20 in steps of 1 and it didn't yield any different results, still fails to detect most of the time, never recognizes the blob.  I also tried to erase the chip and updated, it will sometimes say it's successful but running detect again shows same result, never detecting the blob and failing to detect.

Kindest regards

Navigation

[0] Message Index

[#] Next page

Go to full version