Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: tz <thomas@mich.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] in search of a better microcontroller
Date: Tue, 27 Mar 2012 08:39:50 -0400	[thread overview]
Message-ID: <CAFv7Oih5VzhOPP=XOQvy0_HNa8cbXv6qTTQ119Q3S7DYEwwmgw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6Yvk0pwetde404kfcb7O6q2dcxcg6nNKdDw2FaW=KMtA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2557 bytes --]

While looking for other things, I came across this.

http://www.suntekstore.com/goods-14004282-enc28j60_ethernet_lan_module_for_arduinoavrlpcstm32.html

Ethernet for under $10.  Send a udp packet at pps?
 On Mar 26, 2012 8:53 PM, "Dave Taht" <dave.taht@gmail.com> wrote:

> Since 'plain jane' is coming along nicely, I've been amusing myself with
> what it would take to do 'sexy sadie'
> (not my final choice for a name btw!)
>
> I wanted to combine at least two functions into the usb stick, they would
> be:
>
> * gps/time with supercap backup
> * other sensor support (wind cups, precipitation, barometer, etc)
> * some sort of direct output signal (can bus? spi bus? don't know yet)
> * randomness/entropy generator
>
> While my initial choice for the former two features would be the ublox
> device already discussed, I haven't pursued the possibility of being able
> to modify their firmware to do what I want. I should contact them I
> guess... but I'm wagering that gaining access to that firmware will be
> difficult, so interfacing with a cheaper gps device (e.g plaine jane) and
> adding a microcontroller to it seems like the best option.
>
> The problem is I'd like to find something capable of 480Mbit transfers.
>
> The first microcontroller I picked (the atmel) seems to be near end of
> life and only does 12Mbit, so I went looking for the sexy and new (a lot of
> those!), and stumbled across this one:
>
>
> http://media.freescale.com/phoenix.zhtml?c=196520&p=irol-newsArticle_print&ID=1671968&highlight=
>
> I couldn't help but laugh when I saw:
>
> "Linear 4 GB address space that removes the need for paging, reducing
> software complexity and ensuring a more 8-bit-like user experience"
>
> Yea, that 8 bit-like user experience. That's what I want in a 32 bit 4GB
> capable architecture.
>
> The last phrase was removed from the official site later, after whoever
> wrote the pr release came down off of whatever he/she was smoking.
>
>
> http://www.freescale.com/webapp/sps/site/overview.jsp?code=KINETIS_L_SERIES&tid=van%20LSERIES
>
> This chip is WAY too new to consider using, but it is a sign of things to
> come. Still trying to find a sane 480Mbit USB interface that's under 10
> bucks...
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net
>
> _______________________________________________
> Thumbgps-devel mailing list
> Thumbgps-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/thumbgps-devel
>
>

[-- Attachment #2: Type: text/html, Size: 3608 bytes --]

  reply	other threads:[~2012-03-27 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  0:53 Dave Taht
2012-03-27 12:39 ` tz [this message]
2012-03-27 14:29 ` Patrick Maupin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFv7Oih5VzhOPP=XOQvy0_HNa8cbXv6qTTQ119Q3S7DYEwwmgw@mail.gmail.com' \
    --to=thomas@mich.com \
    --cc=dave.taht@gmail.com \
    --cc=thumbgps-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox