Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by kenemon

  1. Awesome application Blue. I was wondering why someone had not made this, after getting myself an xprotolab. I think the larger footprint, and use of the MSP will make this baby allot easier to work with, and make the enclosure a more manageable project.

    With four channels
    , have you considered a logic probe function? Any plans for a GUI?



    edit: sorry I was confusing this for a moment with Rob's Nokia project :oops:

  2. Thanks Rick,


    What I am actually trying to do is get a MCU to communicate with a WiFi module in an attempt to broadcast the data over 802.11. The module I picked, and it may be a mistake, uses a SDIO connection to the host. It also has I2C and SBW connections, but they share pins with other ports. Your post did point me to an interesting fact that SDIO cards can be accessed using SPI, and this may be the ticket . Most of my efforts are focused on "dumbing down" technology to make it more affordable and specific to some simple sensor/control concepts that would be benefited by wireless nets. KB


    Reading this I am a little hurt to call the MSP a "cheap" MCU, I will admit it is inexpensive ;)



    from: http://elm-chan.org/docs/mmc/mmc_e.html

    SPI Mode


    This document describes the protocol to control MMC/SDCs in SPI mode. The SPI mode is an alternative operating mode that defined to use the MMC/SDCs without native host interface. The communication protocol for the SPI mode is simple compared to its native operating mode. The MMC/SDC can be attached to the most microcontrollers via a generic SPI interface or GPIO ports. Therefore the SPI mode is suitable for low cost embedded applications. Especialy, there is no reason to attempt to use native mode with a cheap microcontroller that has no native host interface. For the SDC, the SPI mode 0 is defined for its SPI mode. For the MMC, it is not the SPI timing, both latch and shift actions are defined with rising edge of the SCLK, but it seems work in SPI mode 0 in SPI mode. Thus the SPI Mode 0 (CPHA=0, CPOL=0) is the proper setting for MMC/SDC interface, but SPI mode 3 also works as well in most case.

  3. Hi Zeke, thanks for the continued attention.


    Please check this out:




    I think I included everything you mentioned. It is hard to see the vias on the image, but they are plated. This has caused me a little confusion. I assume "plating" the vias will connect the two ground planes. As an example, the 4 pads in the top ground plane. They are specified as "exposed copper", and i take that to mean a pad with no plating. The other pads for the module I imagine are "plated" meaning they will be soldered on?? Why would the ground plane pads not be plated?


    Thanks. KB


    it will ultimately do something like this:



  4. Thanks Zeke,


    If I understand correctly:


    I should add a copper pour on top underneath the module, bottom has one already (in blue), or do you mean the whole bottom?

    I should add more vias there


    Im not sure if I understand

    If you ground the H. E. double hockey sticks out of the board then it will work well

    I had trouble making that contact detail work like the drawing, so I improvised with those 4 pads that fan out to the proximal vias,


    I was under the impression the power planes were for heat sinks, much like the HT case IC's


    Thanks again for such a quick reply. KB


    p.s. I have improved it as you suggested, but i cannot upload for some reason, i will try later.

  5. Hi All, can anyone explain what SDIO is to me. I am interested in using this for attaching a peripheral to the MSP430, and am not finding anything in this regard. Is this possible? Wiki is not doing it for me, technically.


    Thanks. KB

  • Create New...