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

Implement MPSSE subtarget and FTDI emulation mode #49

Closed
whitequark opened this issue May 13, 2018 · 8 comments
Closed

Implement MPSSE subtarget and FTDI emulation mode #49

whitequark opened this issue May 13, 2018 · 8 comments
Labels
firmware Component: software gateware Component: gateware software Component: software

Comments

@whitequark
Copy link
Member

This is kind of annoying because it needs reenumeration logic in the firmware.
@whitequark whitequark added firmware Component: software software Component: software gateware Component: gateware labels May 13, 2018
@whitequark whitequark self-assigned this May 13, 2018
@marcan
Copy link
Member

marcan commented May 1, 2019

Don't forget to emulate the 32-bit EEPROM correctly to avoid being hit by FTDI's bricker :P

@whitequark
Copy link
Member Author

Does anyone actually want this?

@whitequark whitequark removed their assignment Aug 19, 2019
@esden
Copy link
Member

esden commented Aug 20, 2019

MPSSE would be fairly useful. There is a bunch of software that uses MPSSE for "stuff" and it would be nice to just transparently use the Glasgow instead of an FTDI cable. Also that implementation might be a useful reference implementation for FTDI chip replacements.

@classic-gentleman
Copy link

MPSSE would be fairly useful. There is a bunch of software that uses MPSSE for "stuff" and it would be nice to just transparently use the Glasgow instead of an FTDI cable. Also that implementation might be a useful reference implementation for FTDI chip replacements.

YES, for every point made.

@whitequark
Copy link
Member Author

Ironically this was the original goal of the project and the very first committed gateware, but I don't think we even have the code left for it in-tree anymore.

@classic-gentleman
Copy link

https://github.com/usb-tools/Facedancer/blob/master/facedancer/devices/ftdi.py

Adapting this shouldn't be horrible...

@whitequark
Copy link
Member Author

The problem is actually the firmware, and there is no great solution that I know of, especially for Windows.

@whitequark
Copy link
Member Author

We decided not to do this. 60d09a2

@whitequark whitequark closed this as not planned Won't fix, can't repro, duplicate, stale Jul 23, 2023
whitequark added a commit to whitequark/glasgow that referenced this issue Oct 6, 2023
@whitequark
CI: attempt to fix caching, attempt GlasgowEmbedded#49.
2d1386e
whitequark added a commit to whitequark/glasgow that referenced this issue Oct 6, 2023
@whitequark
CI: attempt to fix caching, attempt GlasgowEmbedded#49.
f9390b4
whitequark added a commit to whitequark/glasgow that referenced this issue Oct 6, 2023
@whitequark
CI: attempt to fix caching, attempt GlasgowEmbedded#49.
b5890de
whitequark added a commit to whitequark/glasgow that referenced this issue Oct 6, 2023
@whitequark
CI: attempt to fix caching, attempt GlasgowEmbedded#49.
6269fd3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
firmware Component: software gateware Component: gateware software Component: software
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@esden @whitequark @marcan @classic-gentleman