pulsing.wordpress.com
December | 2009 | Program pulses for fun
https://pulsing.wordpress.com/2009/12
Program pulses for fun. Archive for December, 2009. Just a song before we go on winter break. 14 December, 2009. Posted by Paul Pham. Some of you probably don’t celebrate Xmas, but you probably eat cookies. And cookies, like pulse programming, have universal appeal, almost hardwired into the human psyche. The evidence? Behold, Exhibit A:. Who toured Seattle in May. Okay, project updates! I mailed these off to Screaming Circuits. Generously gave an introductory lecture on quantum computing this past Frida...
pulsing.wordpress.com
March | 2010 | Program pulses for fun
https://pulsing.wordpress.com/2010/03
Program pulses for fun. Archive for March, 2010. Firmware Release v0.33. 11 March, 2010. About a week ago, the latest version of the firmware was released. An overview of the main changes can be found in the release notes here. Included in the release was support for the branch-on-trigger and branch-wait features discussed in John’s post. Additionally, some of the DHCP work done by Jeff was included. The signal for writing data for the icnt write instruction was unnecessarily delayed, which was fixed.
pulsing.wordpress.com
leading up to squint | Program pulses for fun
https://pulsing.wordpress.com/2010/02/13/leading-up-to-squint
Program pulses for fun. Laquo; Wait-Trigger and Branch Trigger Level Detection. Networking the Sequencer Board. Leading up to squint. 13 February, 2010. Posted by Paul Pham. Converting addresses between 32-bit (use by PCP) and 8-bit (used by PTP), and clocking issues (synchronizing between triggers and the system clock). The other members of our team have also been busy in the meantime. Jeff is finishing up new support for network device discovery. No more hard-coded IP addresses or dedicated routers!
pulsing.wordpress.com
Networking the Sequencer Board | Program pulses for fun
https://pulsing.wordpress.com/2010/02/24/networking-the-sequencer-board
Program pulses for fun. Laquo; leading up to squint. Firmware Release v0.33. Networking the Sequencer Board. 24 February, 2010. API Change to Support Multiple Devices. This change applies to the Python software in the “pulse-sequencer” SVN repository. DHCPDISCOVER – the sequencer board sends a broadcast message asking for an IP address. DHCPOFFER – the DHCP servers on the network offer IP addresses to the sequencer board. ACK messages back — to indicate failure. When a network device like the sequencer b...
pulsing.wordpress.com
Firmware Release v0.33 | Program pulses for fun
https://pulsing.wordpress.com/2010/03/11/firmware-release-v0-33
Program pulses for fun. Laquo; Networking the Sequencer Board. Firmware Release v0.33. 11 March, 2010. About a week ago, the latest version of the firmware was released. An overview of the main changes can be found in the release notes here. Included in the release was support for the branch-on-trigger and branch-wait features discussed in John’s post. Additionally, some of the DHCP work done by Jeff was included. The data output from the processor wasn’t hooked up to the SRAM controller, so data f...
pulsing.wordpress.com
solothing | Program pulses for fun
https://pulsing.wordpress.com/author/solothing
Program pulses for fun. Networking the Sequencer Board. 24 February, 2010. API Change to Support Multiple Devices. This change applies to the Python software in the “pulse-sequencer” SVN repository. In the past, the networking API for the test configuration (/pulse-sequencer/software/python/test-config.py) did not support addressing multiple devices. Device discovery was already implemented in the discover devices() method defined in /pulse-sequencer/software/python/sequencer/ptp/ init .py . When a netwo...
pulsing.wordpress.com
February | 2010 | Program pulses for fun
https://pulsing.wordpress.com/2010/02
Program pulses for fun. Archive for February, 2010. Networking the Sequencer Board. 24 February, 2010. API Change to Support Multiple Devices. This change applies to the Python software in the “pulse-sequencer” SVN repository. DHCPDISCOVER – the sequencer board sends a broadcast message asking for an IP address. DHCPOFFER – the DHCP servers on the network offer IP addresses to the sequencer board. DHCPREQUEST – the sequencer board contacts a specific DHCP server to confirm its offer. When a network devic...
pulsing.wordpress.com
rmcclur | Program pulses for fun
https://pulsing.wordpress.com/author/rmcclur
Program pulses for fun. Firmware Release v0.33. 11 March, 2010. About a week ago, the latest version of the firmware was released. An overview of the main changes can be found in the release notes here. Included in the release was support for the branch-on-trigger and branch-wait features discussed in John’s post. Additionally, some of the DHCP work done by Jeff was included. The signal for branching based on a comparison between a counter register and another value had some delay issues, which were fixed.
pulsing.wordpress.com
Program pulses for fun | Page 2
https://pulsing.wordpress.com/page/2
Program pulses for fun. 18 January, 2010. Posted by Jeff Booth. For the clock source, Paul bought an ADF-4360-2 chip on an EB1 Rev. D3 evaluation board. This board has a connector for a 9V battery; since the battery died, we connected it to a 12V power source (since the on-board voltage regulator can handle it). It has a clock output labeled “RF” and a DB9 female connector for communications. The pin mappings are:. 3 CLK – Clock. 7 LE – Latch Enable. 8 GND – Ground. R: 0000 0000 0000 0000 1100 1001.
pulsing.wordpress.com
johnwwil | Program pulses for fun
https://pulsing.wordpress.com/author/johnwwil
Program pulses for fun. Wait-Trigger and Branch Trigger Level Detection. 5 February, 2010. Posted by John Williams. This post covers the addition of two requested features to the Python v1 Compiler and the underlying pcp32 firmware. Python API Call: branch(label, triggers, level = 1). PCP32 Instruction: btr [triggers] [level] [address]. Python API Call: branch wait(label, triggers, level = 1). One feature that has been requested is the ability to select the level to trigger when using a branch event.
