Fred

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.

It could be worse. They could have called it the Internetduino.

It could be worse. They could have called it the Internetduino.

It could be worse. They could have called it the Internetduino.

I'd say that if the FET / hub side of things is where the problem is, then it makes a good candidate to be programmed using the FET on the other launchpad and left permanently in your project. You could even cut the broken FET part off.
 
(Edited for phone keyboard typos.)

I'd say that if the FET / hub side of things is where the problem is, then it makes a good candidate to be programmed using the FET on the other launchpad and left permanently in your project. You could even cut the broken FET part off.
 
(Edited for phone keyboard typos.)

One thing the TRF7970 has taught me is that QFN is a PITA. 
Well, I'm actually off to meet monsonite on the pub. Let's hope that doesn't adversely affect his ability to get an LED blinking by sunrise!

One thing the TRF7970 has taught me is that QFN is a PITA. 
Well, I'm actually off to meet monsonite on the pub. Let's hope that doesn't adversely affect his ability to get an LED blinking by sunrise!

Ti dropped a new launchpad today, it isn't even listed on the ti.com/launchpad page. 
 
From the email:
 
"the world

Last week, I put together a design for a lightweight dev-board using the MSP4302433, known as "ChipStick".  ChipStick is a 20 pin DIL module that can plug into the socket on a G2 Launchpad.
 
In the week whilst waiting for the prototype boards to arrive, I have prototyped the design using a SMT adaptor - allowing it to be built on a breadboard.  Today I have refined the original concept, to produce a second design which, being small I have called Nanode (very small node).  
 

 
Nanode is effectively the same circuit as ChipStick, but trimmed to make a smaller form factor. The main difference is that it is pinned out to a 1.27mm pitch 2 x 10 pin connector - rather than the 2.54mm pitch DIL socket. I have also dispensed with the detachable programmer section.  "Where we're going Marty, we don't need programmers"
 
I have featured it on my  recent blogpost, 
 
http://sustburbia.blogspot.co.uk/2016/03/digital-dust-further-journey-into-nano.html
 
Once I have working examples, as usual I will make the design CAD files available.
 
 
 
Ken

I know the FET in the G2 LaunchPad was limited to what microcontrollers you could program with it - i.e. the "value line" topping out at the G2955. I don't know if this has changed with the introduction of more powerful LaunchPads. Anyway, I wouldn't assume that a FR2433 would work in the DIP socket of the G2. 

I've managed a few. Swapping VCC and VSS on my first etched PCB was a good one. I'm glad I'm not the only one who's done that.
 
I also noticed that a TS430RGC64USB target board that I had supported the F5510 that I was coding for. Great! So I stuck it in and wondered why it didn't work. It turns out that a LQFP48 will fit in a QFN64 socket. It might not fit that well or work, but it goes in.
 
Amazingly neither of these (and probably worse that I've forgotten) damaged the MSP430.

When something doesn't work one of the first things I do is swap I/O pins. Even if I'm pretty sure it's right. In fact this exact thing happened last night between a LPCXpresso1769 and an SD card. (Sorry for the MSP430 infidelity - I'm working on some Smoothieboard improvements.)

I've managed a few. Swapping VCC and VSS on my first etched PCB was a good one. I'm glad I'm not the only one who's done that.
 
I also noticed that a TS430RGC64USB target board that I had supported the F5510 that I was coding for. Great! So I stuck it in and wondered why it didn't work. It turns out that a LQFP48 will fit in a QFN64 socket. It might not fit that well or work, but it goes in.
 
Amazingly neither of these (and probably worse that I've forgotten) damaged the MSP430.

I've managed a few. Swapping VCC and VSS on my first etched PCB was a good one. I'm glad I'm not the only one who's done that.
 
I also noticed that a TS430RGC64USB target board that I had supported the F5510 that I was coding for. Great! So I stuck it in and wondered why it didn't work. It turns out that a LQFP48 will fit in a QFN64 socket. It might not fit that well or work, but it goes in.
 
Amazingly neither of these (and probably worse that I've forgotten) damaged the MSP430.

Awesome work as always.
 
What are you using the Smoothieboard for? The mill or the laser? I've recently switched my laser over to one and started contributing to the software. Nothing much so far - just added TTL laser control for now. I'm hoping to add PPI (pulsed cutting) later to help with making mylar solder stencils.
 
Coding for the NXP LPC1769 isn't as nice as any of TI offerings so far. Believe it or not I miss CCS!

Ran the enclosures through my Mill, made a little jig to aid in positioning.


 
There are a few issues left to sort out.
PCB is not retained downward in the enclosure, when removing USB the PCB lifts upwards. LEDs leak light between their corresponding holes in the enclosure Button needs a mechanism to reach up through the case. I plan to solve these issues by creating 2 custom parts.
Part A:
This part will wedge between the PCB and top of the enclosure. Have holes over the LEDs to create light pipes out of the enclosure. A channel around the button to house a switch cap, part B. Part B:
Switch cap, poke through the cutout in the enclosure  
I decided to use my CNC to make molds to form the parts out of polyurethane. Straight from the CNC. You can see the switch part took a few attempts to get the tolerance right.

 
Fitted


 
Button fits perfectly flush with the case to avoid accidental presses.



 
 

My first PCB had vcc and vss switched. Nothing a couple of bodge wires and cut tracks couldn't fix.
 
My tips: Add a few test points. If you have distinct sections like a microcontroller and a peripheral, then add traces between them can be probed or cut. If one bit is wrong you can at least isolate it and make sure the rest it is OK before you make version 2.0.

Too shy to tell us yourself, @@bluehash? Well, I'll have to do it then!
 
It looks like 43oh has won TI's Community Highlight Award. Definitely well deserved. This place has always been a great source of help and inspiration. Probably the reason why I use TI stuff rather than anyone else's.
 
Well done.

In addition to what Rob says. Our ideas are *not* unique. What I mean by this is that if any one of us can write code to do x.y.z, then there are probably thousands of other developers who could write identical, or very similar code. Without ever seeing our code initially.
 
So I kind of get the idea what we do is our thing, and all that. But "hoarding" code in my opinion is very bad form. Also, if one writes code around a bit of hardware that other wise does not have software written for it ( drivers ) I tend to look at that situation that the code is not owned by the writer anyhow. It's *not* their hardware IP, how in the hell can they claim software IP ? Anyone can read a datasheet, or technical reference manual, and write code around that . . .
 
All that said however, it is really bad form and quite honestly chicken s**t of a company, or business to behave in this manner. But you know . . . why else do you guys / gals think that companies make their hardware, and software designs open sourced ?
 
EDIT:
By the way, my thoughts have nothing to do with what is legal, and whats not. My idea are based on what I would consider good ethics.

432 is here to stay. Expect to see more devices with a variety of memory, speed, peripheral, and package options. If you are building with a blend of performance and low power in mind, MSP432 can get you there. Did you see it's going to Antarctica?

Did some more work today.
 
Wanted to check out the size of the buttons, so I printed half a profile to get a feel for button placement, I feel like I had designed these a bit too small.

 
Took a closer look at the battery protection circuitry. unsoldered one and sanded it down to get good images of the copper. then worked the images in photoshop.


 
These have been added to the schematic/pcb so I don't have to have the board soldered inline.
Schematic has been done.

 
PCB is routed too, and here it is in it's natural environment.


 
(Kicad 3d export is still kind of dodgy, components changing colour etc :/ )
 
Surprising how complicated a design can become, from such a simple idea.
Off to the fab tomorrow.

TI has 'launched' a multi protocol wireless launchpad.  
It uses the CC2650 chip:  The CC2650 device is a wireless MCU targeting Bluetooth Smart, ZigBee and 6LoWPAN. The CC2650 device contains a 32-bit ARM

Too shy to tell us yourself, @@bluehash? Well, I'll have to do it then!
 
It looks like 43oh has won TI's Community Highlight Award. Definitely well deserved. This place has always been a great source of help and inspiration. Probably the reason why I use TI stuff rather than anyone else's.
 
Well done.

Too shy to tell us yourself, @@bluehash? Well, I'll have to do it then!
 
It looks like 43oh has won TI's Community Highlight Award. Definitely well deserved. This place has always been a great source of help and inspiration. Probably the reason why I use TI stuff rather than anyone else's.
 
Well done.