Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
C
Conv TTL Blocking
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
5
Issues
5
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
Conv TTL Blocking
Commits
c5561f06
Commit
c5561f06
authored
Nov 01, 2013
by
Javier Serrano
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
First comments after reading HDL guide
parent
3fa1e9c0
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
26 additions
and
0 deletions
+26
-0
javier.txt
design-review/javier.txt
+26
-0
No files found.
design-review/javier.txt
0 → 100644
View file @
c5561f06
Some comments after reading the "CONV-TTL-BLO HDL Guide" pdf document:
======================================================================
Page ii: "Intergrated" -> "Integrated" I don't know if vim has a spell
checker. Emacs does ;) Also, VBCP should be defined here.
Page 1: some text labels in figure 1 cannot be seen completely.
Page 4: Not clear what "LED refresh rate" means. Some kind of duty
cycle? "the to the LEDs" -> "then to the LEDs".
Page 5: "Setting" column in table is empty. Fill or delete.
Page 6: what are the units for the length of the glitch filter? clk_i
cycles? A maximum g_pwidth should also be imposed to preserve the
transformer. "The behavior of the outputs are different" -> "The
behavior of the outputs is different"
Todo
====
- Check DAC output for OSC1 has a stable voltage.
- Check that the duty cycle of 1/5 max is also imposed when the glitch
filter is active.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment