Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Force HyperSerial detection #732

Merged
merged 4 commits into from
Jan 18, 2024
Merged

Force HyperSerial detection #732

merged 4 commits into from
Jan 18, 2024

Conversation

awawa-dev
Copy link
Owner

@awawa-dev awawa-dev commented Jan 15, 2024 •
edited
Loading

Ignore ProductId/VendorId of the serial port device and force initialization HyperSerial driver. Thanks @alex-013

obraz

@awawa-dev
Copy link
Owner Author

Hi @AstaRom
Do you think you would be able to update the translation with the new item: edt_dev_spec_forceSerialDetection? Thank you in advance.

@AstaRom
Copy link
Contributor

AstaRom commented Jan 16, 2024

Good evening, yes I can.
I can do it tomorrow.
Should changes be submitted to the "force_hyperserial" branch?

@awawa-dev
Copy link
Owner Author

Great 👍 Yes, 'force_hyperserial' branch. It has already been merged with the latest translation resource changes introduced in '20rc1' branch.

@AstaRom
Copy link
Contributor

AstaRom commented Jan 17, 2024

Do you think you would be able to update the translation

Done.

@awawa-dev awawa-dev merged commit cd082dd into v20rc1 Jan 18, 2024
1 check passed
awawa-dev added a commit that referenced this pull request Jan 25, 2024
@awawa-dev @AstaRom @alex-013
Update resource, force HyperSerial detection (#723)
d04527b 
* Update translations by @AstaRom

* update license

* Disable cache before release build

* Update language file's (#716)

* Force HyperSerial detection (#732)

* Add ttyACM detection

* Fix

* Update language file's (#736)

---------

Co-authored-by: Aleksandar Jovanovic <aleksandar.jovanovic@ricardo.ch>
Co-authored-by: Roman Astafev <39379875+AstaRom@users.noreply.github.com>

* Update CHANGELOG.md

* Fix verbose option

* Update

* Update language file's (#747)

---------

Co-authored-by: Roman Astafev <astafev.roman.mail@gmail.com>
Co-authored-by: Roman Astafev <39379875+AstaRom@users.noreply.github.com>
Co-authored-by: Aleksandar Jovanovic <aleksandar.jovanovic@ricardo.ch>
@awawa-dev awawa-dev deleted the force_hyperserial branch February 7, 2024 12:59
@Bascht74
Copy link

Could you add a hint what this feature is for?
Can I set the output path to auto and hyperHDR will look for it?

@awawa-dev
Copy link
Owner Author

On some systems (mainly due to a udev bug), the system does not report the correct ProductId and VendorId of the Pico board, and HyperHDR could not detect and initialize them correctly. Typically ProductId/VendorId have the value 0, but e.g. in RPi4 they may have the ProductId/VendorId of the USB hub. Correct ProductId/VendorId for Pico is 0xa / 0x2e8a (can be found in the logs).
As it ignores the automatic detection you rather do not want to use it with auto ( it may work if there is only one serial device).

@Bascht74
Copy link

Ok Thx, so if I dont' have any problems with the pi4 I don't need to check it, but it would not hurt?

@awawa-dev
Copy link
Owner Author

It's better to not use this option if it is not necessary (only when the board is not detected) because it disables important check. This is a workaround for a bug in other software (mainly udev).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@awawa-dev @AstaRom @Bascht74 @alex-013