GarySnA
-
I'm giving a part 5/5 of an @ webinar series on System Level Testing and Debug today at 2:00 PM Eastern.
8:45 AM Mar 23rd
via web
-
10.3.9 Design each block with its own abort function that services just that block.
8:41 AM Oct 6th, 2011
via web
-
5.8.4 Document the conditions and states that affect the variations of minimum, maximum, and typical times for each operation.
6:14 AM Sep 21st, 2011
via web
-
3.3.5 Firmware: Work with the hardware engineer to find solutions to hardware/firmware interaction problems when they are discovered.
11:02 AM Sep 19th, 2011
via web
-
11.1.3 Collaborate with firmware engineers on the design of test and debug hooks.
7:01 AM Sep 16th, 2011
via web
-
3.2.5 Make sure that the firmware team is represented in reviews and signoffs of hardware checkpoints throughout the life cycle.
12:04 PM Sep 14th, 2011
via web
-
4.5.4 Evaluate prior history, the existence of device drivers, and strong technical support when purchasing IP from a third-party.
6:51 AM Sep 12th, 2011
via web
-
5.6.1 Display the register map in a horizontal format in the block's documentation.
8:28 AM Sep 7th, 2011
via web
-
7.2.2 Provide data buffering, queuing, and chaining to maximize data throughput.
9:07 AM Sep 6th, 2011
via web
-
4.6.1 Review the postmortem notes from the previous chip and apply appropriate changes to fix defects and add design enhancements.
8:02 AM Sep 2nd, 2011
via web
-
5.7.4 Assign the name, "Enable," to the register that controls which interrupts will propagate.
8:55 AM Aug 31st, 2011
via web
-
11.2.4 Make counter and address registers readable even if they change rapidly.
9:23 AM Aug 29th, 2011
via web
-
3.2.4 Make sure that the firmware team is represented in the chip design, the detailed block designs, and the testing plans.
8:57 AM Aug 24th, 2011
via web
-
5.5.5 Document all interactions between registers.
7:25 AM Aug 22nd, 2011
via web
-
8.2.10 Avoid reusing bit positions of deleted bits in an existing register.
9:16 AM Aug 19th, 2011
via web
-
5.4.9 Include a list of other documents to reference that may provide useful or necessary information for this block.
10:56 AM Aug 18th, 2011
via web
-
9.6.3 Do not use an interrupt to indicate completion of firmware-launched hardware tasks that always complete instantaneously.
8:29 AM Aug 12th, 2011
via web
-
3.2.6 Use co-development activities, such as virtual prototypes, FPGAs, co-simulation, and old hardware.
12:21 PM Aug 10th, 2011
via web
-
4.5.2 Analyze each I/O block to ensure that it provides the proper buffer support for status, control, interrupts, errors, and debug.
10:11 AM Aug 8th, 2011
via web
-
8.2.9 Avoid changing bit assignments from one version of the block to the next.
9:44 AM Aug 5th, 2011
via web
|
- Name Gary Stringham Assoc
- Location Boise, Idaho
- Web http://garystring...
- Bio Embedded systems consultant specializing in the hardware/firmware interface.
|