1. The DigiUSB library is not available in the Arduino IDE. I couldn't find any clones. Is there a way to use the built-in USB port on the board? At least for printing to the monitor at 9600 baud?
I'm most interested in the first method, but if that's not possible, what library can I use to transfer the serial date to the RX and TX pins? I have a TTL-USB converter on a CH340,and I can use it to read and transmit. But I don't understand how on attiny to transfer or read from these pins .
The Attiny85 microcontroller does not have internal serial interface modules. (USART).
Therefore, it cannot use printed output.
You can use a softserial , but I've never used one on the Attiny.
See the difference in the block diagrams of both.
softwareserial is good. What if we take a different approach? Copy the necessary files from GitHub and include them in the project. DigiCDC.cpp DigiCDC.h usbconfig.h
But it's unclear what to do next? Do I need to download any drivers for the virtual com port?
The ATtiny85 has only 8 KB of flash memory. Digispark uses about 2 KB of this for the bootloader. Although it would have been possible to add a communication protocol to the bootloader, it was considered unnecessary given the limited amount of available flash.
I have downloaded and included your library in the IDE 1.8.19 and have opened an example to see the content. I see you have included SoftwareSerial.h also. Will the sketch work if I comment out the SeralSoftware.h file?
In the Arduino UNO R3, the original signal is an asynchronous TTL serial frame. This signal passes through a TTL↔USB converter chip, which converts it into an asynchronous USB-formatted signal so that it is compatible with the USB-A port of PC, since modern PCs no longer have the traditional COM ports. The PC retrieves the oiginal asynchronous TTL signal using a software based USB <----> TTL converter (hence the tag: virual COM Port and the software driver).
In the Digispark ATtiny85 board, the board appears as a USB device rather than a COM device because the original signal is already in USB format.
If one wants to add communication facilities to the bootloader of the Digispark ATtiny85 board, it is technically possible, but it would require considerable effort. Such work is more appropriate for a professional software house.
I refer to digistump but looks like improved version little bit new.
ook I have compiled as digispark default 16.5mhz (as atiny85 micronucleus digispark it foesnt want to compile)
but now I have problem with unknown usb device with ID 0006 .
I have tried zadig libusbk and winusb but instalation failed (ok now instalation was successful but anyway unowkn descriptor of usb)
at this point I have stoped at the moment
The DigiSpark is a cool little board, but unfortunately the USB capabilities can be unreliable. The reason is that the ATtiny85 doesn't have a native hardware USB capability, so this is being faked using the code running on the ATtiny85 in the background of your sketch program.
If you use the USB connection only for uploading sketches and powering the board, I think you will have good results, but anything more may bring significant frustration.
So you might consider going with your "plan B" of using the CH340 module..