Jump to content
43oh

zeke

Members
  • Content Count

    1,782
  • Joined

  • Last visited

  • Days Won

    102

Reputation Activity

  1. Like
    zeke got a reaction from bluehash in Ideas to share more code   
    Some dev boards could be kind of expensive.
     
    I think that you ought to take a deposit from participants. Sort of a "Put your money where your mouth is" clause.
     
    Or, you could put together a contract between developer and recipient. Then you could add in a token amount of money so that it legally becomes clear what's occurring - fee for service.
  2. Like
    zeke reacted to NatureTM in Flashing the missing DCO calibration constants   
    I guess it does belong in this thread. The other thread sets the DCO at runtime, while this thread and the code you posted actually flashes the calibrations after setting the DCO.
     
    The code looks nice, and I wonder if I should edit the first post of the thread to link to what you found instead.
  3. Like
    zeke got a reaction from bluehash in MSP430 data acquisition from multiple sensors   
    Well, that sounds like an exciting project! A whizzy cool pedometer. Right on!
     
    By the way, if you add a gps, gobs of RAM and FLASH, a monster cpu and a cellphone module then you will have a Parole Ankle Module. Just like Paris Hilton or Martha Stewart had.
     
     
    The first thing you should do is investigate the communication methods between the sensors and the micro. I haven't looked up the sensors but I bet that they talk either SPI or I2C.
     
    Once you figured that out then you could begin by selecting one of the devices and write some c code to talk with it. Once you've done that then you've written your first device driver. WOO HOO!
     
    If the remaining sensors speak the same way then it's a matter of repeating the device driver development for each sensor. Each one may be slightly different from the others so the datasheets will be your close companion.
     
    I know that the SD card is an SPI device and there's sample code out there that you could embrace and extend for your needs. I know that TI's MSP430F5529 has a dev board with an microSD card on it. I also believe that the MSP430F5438A has a dev board with microSD card on it.
     
    So you could download the sample code for either of those boards and use it as a starting point. Most likely, you will rip it out of its context and then patch it into your system. It's just like working with Lego blocks.
     
    If you post up some code then we are willing to help you refine your work. As many others here have said, we'll help you succeed but we won't do the work for you.
     
    Remember this. There's nothing to fear. Failure is perfectly acceptable thing because it tells you what not to do. You can design it out of the results though. So make a plan/design. Adapt it as needed. You WILL succeed!
     
    Please post some pictures of it for us.
  4. Like
    zeke got a reaction from RobG in MSP430 data acquisition from multiple sensors   
    Well, that sounds like an exciting project! A whizzy cool pedometer. Right on!
     
    By the way, if you add a gps, gobs of RAM and FLASH, a monster cpu and a cellphone module then you will have a Parole Ankle Module. Just like Paris Hilton or Martha Stewart had.
     
     
    The first thing you should do is investigate the communication methods between the sensors and the micro. I haven't looked up the sensors but I bet that they talk either SPI or I2C.
     
    Once you figured that out then you could begin by selecting one of the devices and write some c code to talk with it. Once you've done that then you've written your first device driver. WOO HOO!
     
    If the remaining sensors speak the same way then it's a matter of repeating the device driver development for each sensor. Each one may be slightly different from the others so the datasheets will be your close companion.
     
    I know that the SD card is an SPI device and there's sample code out there that you could embrace and extend for your needs. I know that TI's MSP430F5529 has a dev board with an microSD card on it. I also believe that the MSP430F5438A has a dev board with microSD card on it.
     
    So you could download the sample code for either of those boards and use it as a starting point. Most likely, you will rip it out of its context and then patch it into your system. It's just like working with Lego blocks.
     
    If you post up some code then we are willing to help you refine your work. As many others here have said, we'll help you succeed but we won't do the work for you.
     
    Remember this. There's nothing to fear. Failure is perfectly acceptable thing because it tells you what not to do. You can design it out of the results though. So make a plan/design. Adapt it as needed. You WILL succeed!
     
    Please post some pictures of it for us.
  5. Like
    zeke got a reaction from NatureTM in The Party Thread!   
    Oh YEAaaaaaaaaaaaaah!
     
    I feel a fever coming on!
    And it's not even Saturday!
     

  6. Like
    zeke reacted to NatureTM in The Party Thread!   
  7. Like
    zeke reacted to gatesphere in The Party Thread!   
    *orders a shirley temple*
    *gets stared at* Whaaat? They're tasty.
  8. Like
    zeke got a reaction from jsolarski in Power supply testing procedures?   
    Well, it looks like I'm gonna answer my own question.
     
    I found this document that describes the salient details of power supply testing.
  9. Like
    zeke got a reaction from bluehash in Circuit Diagram Website   
    I regularly watch the RSS feed from this website: Electronic Circuit Diagram.
     
    There's some pretty interesting circuits there.
     
    I thought you all might like to follow it too.
  10. Like
    zeke got a reaction from Rickta59 in Circuit Diagram Website   
    I regularly watch the RSS feed from this website: Electronic Circuit Diagram.
     
    There's some pretty interesting circuits there.
     
    I thought you all might like to follow it too.
  11. Like
    zeke got a reaction from jsolarski in Circuit Diagram Website   
    I regularly watch the RSS feed from this website: Electronic Circuit Diagram.
     
    There's some pretty interesting circuits there.
     
    I thought you all might like to follow it too.
  12. Like
    zeke got a reaction from GeekDoc in Circuit Diagram Website   
    I regularly watch the RSS feed from this website: Electronic Circuit Diagram.
     
    There's some pretty interesting circuits there.
     
    I thought you all might like to follow it too.
  13. Like
    zeke got a reaction from fj604 in Launchpad Oscillator fault triggered   
    Strange to say this but how sweaty are your hands?
     
    Do a quick test.
     
    First, see if your unwashed hands can mess up the crystal.
    Then, wash your hands with hot water and good soap and then try to mess up the crystal again.
     
    What happened? Any difference?
     
     
    From a code point of view, this is what I use when I run the 32kHz crystal:

    void main(void) { WDTCTL = WDTPW + WDTHOLD; // Stop watchdog timer BCSCTL1 = CALBC1_1MHZ; DCOCTL = CALDCO_1MHZ; BCSCTL3 |= XCAP_3; // Launchpad watch crystals need ~12.5 pF ... }
  14. Like
    zeke got a reaction from microcozmoz in Best information for those new to the MSP430?   
    So, now you got a job doing hardware design and you want to use the MSP430 in your design.
     
    But you've discovered that your boss has insisted on using this "wicked cool awesome" and ancient 5V sensor because they have a bazillion in stock.
     
    "What's the problem with that?" you ask.
     
    The problem is this: the MSP430 is a 3.6V device and it doesn't have 5V tolerant I/O's. This means that you'll probably hurt the part if you put 5V into an input. Go ahead and google it. You'll find our very own OCY schooling someone on this topic back in 2008. I'll let you find the article. OCY is shy. And he's probably gonna rip me open for giving away his secret identity.
     
    So, what's the answer? SLAA148 is the answer.
     
    It will take you through the various input and output scenarios that you may face trying to interface to higher voltage systems - not just 5V.
     
    Using this information, you should be able to measure the status of a 12V power supply with the A/D inputs or figure out how to drive a 12V relay.
     
    Have a read. It's useful info.
  15. Like
    zeke reacted to nobody in Launchpad Oscillator fault triggered   
    If you plan to permanently use the crystal, it is a good idea to remove the 0 Ohm resistors between oscillator and pin header. The basic idea is to minimize the size of the routes in the oscillator circuit. And of course set the appropriate size of capacitors (SLAU144H page 285).
  16. Like
    zeke got a reaction from bluehash in Ethernet to serial module?   
    I'm having a ball tonight.
     
    I just figured out how to edit and to recompile the on-board file system on the S2E module. I went and re-branded it for fun.
     
    Then I figured out how to program the S2E module using the ethernet port and the TI/LM utility program. 89kB in 3 seconds. Who needs a JTAG programmer? BWAAAHHAAAAhaaaaaaa
     
    The demo html pages are kludgy. Someone decided that frames would be really neat. They're not.
     
    I'm going to dump the frames and see if I can whip up some DHTML/CSS style pages. Should be fun.
     
    Here's a picture of my re-branding job I did tonight.

  17. Like
    zeke reacted to SugarAddict in Misc (3.6v USB power, 8x8 led matrix slave)   
    It Just Worked.
  18. Like
    zeke got a reaction from RobG in Oscilloscopes and such...   
    I've used the USBee at work and I don't recommend it.
     
    The Saleae Logic or Logic16 will kick the crap out of it Bruce Lee style.
     
     
    As far as scopes go, you should consider your budget first. You want to purchase the best device that your limited amount of money can buy.
     
    You could find an old Tektronix 465B or 2235 online for around $500. Both are 2 channel, 100MHz analog scopes. I have a 2235.
     
    If you are independently wealthy, then you should consider a Tektronix since many are on sale right now.
     
    Or you could get a Rigol if you don't like the Tek tax.
     
    Buy the best you can afford because you're going to have it for a long time. I've had mine for 20 years.
  19. Like
    zeke got a reaction from jsolarski in Ethernet to serial module?   
    I received my Stellaris S2E kit today. It's a neat little device.
     
    The serial interface board is kinda weird but I understand why they stacked it up that way. The USB cable is there to supply power to the target board. Sneaky.
     
    I like the little webserver on-board. It's slow but it's there so that you can configure the communication parameters.
     
    The telnet interface is cool. Telnet to x.x.x.x:23 for port1 and x.x.x.x:26 for port2. You've gotta have a terminal connected to the DB9 serial port connector to perform end to end testing.
     
    I see this as a reference design device. It should be adapted to your application - whatever that might be.
     
    I can see this being successfully adapted as an LP shield board. It would need a complete board respin and some new code created.
     
    I can also see this ref design being successfully adapted as an ethernet to Zigbee link board. Again, a new board would be created to accommodate a Digi board and the code could be modified to be able to configure the Digi module.
     
    I'm going to keep playing with this module. I may even get a second one so that I can try a long S2E2S link configuration.
     
    All in all, I think it's a 9 out of 10 on the Nerdy Cool Scale

  20. Like
    zeke got a reaction from RobG in Ethernet to serial module?   
    I should also point out a small but important detail about this S2E kit.
     
    There are two S2E kits on the TI/Stellaris: RDK-S2E and MDK-S2E.
     
    The RDK-S2E kit is normally ~$150.
    The MDL-S2E kit is normally $50.
     
    The RDK is on special for $50 until the end of May.
     
    The difference is all the extra stuff you get with the RDK. Take a look at the photos at the above links to see what I mean.
     
    So, this is why this deal is a good one - the extras.
  21. Like
    zeke got a reaction from bluehash in Ethernet to serial module?   
    I received my Stellaris S2E kit today. It's a neat little device.
     
    The serial interface board is kinda weird but I understand why they stacked it up that way. The USB cable is there to supply power to the target board. Sneaky.
     
    I like the little webserver on-board. It's slow but it's there so that you can configure the communication parameters.
     
    The telnet interface is cool. Telnet to x.x.x.x:23 for port1 and x.x.x.x:26 for port2. You've gotta have a terminal connected to the DB9 serial port connector to perform end to end testing.
     
    I see this as a reference design device. It should be adapted to your application - whatever that might be.
     
    I can see this being successfully adapted as an LP shield board. It would need a complete board respin and some new code created.
     
    I can also see this ref design being successfully adapted as an ethernet to Zigbee link board. Again, a new board would be created to accommodate a Digi board and the code could be modified to be able to configure the Digi module.
     
    I'm going to keep playing with this module. I may even get a second one so that I can try a long S2E2S link configuration.
     
    All in all, I think it's a 9 out of 10 on the Nerdy Cool Scale

  22. Like
    zeke reacted to bluehash in MSP430 LaunchPad Book?   
    MSP430 Microcontroller Basics is one. Some members over here have it, maybe they can chime in.
     
    [PS. The above link is an Amazon affiliate link. If you decide to buy it by going through the above link, 43oh gets a small amount(~6%). There is absolutely no obligation to do so though.]
  23. Like
    zeke got a reaction from MadhaV in Question regarding Launchpad Programmer.   
    To quote Wikipedia:
     
    Debugging interface
     
    In common with other microcontroller vendors, TI has developed a two-wire debugging interface found on some of their MSP430 parts that can replace the larger JTAG interface. The eZ430 Development Tool contains a full USB-connected Flash Emulation Tool ("FET") for this new two-wire protocol, named "Spy-Bi-Wire" by TI. Spy-Bi-Wire was initially introduced on only the smallest devices in the 'F2xx family with limited number of I/O pins, such as the MSP430F20xx, MSP430F21x2, and MSP430F22x2. The support for Spy-Bi-Wire has been expanded with the introduction of the latest '5xx family, where all devices have support Spy-Bi-Wire interface in addition to JTAG.
     
    The advantage of the Spy-Bi-Wire protocol is that it uses only two communication lines, one of which is the dedicated _RESET line. The JTAG interface on the lower pin count MSP430 parts is multiplexed with general purpose I/O lines. This makes it relatively difficult to debug circuits built around the small, low-I/O-budget chips, since the full 4-pin JTAG hardware will conflict with anything else connected to those I/O lines. This problem is alleviated with the Spy-Bi-Wire-capable chips, which are still compatible with the normal JTAG interface for backwards compatibility with the old development tools.
     
     
    Take a look at this thread for a technical discussion on the topic.
  24. Like
    zeke got a reaction from bluehash in Best information for those new to the MSP430?   
    Note: This is a follow up on the JTAG posting above.
     
    This is very valuable information that you should remember.
     
    The MSP-FET430UIF is TI's programming tool. It is able to program an MSP430 using either JTAG or Spy-Bi-Wire. I recommend that you get one if you don't already.
     
    The MSP430 Hardware Tools - User's Guide is its user manual. You want this document because it will aid you in your circuit design choices.
     
    Pay special attention to pages 25 and 26. These circuit diagrams will show you the difference between JTAG and Spy-Bi-Wire circuits.
     
    When you design your product for your customer, you should refer to this User Manual so that you select the correct circuit and components. Then you will be able to mass manufacture your devices with confidence knowing that you will be able to program them.
     
    Also, one more note. The LaunchPad can be used as a programmer for your devices. But, you should take note of which device will be supplying power. Will it be the LaunchPad or the Target Device? Please don't say both. You will light something on fire if you do. Most likely the Target MSP430 will suffer from the excessive amount of heat you generate in it. Learn from my personal experience!
  25. Like
    zeke got a reaction from jsolarski in Question regarding Launchpad Programmer.   
    To quote Wikipedia:
     
    Debugging interface
     
    In common with other microcontroller vendors, TI has developed a two-wire debugging interface found on some of their MSP430 parts that can replace the larger JTAG interface. The eZ430 Development Tool contains a full USB-connected Flash Emulation Tool ("FET") for this new two-wire protocol, named "Spy-Bi-Wire" by TI. Spy-Bi-Wire was initially introduced on only the smallest devices in the 'F2xx family with limited number of I/O pins, such as the MSP430F20xx, MSP430F21x2, and MSP430F22x2. The support for Spy-Bi-Wire has been expanded with the introduction of the latest '5xx family, where all devices have support Spy-Bi-Wire interface in addition to JTAG.
     
    The advantage of the Spy-Bi-Wire protocol is that it uses only two communication lines, one of which is the dedicated _RESET line. The JTAG interface on the lower pin count MSP430 parts is multiplexed with general purpose I/O lines. This makes it relatively difficult to debug circuits built around the small, low-I/O-budget chips, since the full 4-pin JTAG hardware will conflict with anything else connected to those I/O lines. This problem is alleviated with the Spy-Bi-Wire-capable chips, which are still compatible with the normal JTAG interface for backwards compatibility with the old development tools.
     
     
    Take a look at this thread for a technical discussion on the topic.
×
×
  • Create New...