Jump to content
43oh

cyberman_ff

Members
  • Content Count

    29
  • Joined

  • Last visited

Everything posted by cyberman_ff

  1. That appears to have fixed the issue. It seems CCS studio tools have less stable software (Java API might cause this?) than using a CLI tool (under linux). Thanks for your wisdom. Stephen
  2. I installed under linux (Gentoo AMD64) CCS6.1.1 Ran the script to install the drivers (install_drivers.sh) Started CCS6.1.1 Toke a quick example program, did a build and then ran debug It wanted to "update" the FET version on the launchpad so "silly" me said "OTAY" so it fails. I thought "ok not a good thng but let me try this again" it gives "recover" option so I tried that. it fails. I take ye olde launchpad (now known as victim of random update for the FET) to work just too see if it works under "lincensed" vindows variant. It doesn't recognize their is even a FET pluged in. I hav
  3. Congrats The FIFO on that part makes it invaluable to be honest. I was looking at making a booster a while back using SPI with this. Most of the bigger launchpads have lots of uarts unfortunately sometimes you need a lot more (sad). If you combine DMA with SPI you can run that thing pretty fast. The additional IO is handy too. My plan was 4 ports with both cmos and level shifted output options I was looking at the F5529lp (40pin launchpad pinout) as the board to plug into. Maybe when I have time I'll build i. If I had done it a when I was thinking about it I could use it for work (heh).
  4. I looked at that, it's not exactly a hobbiest scale device (LOL) it's the full 80 connection launchpad layout. That aside it is an interesting part it appears to be for competing against the SAM4E. Don't quote me on that. I know they are working on an ARM based part with a 24 A2D and 8 channel mux. That is a tricky beast too tame. Cyb
  5. Thank you just what I asked for. The pdf says you have a mac. Again thanks.
  6. And now for something completely different suggestions 1: PDF of the schematic if it behoves the author to do so? I just hate trying to print PNGs and color (IE I want BW and fine pixel resolution). 2: A big white patch or something to indicate which side of the board toward what pins, or marking the 3.3V pin and ground pin on the side that mates to the lunchpad (or launchpad ) 3: otherwise pretty cool Did you use KiCAD to do the schematic? Cyb
  7. If you have the time I'll get my camera out and look using my tripod to get a good shot of it my eyes aren't able too zoom in that well
  8. I suggest you outline what you need, first. Then what tools you have. You can use a EXP-msp430F5529lp without trouble to program a board without the added parts (QFN 5528 I think the lp has on it). You can use the BSL but that requires more specialized circumstances to start up (BSL button on that board) I don't know what software is needed to use the BSL option. List what you intend to do List what you believe you need to do it. Find the difference. It's easy to program the LP board as is but it doesn't have all the IO I would like on it (heh). You can use that board to program your boar
  9. You can use a DS2480 and a FT230X to make a little USB CDC one wire connection. The laptop might be using a DS2480 itself (I used them for programing DS2432's a long time ago {I think it was?}) anyhow if so that means it is using a UART to communicate. Hmmm anyhow I digress. The DS2480 I believe you can use to snoop the 1 wire bus (make your life somewhat easier I guess?) Never was a big fan of the 1 wire thing but that's probably just me. The DS2502 has 1kbit of OTP EPROM it also has a unique 48 bit serial number the latter may also be used (IE included with the laptop information in
  10. If I may toss some advice your way. 1: bewary of the burden voltage of your DMM it's an inherent problem with precisely measuring current it will screw your readings up if you aren't careful (back ground + http://www.eevblog.com/2009/04/08/eevblog-2-burden-voltage-and-hp-multimeter-review/ http://www.eevblog.com/projects/ucurrent/ ) 2: You may wish to sprinkle (LOL sorry just gives me a chuckle to use that word with resistors) 1 and 10 ohm < 1% resistors (.1 prefered) for each device on your board. Have your O scope handy to watch current over time also. Are you planning re
  11. @@RobG in words of one syllable "oh". Hmmm here I had my own woe is me thing planned out for the next week. Darn just have to make do with some LCD's instead. Thanks again. You know I probably should download the library too (just a sudden thought huh?) Cyb Addendum received, thanks.
  12. Out of stock (the shock is overweliming) heh. I waited 2 days too long darn it. Anyhow this I can see as a popular item because DIY with the flexible interconnect is a real pain (hehehe). putting the smt flex interfaces on can be harrowing (even if you done it a few times) also the SD card socket is a definate bonus. That's just me saying "cool but I missed out the last batch". Cyb
  13. A suggestion before you begin to 'convert' it you may want to grab TI's smart RF tool. You will need that to generate the data to compile in for the firmware update. The register access and locations are different but the CC430 and the CC1101 are mostly similar in what registers do what. (mostly) I don't know what the firmware in the watch is as I've haven't had then time to play (frolic even) apart from setting the time (seriously). Anyhow the smart RF tool will help you know what changes when you change the base frequency. Be aware it's not a perfect tool (heh) it can dump out code
  14. ike: Oi ... I have been doing thatPossum That is more what I was looking for thanks.
  15. I have 2 seperate msp430f5529 USB experimentor boards running code for the same program. The problem is I'm not sure how to program one board with the identical application software under code composer studio. IE JUST program it, nothing more. It wants you to run a debug session each time. I plan on doing that on the 'other board' kind of frustrating too me. I am using the MSP-FET430UIF for debugging and programming. Ideas and or suggestions welcome. Cyb
  16. If you are using simpliciTI there are ASSERT statements that will cause the code to end up in an endless loop if the statement is not true. Look for 'ASSERT'. It depends on the state it's looking for. These assume you are using a debugger when you are runing code. I would suggest running the node that goes out to lunch using CCS and in debug mode (just run it and wait for it to hang) then pause execution. That will show you where it's going out to lunch. It could be in the mrfi or bsp code. I was frustrated at first until I discovered that "feature" it had. The ASSERT macros are useful unt
  17. I hate it when that happens I'm glad your problem was resolved.
  18. Did you look at the compilor assembly output in the .lst file for the C code? That might give you a hint what's different. Cyb
  19. The only reliable method I've found to wait until something is transmitted is main_loop: bit.b #UCA0STAT, &UCBUSY jz main_loop That guarentees that it's not transmitting before you transmit. Although TI seems to extensively abuse the IFG flags DON'T use it for serial comm (of ANY KIND) that is NOT what it's intended for. The UCBUSY flag IS intended to indicate when serial com is occuring. So use that instead. I had to fix TI's code several times if I changed the processor frequency because of the use of the IFG flag, (in summary). Use UCBUSY it is specifically their just for what you ar
  20. If you ever get bored try looking at this document from TI, section 1.2.3 covers the spy-bi-wire interface and timing. The high level API for the FET (msp430xxx.dll) is designed to work through the USB CDC com portinterface. They did this primarily to create linux compatibility with the interface. It is too expensive and legally difficult to use a proprietary driver for devices like that so they choose to reduce the propretary end of things. Cyb
  21. At least you have the TI JTAG (FET) interface on it. :grin: The ez430 would allow you to use a regular launchpad for the programmer (a bit more easily) as it has the 6pin 1.27mm pins built in (just not the header) then again adding the femal connector on your end I'm uncertain what part they are off the top of my head (sad indeed). I obtained 6 pin to 6 pin female to female flex cables for doing this sort of thing for a msp430F5341 board (work related). The only issue with that is then you have the pins mirroed on the other end if you aren't careful (sigh). So you need the female header (h
  22. Hmm ouch poor fish. However a cat induced fatality is hardly your fault. The cat could have just as well eaten the poor fish. Which reminds me of some lessons I've learned in temperature controllers hard sensor failure indicator (IE if it gets disconnected) with automatic emergency power disconnect (1 second usually in case of transients etc.) hard and seperate over temperature controller + sensor, that is always ALWAYS latching (IE it would disconnect everything until power is removed) always have an analog signal you can read with a multimeter (IE verify what your processor THINKS it's
  23. Hmmm you needed to add a disclaimer saying "no fish were injured cooked or otherwise killed in this pot" Erstwhile I liked your 'toy robot' museum the big trak brought back memories of wanting to hack one of those with a TS1000 (timex sinclair) controlling it Cyb
  24. With the TUSB3410 the driver itself has to force the com port to a specific location, it does so when it creates the first instance and has the serial # to associate with it. However you need to specify it. If you use the TUSB3410 otherwise under winXP you get YET another com port (I have 33 have to remember how to delete the stupid things). I believe many other manufacturers devices do the same thing. Unfortunately you have to get TI blessing (IE you need to register with them and they let you get the data) to get the source for thier drive. The FET has 2 serial ports and is actually
  25. Good too know it works (LOL). I presume it took 10 minutes because you had 10 boards? I'm not overly fond of how USB is handled in windows. I'll refrain from windows hate but does the FTDI parts NOT magically add yet another COM port under windows? :grin: I believe they are already serialized (0x40- 0x4E I think it was in the MTP map). Hmmm I thought you could program them for that? (data sheet says 'no'.) I concur that would make more sense but then again I'm not a big fan of USB. It took them 4-5 years to get a COM device style anything for it, honestly that's kind of insane as almost
×
×
  • Create New...