Jump to content
43oh

Fred

Members
  • Content Count

    885
  • Joined

  • Last visited

  • Days Won

    43

Everything posted by Fred

  1. Things I would do: Check voltage on VCC and RESET. Bodge on some sort of SBW header. Try to find a place where RESET and TEST are available. Maybe solder some temporary wires on the bottom of the IC socket's pins. Check the obvious again - continuity to GND, VCC, etc. When you eventually find it, it will probably seem stupid and obvious! I believe it's just VCC, ground, RESET pulled high.
  2. @@Rickta59 True. Although above he did say it's not working on the board. I must admit I'm still a little confused as to what @@yyrkoon is asking. A photo will definitely help.
  3. In which case, I'm with the guys who say to add a SBW header. Don't forget the pull up resistor and capacitor. That's the only other thing that the Launchpad part adds to the DIP chip. You will be able to disconnect the jumpers on an unmolested Launchpad and use that for programming and debugging. No need for cutting.
  4. I think there's a really simple solution to this, so the chances are I've misunderstood what your asking! You can physically cut and separate the FET part of a G2 Launchpad from the target device. All you need to do it cut carefully along that dotted line. Leave the target half in your project. Connect them back up for programming and debugging. Test this out by just removing the jumpers before you cut. If you don't feel destructive, just use 2 Launchpads.
  5. I'm really trying not to buy Launchpads when they come out just because they sound cool. I have way too many already, some of which have hardly been used.
  6. WTF is an of-the-shelf IoT gateway anyway? Just an rebranded ordinary router? An edge router for every protocol they thought of - Zigbee, 6LoWPAN over various frequencies, etc.? Sounds like a scary idea. By the way, there's now an OWASP for IoT. Not great but better than nothing. Not sure where I heard about it. Apologies if it was here! https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project
  7. I'd say the main (perhaps only) reason for making your own PCBs is if you enjoy it. Whilst in theory I could make a board in a couple of hours, it would take me 2 weeks to find those spare hours!
  8. A CNC mill is great and I'd really recommend one. However, I gave up on using it for PCB milling and switched to photo resist etching.
  9. If you've been set this as coursework then I'd suggest you start with what you've been taught. There are plenty of helpful people here that will be glad to assist if you're stuck on something specific and have tried working it out yourself first. What you won't find are people to do your assignment for you. This assignment has probably been given for a good reason. If someone creates a solution for you that doesn't use any of the principles you've been taught then it'll be fairly obvious and you'll probably fail. Also, 43oh is about the most prominent resource for MSP430 information. Your
  10. That also sounds very specific and a bit like it's your coursework.
  11. I've used Windows 10 on the Pi. It's a bit unfinished but shows some promise. I'm planning to use it for an upcoming project at work. My team is mostly C# developers and they'd definitely feel more comfortable with it. The plan is that they'll be able to contribute too.
  12. The examples I've seen from TI for edge routers on sensor networks (6LoWPAN, etc.) tend to use the BeagleBone with an appropriate USB radio.
  13. I've just started playing around with the CC3200 Launchpad as I'm also finding it tricky. I think it's definitely the CC3200 that's difficult as playing with the TM4C1294 Connected Launchpad and TI-RTOS beforehand wasn't too bad. Here are some things I seemed to have to find out the hard way. Please correct me if you know better I've got anything wrong. Flashing with CCS Uniflash Connect using CC3x Serial (UART) Interface, not Stellaris In-Circuit Debug Interface. The SOP jumper must be set to 2 You must power cycle the whole board if you change the jumper. Not just the reset button.
  14. As stated in the title. https://e2e.ti.com/support/wireless_connectivity/proprietary_sub_1_ghz_simpliciti/f/156/t/469373
  15. The latest SimpleLink Starter android app seems to support the WiFi SensorTag, so that's a good sign that it's on the way. There also seems to be a CC1350 version coming about the same time.
  16. CC2650 is 2.4GHz. I would assume that OpenThread is independent of the underlying frequency. Not sure why I thought the Nest implementation was using 2.4GHz - probably either a poorly researched article on it or just my assumption. I understand exactly what you mean about it seeming "green". This is the best I've found - a blog by a TI employee but not the easiest to follow. I'm sure he'll do some CC1310 stuff too. http://sunmaysky.blogspot.co.uk
  17. Well, it seems that the "SimpleLink Starter" Android app is finally available. It's still quite SensorTag focused, but does support the CC2650 Launchpad. It also references the as yet unavailable WiFi SensorTag. I've still not done much with the LaunchPad. When Google open-sourced their Thread protocol I thought it might be possible to link a launchpad up to a Nest mesh network, but that doesn't look likely any time soon according to TI employees over on e2e. Even the documentation and support on 6LoWPAN seems lacking for the CC2650 right now.
  18. That is very nice work. Far better than some of the rubbish on Hackaday recently.
  19. Doesn't the CC2650 cover the BLE bit? It's not an MSP430, but there's a launchpad available. A little bit more in the way of guidance (especially if you want to go 6LoWPAN) could make it just as easy to use.
  20. Some more support for the CC2650 Launchpad would be nice. The SimpleLink Starter android app mentioned in the quick start guide still doesn't exist. The board has some potential but seems to have been released before things were ready.
  21. Yes, I did assume web. I still think that you're better to let the clients identify themselves with a token rather than to track them. Better practice in an environment where a clients may disappear at any point, share a proxy, etc. Obviously, I don't know exactly what you're trying to do so you may have specific requirements. I also hadn't noticed you're using Energia. I use the "new posts" link and hasn't spotted the category. I don't use Energia so won't be able to help with anything specific. I'm going through the TI-RTOS examples at the moment.
  22. I've just started looking at a web server project myself. I can't help with this exact problem (yet). However, are you sure this is the right approach? Web stuff works best if you don't try to retain knowledge of clients. A cookie handed to the content on first request and detected afterwards might be a better way. Something added to the URL (e.g. query) is another way if you're not worried about one client easily impersonating another.
  23. A few things from me. Device pinouts - the MSP430-TS range of target boards are quite useful for prototyping. The inconsistent pinouts between devices in the same package mean that one target board doesn't cover many devices. This makes them too expensive for the use they'd get - for hobbyists at least. Not an easy thing to change, but perhaps something to bear in mind for future devices. Energia. I'm not a fan. I understand that it's to try to bring over some of the hobbyists from Arduino, but is this really a good idea? Everything about the Arduino is awful. The MSP430 and CCS is so
  24. I assume you mean over a USB serial port, although it would also be possible to emulate a USB keyboard typing those strings. Take a look at the USB CDC examples for the F5529 Launchpad. That would be a good starting point.
×
×
  • Create New...