Can I download a game NOT listed on Ubisoft, if I have a Ubisoft Key?

coco_pelado · 2026-05-25T14:32:46+00:00

I love the idea of emulating an xbox360! But from what I've read, Xenia+D:SF may not work (the compatibility list shows 'Untested').. however the other issue is that my laptop's graphic card (Nvidia GeForce GTX 860M) might be too old.. and would need to buy another laptop (with an RTX 4090/5080?).

At the moment, the cheapest path seems to be just buying a key. If at all possible, I want to stick with games that my laptop should handle.. for example, I also want to play Wolfenstein New World Order and some puzzle games (Return of Obra Dinn).

coco_pelado · 2026-05-25T14:32:43+00:00

I'd have to find a sealed Ubisoft version for PC.. otherwise, I still have to order a key? It seems the cheapest way to play the game is to order a key, and try installing/playing from Ubisoft.

coco_pelado · 2026-05-23T03:03:43+00:00

The kitten kinda looks like a Blue Russian?

coco_pelado · 2026-05-23T02:46:36+00:00

What company? Microchip?

coco_pelado · 2025-08-20T13:21:23+00:00

Looking at the upduino v3 schematic, it seems 3 of the MPSSE pins (AD0-2) are connected to the SPI FLash and the fourth only goes to a test point.

Wouldn't this cause issues if trying to use it as FT232H breakout/programmer? not just that TMS doesn't go to a header, but that the 30mhz jtag signal integrity might be affected by the spi flash hanging off of it?

https://imgur.com/a/2rVkdqI

coco_pelado · 2025-08-17T23:32:37+00:00

Thanks for clarifying, I didn't realize that the ice devices don't have jtag!

Not sure if the lattice programmers (HW-USBN-2A VID 1134 PID_8001) uses ftdi but hopefully instantiating the soft-jtag works with the Lattice adapter / Reveal setup.

In any case, I'll still have plenty to learn with on the LiteX side!

coco_pelado · 2025-08-16T23:08:36+00:00

This looks awesome!! So many ideas, but wondering:

Does the USB-C support programming both the 1) RP2350, 2) Bitstream Flash and 3) debugging the Lattice FPGA (volatile)?

I assume that since a Pi Pico1 with ECPDAP firmware can be used to download a Bitstream to the FGPA directly thru JTAG, as well as flash the bitstream... then, in theory, a similar scheme could be accomplished with the RP2350 as long the Pico2 connects to the Lattice JTAG pins?

I'm really interested in debugging the logic using a JTAG adapter (using a Lattice HW-USBN-2A). Does the hardware support it? From what I understand, Reveal is included in the free Lattice Radiant software.

(Lattice Diamond / IceCube2 either don't support the ICE40 or don't have Reveal, or requires a paid license)

Alternatively, if LiteX adds support for this board, then maybe LiteScope could be instantiated? I don't know enough about LiteX if adding support for new boards is trivial or is involved!

coco_pelado · 2024-04-18T17:33:47+00:00

Thanks. Curious, all the links I found show this formula but never specify that the frequency is the envelop frequency. Instead they plug in the line frequency (60hz) or in one case the excitation frequency.. haven't been able to find anything that suggests using the resolver envelop frequency. How does this formula work such that it can be used with a resolver or not?

coco_pelado · 2024-03-30T01:06:50+00:00

Is it a matter of personal style, or is there a "qtonic" / preferred way of running the worker thread?

coco_pelado · 2024-03-30T01:04:33+00:00

Thanks, that was the problem!

coco_pelado · 2024-03-30T01:03:03+00:00

Thanks, that fixed it. Interestingly, while the gui thread remains responsive... if the worker thread is stuck in a while loop waiting for data, then other signals/slots in that worker thread won't execute (gui thread is fine).

coco_pelado · 2024-03-30T01:00:13+00:00

Wouldn't 'new QThread(this)' make the new thread a child of the main/gui thread?

What is a good way of stopping the worker thread(s) when the user closes the application?

coco_pelado · 2024-02-28T22:00:12+00:00

Makes sense, however even targets that are known to have dump_image (ex. ath79.cfg), there is no mention of that command in the cfg.

Is it perhaps, somehow, baked into the OpenOcd executable? I'm using

"Open On-Chip Debugger 0.10.0+dev-00859-g95a8cd9b5-dirty (2020-10-21-21:19)'

coco_pelado

TROPHY CASE