Jump to content


  • Content Count

  • Joined

  • Last visited

  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 have a bricked called a launchpad? Can this thing be resurrected? The code I had originally on the launchpad still works (F5529) but the FET seems to have other issues. Anyway to fix this thing? Has anyone had such issues under linux? Is it possible to use BSL and reload the firmware into the FET on the LP board? I would appreciate some hints thoughts (maybe even humorous anecdotes?) I've always been leery about updating tools every time I updated CCS (because each time it's FAILED the first shot and I had to recover then reinstall). It's weird though that someone feels the need to "play" with the tools firmware every new version of CCS. Cyb
  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). Note you could set it so you can swap between spi and i2c (just connect a pin to VDD or GND).
  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 board for your purposes using the SBW method (those jumpers are on the board for that purpose). However write down your needed IO and anlogue (if you need USB or not etc.) It's better not to use the micro USB style connector they used as they are hard to get and less rugged than the mini B type (cables of useful length are a real challenge as the micro connector was designed for cell phone usage not for stuff like the lp). If you intend to use the USB you should decide the device class etc. (HID CDC MSC etc. ) or composite. The TI provided USB stack is nice but a bit bloated (seriously). I won't comment on thier interrupt usage as it wouldn't be polite. Anyhow you should decide what you need then determine what to implement from thier. Otherwise you can spin yourself in circles if you aren't careful. Cyb
  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 the bios DELL has some nasty bios tricks they pull). However it may be enough to have the power for the original device. Does the supply voltages for the PSU's vary? I have a DEAD Dell laptop sitting here in dire need of power so I will look at it's PCB, originally I was going to replace it's connections to the outside world but if it uses a varification system like this it could be interesting to rectify it's attitude with a smart power adaptor (similiar to what you've done basically). My greatest concern is properly matching the voltage however my guess is most laptops use the same 19V system? Cyb
  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 real time telemetry tracking? I was thinking something useing the CC110L myself it's a striped CC1101 (probably with defective support for features not "avaiable in the CC110L) Layout for those chips takes a fair bit of work Cyb have fun ...
  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 though for the register set on the CC430 in the watch just look at the settings carefully (their are a few to say the least). Cyb
  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
  • Create New...