Thanks Jack!
Sorry for the delay, I have been busy with other projects for a while.
In fact we sorted out the problem which was because of another totally
unrelated bug, so the GPIO approach worked from the start.
So, for the record, to get previously undefined GPIO pins working you should
- add them in mlib_devel/jasper_library/<platform>.yaml with a
convenient label.
- add the label to the gpio.slx mask
- run xps_build_new_library in matlab prompt
- load your (old) design and run update_casper_blocks(bdroot)
We did not yet try the custom group, that would of course be more
convenient... But it seems surprisingly simple in any case.
Here are the pmod header definitions for zcu111.yaml:
pmod:
drive_strength: 8
iostd: LVCMOS12
loc:
- C17
- M18
- H16
- H17
- J16
- K16
- H15
- J15
- L14
- L15
- M13
- N13
- M15
- N15
- M14
- N14
Thanks,
Kaj
On 19.3.2024 21.29, Jack Hickish wrote:
On Mon, 11 Mar 2024 at 08:47, Kaj Wiik <kaj.w...@iki.fi
<mailto:kaj.w...@iki.fi>> wrote:
Hi all,
Somewhat related to the previous question: how to define and use
(RFSoC) pins as GPIOs via the gpio block?
I noticed that group 'led' is in both gpio block mask and in .yaml
but e.g. there is 'pmod' group in rfsoc4x2.yaml but it is not seen
in the gpio mask parameters. Can that group be used e.g. via the
'custom' group?
What is the process of adding pins to the gpio block other than just
adding them into the .yaml file?
Should I define a new group e.g. pmod and add that to the mask,
would that be enough?
Thanks,
Kaj
Hi Kaj,
As you infer, you can use the "custom" group and then just type what you
want in the mask dialog -- e.g. 'pmod' (I wouldn't like to say if the
quotes are required or forbidden....)
With this mechanism, you can use any pin group present in the YAML file
without modifying the GPIO mask.
Otherwise, you can modify the mask to add the groups as you describe.
The annoyance then becomes choosing between having a bunch of groups in
the dropdown which are only supported if the platform YAML has included
them, or, adding a bunch of callback code so only the supported groups
are displayed based on your chosen platform.
My vote: "custom" :)
Cheers
Jack
--
You received this message because you are subscribed to the Google
Groups "casper@lists.berkeley.edu
<mailto:casper@lists.berkeley.edu>" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to casper+unsubscr...@lists.berkeley.edu
<mailto:casper+unsubscr...@lists.berkeley.edu>.
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADpJ3s2srCtQK5JJyTkVqk7_-KzR2T%3DzkG8jU8DDOUMXLTZDnA%40mail.gmail.com
<https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADpJ3s2srCtQK5JJyTkVqk7_-KzR2T%3DzkG8jU8DDOUMXLTZDnA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to casper+unsubscr...@lists.berkeley.edu
<mailto:casper+unsubscr...@lists.berkeley.edu>.
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKSn8GoRn4Ve5GtoqhS5WyY6j_4Y9EKWBAQpb1_YZZdi%2BQw%40mail.gmail.com <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKSn8GoRn4Ve5GtoqhS5WyY6j_4Y9EKWBAQpb1_YZZdi%2BQw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6bb23ecc-0d7c-4848-ba77-c80bb3319339%40utu.fi.
