Searching \ for '[OT] WAY too quiet' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=way+too+quiet
Search entire site for: 'WAY too quiet'.

Exact match. Not showing close matches.
PICList Thread
'[OT] WAY too quiet'
2016\09\27@155904 by Van Horn, David

flavicon
face
Is the server down?  Not much in days.

--
David VanHorn
Lead Hardware Engineer

Backcountry Access, Inc.
2820 Wilderness Pl, Unit H
Boulder, CO  80301 USA
phone: 303-417-1345  x110
email: spam_OUTdavid.vanhornTakeThisOuTspambackcountryaccess.com<.....david.vanhornKILLspamspam@spam@backcountryaccess.com>

-- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
mailman.mit.edu/mailman/listinfo/piclist
.

2016\09\27@160237 by David Strumpf

picon face
Here.  
Sent from AOL Mobile Mail


-----Original Message-----
From: Van Horn, David <david.vanhornspamKILLspambackcountryaccess.com>
To: Microcontroller discussion list - Public. <.....piclistKILLspamspam.....mit.edu>
Sent: Tue, Sep 27, 2016 03:01 PM
Subject: [OT]  WAY too quiet


Is the server down?  Not much in days.

--
David VanHorn
Lead Hardware Engineer

Backcountry Access, Inc.
2820 Wilderness Pl, Unit H
Boulder, CO  80301 USA
phone: 303-417-1345  x110
email: <a href="EraseMEdavid.vanhornspam_OUTspamTakeThisOuTbackcountryaccess.com">david.vanhornspamspam_OUTbackcountryaccess.com</a><<a href="@spam@david.vanhornKILLspamspambackcountryaccess.com?">KILLspamdavid.vanhornKILLspamspambackcountryaccess.com</a>>

-- <a href="http://www.piclist.com/techref/piclist" target="_blank">http://www.piclist.com/techref/piclist</a> PIC/SX FAQ & list archive
View/change your membership options at
<a href="http://mailman.mit.edu/mailman/listinfo/piclist" target="_blank">mailman.mit.edu/mailman/listinfo/piclist</a>
-- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
mailman.mit.edu/mailman/listinfo/piclist
.

2016\09\27@162824 by Dom S

flavicon
face
I didn't see or hear anything ;)

-----Original Message----- From: Van Horn, David
Sent: Tuesday, September 27, 2016 8:59 PM
To: Microcontroller discussion list - Public.
Subject: [OT] WAY too quiet

Is the server down?  Not much in days.

--
David VanHorn
Lead Hardware Engineer

Backcountry Access, Inc.
2820 Wilderness Pl, Unit H
Boulder, CO  80301 USA
phone: 303-417-1345  x110
email: RemoveMEdavid.vanhornTakeThisOuTspambackcountryaccess.com<spamBeGonedavid.vanhornspamBeGonespambackcountryaccess.com>

-- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
-- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
mailman.mit.edu/mailman/listinfo/piclist
.

2016\09\27@173357 by James Cameron

flavicon
face
Sorry, been having too much fun to talk.  ;-)

Here's my brain dump for this morning.  On reply, please change topic
tag!

Experimenting with rapid prototyping, to reduce or remove the edit
compile reflash test cycle.  Using, in essence, telnet and ftp over
encrypted WiFi to ESP8266.  Use telnet with a log to write code on the
target, in circuit.  Use an editor on the host to capture the usable
parts.  Drag and drop.  Use ftp to send debugged and tested code to
the target SPI Flash for loading on restart.

I'd eventually like to integrate the whole into emacs, with a target
console window, and using emacs built-in FTP support.  For fun.

Some way to go.  But so far ... at 160 MHz overclocked, I'm able to
toggle GPIO pins at 18 microseconds per Forth DO-LOOP.  If my
calculations are correct that's 55 kHz.  Higher rates would need C and
reflashing.

Test code (use monospaced font);

\ abbreviation for the pin number
3 constant gpio0

\ enable as output without pull-up
nopull gpio-output gpio0 gpio-mode

\ measure the time taken for ten thousand loops of toggling pin
: x
  get-ticks            ( us )          \ get clock time at start
  #10000 0 do
    1 gpio0 gpio-pin!                  \ raise pin output
    0 gpio0 gpio-pin!                  \ lower pin output
 loop                  ( us )
 get-ticks             ( us new-us )   \ get clock time at end
 swap - .d             ( )             \ subtract and print
;

Running it a few times;

180950 180881 180881 180882 180881 180881 180881 180882 180887 180888
180882 180881 180881 180882

Observed;

- first run usually largest, probably due to the code running in IROM
 space which is cached SPI Flash, so required pages have to be
 paged in, (have previously scoped SPI Flash to verify),

- some variance due to concurrent wireless interrupt load.

-- James Cameron
http://quozl.netrek.org/
-- http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
mailman.mit.edu/mailman/listinfo/piclist
.

2016\09\27@185908 by 99guspuppet

flavicon
face

James
Your experiments with rapid prototyping and ForthLang are way too cool ……
Gus in Denver


On 2016m09d27, at 15:33 MDT, James Cameron <TakeThisOuTquozlEraseMEspamspam_OUTlaptop.org> wrote:

Sorry, been having too much fun to talk.  ;-)

Here's my brain dump for this morning.  On reply, please change topic
tag!

Experimenting with rapid prototyping, to reduce or remove the edit
compile reflash test cycle.  Using, in essence, telnet and ftp over
encrypted WiFi to ESP8266.  Use telnet with a log to write code on the
target, in circuit.  Use an editor on the host to capture the usable
parts.  Drag and drop.  Use ftp to send debugged and tested code to
the target SPI Flash for loading on restart.

I'd eventually like to integrate the whole into emacs, with a target
console window, and using emacs built-in FTP support.  For fun.

Some way to go.  But so far ... at 160 MHz overclocked, I'm able to
toggle GPIO pins at 18 microseconds per Forth DO-LOOP.  If my
calculations are correct that's 55 kHz.  Higher rates would need C and
reflashing.

Test code (use monospaced font);

\ abbreviation for the pin number
3 constant gpio0

\ enable as output without pull-up
nopull gpio-output gpio0 gpio-mode

\ measure the time taken for ten thousand loops of toggling pin
: x
 get-ticks            ( us )          \ get clock time at start
 #10000 0 do
   1 gpio0 gpio-pin!                  \ raise pin output
   0 gpio0 gpio-pin!                  \ lower pin output
loop                  ( us )
get-ticks             ( us new-us )   \ get clock time at end
swap - .d             ( )             \ subtract and print
;

Running it a few times;

180950 180881 180881 180882 180881 180881 180881 180882 180887 180888
180882 180881 180881 180882

Observed;

- first run usually largest, probably due to the code running in IROM
space which is cached SPI Flash, so required pages have to be
paged in, (have previously scoped SPI Flash to verify),

- some variance due to concurrent wireless interrupt load.

--
James Cameron
http://quozl.netrek.org/
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist


--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
mailman.mit.edu/mailman/listinfo/piclist

2016\09\28@100007 by Harrison Cooper

flavicon
face
I've noticed the amount of traffic has gone way down over the past several years.  It used to be I had to skim over everything once a week just to keep up.    I will admit I have been doing less with PIC's in the last year or so as well.

{Original Message removed}

More... (looser matching)
- Last day of these posts
- In 2016 , 2017 only
- Today
- New search...