tinyvision-ai-inc / tinyclunx33_public

Documentation for the tinyNX33U SoM and related boards

tinyCLUNX33

Sources and documentation for the tinyCLUNX33 SoM and related boards.

tinyclunx33_public's Issues

[doc] Get the boards Rev2/Rev3 naming clear

~13 Rev2 -> Rev1 (SoftEye) + some around
~16 Rev3 -> Rev2

Enable more LiteX peripherals (GPIO, PWM)

GPIO needed for "enable" signals, i.e. camera module

[doc] document each adapter

Currently, the adapters are only present on the Hardware directory of the repo. Maybe it is interesting to have them listed on the doc website...

Eventually this would require to decide on what is publicly visible and what considered "internal intermediate state", only given to one client or two.

AP2120 is now marked inactive

The datasheet became a deadlink, and now we have this https://www.diodes.com/assets/Datasheets/products_inactive_data/AP2120.pdf

The link is products_inactive_data.

That does not look like a part difficult to source or extremely demanding in specs though...

ATtiny roles in Rev3

Here is a discussion to start anticipating the role an ATtiny could have on such a module, for inclusion in Rev3 instead of the GPIO expander.

[doc] update the schematic links

Some of the schematics need to be updated, currently a 404.

[doc] connectors and pinout

Currently, locating the connectors on the devboard is a bit challenging to figure out.
A photo with an overlay drawing could help, or something like this:
https://pico-ice.tinyvision.ai/md_pinout.html

[doc] Add a mention to `pyelftools`

This seems to be required but not present on the doc for Ubuntu.

[doc] update the quickstart instructions

The quickstart section is out of date. This require users to go bug us to get started and is not pleasant.
https://tinyclunx33.tinyvision.ai/md_carrier_devkit.html#autotoc_md1

Furthermore, there are no general instructions for how to plug things together, and what to connect, and what to expect, where to get the debug logs.

Things that are obvious after being introduced to it, and a short summary can help confirming what is expected.

I.e.:

• there are two /dev/ttyUSB# interfaces, but only one of them (usually the second) is containing logs
• there are two USB interfaces, and the shell will usually be visible on the FTDI "DEBUG" interface, unless it is configured over USB, in which case it will be in the USB3 "DATA" interface. The logs are usually configured to be over the FTDI "DEBUG" interface
• non-standard baud rate in some revisions
• The connector labels are in-between the connectors, ambiguous between whether they are for the left or right connector.

[doc] document the use of Zadig for Windows, and sudo for Linux

The open-source command line tools used to debug the tinyCLUNX33 such as ecpprog were developped under Linux as part of the Yosys community.

This means they use libusb to implement the FTDI driver in user-space, rather than using the FTDI-provided driver (absent on Linux). One Windows, like for many command line utilities developped for Linux/MacOS first, this means that it is required to switch the driver used using tools like Zadig, so that instead of using the FTDI driver, they get a generic driver assigned allowing to communicate with the device directly.

Also, on Linux, in order to be able to read logs from the /dev/ttyUSB1 device, it is required to:

• Add the user to the dialout (I think?) group
• Log-off log-in to apply the group (or reboot)

And to be able to use ecpprog command:

• the user might need to be in the plugdev group
• log-off log-in to apply the group (or reboot)
• have udev rules setup for the FTDI
• reload these udev rules

An alternative to bypass all of this setup is to run the command with sudo

And bit of background about how this can be done in a VM or WSL would also be appreciated: links for how to access a local USB device into WSL or in a VM, even if it is not tested.

This would need to be mentioned on this page maybe:
https://tinyclunx33.tinyvision.ai/md_som_flash.html

Unless there is a better place where to document it...