PSAS/ capstone2009/ blogs/ JeremyBooth
  1. Weekly Progress Reports:
    1. WPR June 04
    2. WPR May 28
    3. WPR May 21
    4. WPR May 14
    5. WPR May 07
    6. WPR Apr 30
    7. WPR Apr 23
    8. WPR Apr 16
    9. WPR Apr 09
    10. WPR Apr 02
    11. WPR Mar 26
    12. WPR Mar 12
    13. WPR Mar 05
    14. WPR Feb 26
    15. WPR Feb 19
    16. WPR Feb 13
    17. WPR Feb 06
    18. WPR Jan 30
    19. WPR Jan 22
    20. WPR Jan 16
  2. notes:
    1. My Notes
    2. ADC Notes
  3. codely bits:
    1. ADC flashy asychronous to the ADC output to the serial port
    2. PRESSURE TEST CODE - This is the code that sends ADC info out via the serial port in formatted packed binary. It also includes additions to the freertos serial files that support this nifty binary sending action!
  4. Questions
  5. Meeting notes Mar 06/06

Weekly Progress Reports:

WPR June 04

Last Week:

Next Week:

WPR May 28

Last Week:

Next Week:

WPR May 21

Last Week:

Next Week:

WPR May 14

Last Week:

Next Week:

WPR May 07

Last Week:

Next Week:

WPR Apr 30

Last Week:

Next Week:

WPR Apr 23

Last Week:

Next Week:

WPR Apr 16

Last Week:

Next Week:

WPR Apr 09

Last week:

Next Week:

WPR Apr 02

Last Week:

Next Week:

WPR Mar 26

Last Week:

Next Week:

WPR Mar 12

Last Week

Next Week

Issues:

WPR Mar 05

Last Week

Next Week

WPR Feb 26

Last week

Next week

WPR Feb 19

Last week

Next week

WPR Feb 13

Last week

Next week

WPR Feb 06

Last week

Next week

WPR Jan 30

Last week

Next Week

WPR Jan 22

Last week

Next week

Issues or "A log of failure and resolution":

"psasftdlib.sh -i" in docs should be "psasftdilib.sh -i" (page 5) This is in a PDF, so I will not attempt to change now...

psas_ftdlib.sh -i issues:

sudo busted...

edited sudoers, added main user account (what crappy debian did I install anyhow??? so much seems missing)

./psas_ocd.sh : Non-zero return. Command is: svn checkout -r 1257 svn://svn.berlios.de/openocd/trunk openocd

??Permissions issue?? no...

no svn! - package is apparently called subversion - installed - man svn works...

went further, then: " ./bootstrap: line 2: aclocal: command not found

./psas_ocd.sh : Non-zero return. Command is: ./bootstrap "

aclocal appears to be related to some "automake" thing. - checking for package - installed

script finished //end ./psas_ocd.sh

./psas_lpc21isp.sh having issues now:

" ./psaslpc21isp.sh : Non-zero return. Command is: cp /home/user/lpc-kit/Sources/lpc21isp155.zip . "

//end Issues or "A log of failure and resolution"

//end WPR Jan 22

WPR Jan 16

Last week

Next week

notes:

My Notes

My Notes This page has my notes on Eagle, and will have additional notes...

http://jcwren.com/arm/ (windows zip package ...)

http://jcwren.com/arm/packages/LPC2148_Demo_latest.zip

ADC Notes

All channels appear to be open in the form of ADC[which ACC]_[which channel]

Looks like the pot is wired to ADC0_3

data should be 10 bits wide? this sounds happy... The return claims that it's sending back a cleaned up picture of bits 15:6, aligned to 0 (shifted right 6)

some serial prog info: http://www.faqs.org/docs/Linux-HOWTO/Serial-Programming-HOWTO.html

codely bits:

ADC flashy asychronous to the ADC output to the serial port

main.c.ADC_LED_serial_test

PRESSURE TEST CODE - This is the code that sends ADC info out via the serial port in formatted packed binary. It also includes additions to the freertos serial files that support this nifty binary sending action!

freertos pressuretest.tar

Questions

Where did this LPC helper "toString2()" function come from? Is this just a straight replacement for the "toString()"??

what is this all about: // portTickType xLastWakeTime; // const portTickType xFrequency = 1;

// Initialise the xLastWakeTime variable with the current time.

// xLastWakeTime = xTaskGetTickCount ();

Meeting notes Mar 06/06

*UART to output => header [binary bytes] 1kHz 115 kbps

need to run the UART as tight as possible, sending just a few bytes, and then leave a bit of padding after the burst

packing bits is a possible option, (using 2 bits as one-hots to flag if medium or slow data is present) but we'd be obligated to unpack at client side.

Need to be able to do 1kHz loops / spewing data out the port... Whee!