-
According to the documentation ```scope.userio.drive_data``` on the Husky should return an integer describing how the userio is currently driven. Instead it always returns 0.
# Steps to Reproduce…
-
We have fresh-out-of-the-box CW340 card that appears to be non-functional and require some assistance with debugging.
Once connected to the host computer, we can successfully run the OpenTitan [set…
-
Latest firmware (1.3.0) seems to have broken I2C:
```python
>>> target = cw.target(None, cw.targets.CW310)
Traceback (most recent call last):
File "", line 1, in
File "/home/jw/projects/ch…
-
>Traceback (most recent call last):
> File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python39_64\lib\runpy.py", line 197, in _run_module_as_main
> return _run_code(code, main_global…
-
I have the target board for the N76E003 (and other NuMicro 1T 8051 chips) ready to be PRed here:
https://github.com/nikitalita/n76e003-ufo-target-board
However, the board is made in KiCad, and I n…
-
https://forum.newae.com/t/chipwhisperer-nano-glitch-issue/3485/4
-
### Hierarchy of regression failure
Chip Level
### Failure Description
There appears to be a flakiness issue with some tests that make use of UART communication between the host and device (e…
-
### Description
We've had a few problems with the SAM3x on the CW310 FPGA boards recently.
* @pamaury observed that `0xff` bytes were being added to UART traffic between the SAM3x and OpenTitan …
jwnrt updated
7 months ago
-
### Context
We'd like to be able to save the project-related data we obtain so it can be combined by us and by others with the parent data of the NLnet projects. NLnet uses RDF data formats for the …
-
After the latest changes in capture setups, we are experiencing problems when capturing using ChipWhisperer Husky.
Currently, I am not sure what is causing the problem, but these are the symptoms:
…