chicken

I don't have a BeagleBone, but found these two articles from Ken Shirriff very insightful.
 
The BeagleBone's I/O pins: inside the software stack that makes them work
http://www.righto.com/2016/08/the-beaglebones-io-pins-inside-software.html
 
PRU tips: Understanding the BeagleBone's built-in microcontrollers
http://www.righto.com/2016/08/pru-tips-understanding-beaglebones.html
 
Like all his articles, these are long and VERY detailed. Solidly in the "all you ever wanted to know about.."  category.
 
I suspect (hope) there are more BeagleBone articles coming.

I don't have a BeagleBone, but found these two articles from Ken Shirriff very insightful.
 
The BeagleBone's I/O pins: inside the software stack that makes them work
http://www.righto.com/2016/08/the-beaglebones-io-pins-inside-software.html
 
PRU tips: Understanding the BeagleBone's built-in microcontrollers
http://www.righto.com/2016/08/pru-tips-understanding-beaglebones.html
 
Like all his articles, these are long and VERY detailed. Solidly in the "all you ever wanted to know about.."  category.
 
I suspect (hope) there are more BeagleBone articles coming.

I don't have a BeagleBone, but found these two articles from Ken Shirriff very insightful.
 
The BeagleBone's I/O pins: inside the software stack that makes them work
http://www.righto.com/2016/08/the-beaglebones-io-pins-inside-software.html
 
PRU tips: Understanding the BeagleBone's built-in microcontrollers
http://www.righto.com/2016/08/pru-tips-understanding-beaglebones.html
 
Like all his articles, these are long and VERY detailed. Solidly in the "all you ever wanted to know about.."  category.
 
I suspect (hope) there are more BeagleBone articles coming.

I don't have a BeagleBone, but found these two articles from Ken Shirriff very insightful.
 
The BeagleBone's I/O pins: inside the software stack that makes them work
http://www.righto.com/2016/08/the-beaglebones-io-pins-inside-software.html
 
PRU tips: Understanding the BeagleBone's built-in microcontrollers
http://www.righto.com/2016/08/pru-tips-understanding-beaglebones.html
 
Like all his articles, these are long and VERY detailed. Solidly in the "all you ever wanted to know about.."  category.
 
I suspect (hope) there are more BeagleBone articles coming.

I seem to remember that the stop condition needs to be indicated to the I2C peripheral before the last byte is received..
 
You may want to check out the I2C code in Energia.

Hooleygan,
 
Sorry to say, but you've got multiple, steep, learning curves ahead.
First, regarding your loop code (the while() statements). 
...while (Run_value = 1)...
You are assigning the value of 1 to Run_value, not testing it. Same with the following statement intended to test for zero.
To test for equality you need to use the "==" operator, not the "=" operator.  This can happen to experienced programmers too, as a typo.
Some use the following syntax so the compiler will generate an error:  while(1== Run_value), if you inadvertently attempt to assign with while( 1 = Run_value), the compiler will stop and tell you that you can't assign to a constant.
As to your bigger problem, a beginning micro class where the professor is either unaware of, or choosing to ignore your lack of prior programming skills, you really do need to sit down with him/her and sort out a plan. Further, in most institutions, the course catalog and syllabus are the "contract" regarding requirements for a course.  If your instructor is basically running a course that does not adhere to the "contract" you might have grounds to have a more assertive conversation - though that may have unwanted consequences. 
Ultimately, you are at such a tremendous disadvantage if the course continues as you've described, your best bet may be to cut your losses and postpone the course.
FWIW, in real life I'm an asst. professor of nursing in an accelerated program, so I see the "deer in the headlights" look with some frequency.  You have to decide how best to handle your situation, whether it's a quick exit, or planning to do a long stretch of 20-hr days.  If you decide to proceed, find the smartest, sympathetic classmate to buddy-up with.  My nursing students employ that technique on a regular basis, and it is a strategy with a high success rate.
Best of luck!
Bob

I like the boosterPack concept, but for my current project I needed access to all the pins on an F5529 as well as an F2013.  So, I constructed a couple of boards to plug into an MSP-TS430PN80USB in a boosterpack fashion. As is  probably obvious, I missed a couple of traces (GND lines), for which I had to add the little green wires. The top board has all my sensors, and the bottom is basically battery management and a sx1509 port expander to manage a number of LEDs.  I don't actually need the extra ports, but I wanted the sx1509's built-in LED "breathe" capability. Saves coding... -lazy programmer
I was a happy camper when I fired-up the system and was able to access and program both MCUs.
I've found that I can choose between running two instances of IAR (or CCS) and debug both micros simulaneously.  Handy for the comms and interrupt handing.
So, let the fun begin...
 
BTW - the TFT LCD is from buydisplay.com - 2.8" TFT with Cap touch (about $15.00 U.S.).  It's using the ILI9341 controller for the LCD and the FT6206 controller for the cap touch.  For proof of concept I was able to use the Adafruit sketches to connect with both, and the edits were limited to pin assignments, if I remember correctly.

I've never had issues with a similarly looking power bank.
 
Haven't tried it in real low power scenarios, but it was happy to feed my AIS receiver at 17mA all day long.

I think we're currently in the AOL and CompuServe stage of IoT. Here's hope that there's an equivalent of Tim Berners-Lee out there who will invent an open and simple but good-enough way to integrate all these devices.
 
There will always be the Facebooks and Apples that try to capture their users in a closed system, but eventually the system that gives customers the right balance of simplicity and interoperability will dominate. Think HTML and REST over HTTP vs. Corba, J2EE, SOAP and many other dead sophisticated technologies that were supposed to take over the computer-to-computer communication.
 
On the "widget tied to cloud services" tangent: Today, most hardware startups are pressured by their VCs to come up with a business model with recurring revenue. See the many blog posts about hardware business on Bolt.io to get a taste of it, e.g. this one.
 
I doubt that this model is sustainable in the long run for applications where there's no real benefit for the customer to be tied to a vendor's internet service (locks, lights, litter box, fridge, ...). Having to develop and sustain an internet service adds a significant complexity, cost and time-to-market handicap. There will be hardware companies that copy the good idea (automated odor control for the litter box) without the baggage (vendor lock-in for refills, stink when the internet is down, ..), and probably they will be able to sell it to you for less money.

I think we're currently in the AOL and CompuServe stage of IoT. Here's hope that there's an equivalent of Tim Berners-Lee out there who will invent an open and simple but good-enough way to integrate all these devices.
 
There will always be the Facebooks and Apples that try to capture their users in a closed system, but eventually the system that gives customers the right balance of simplicity and interoperability will dominate. Think HTML and REST over HTTP vs. Corba, J2EE, SOAP and many other dead sophisticated technologies that were supposed to take over the computer-to-computer communication.
 
On the "widget tied to cloud services" tangent: Today, most hardware startups are pressured by their VCs to come up with a business model with recurring revenue. See the many blog posts about hardware business on Bolt.io to get a taste of it, e.g. this one.
 
I doubt that this model is sustainable in the long run for applications where there's no real benefit for the customer to be tied to a vendor's internet service (locks, lights, litter box, fridge, ...). Having to develop and sustain an internet service adds a significant complexity, cost and time-to-market handicap. There will be hardware companies that copy the good idea (automated odor control for the litter box) without the baggage (vendor lock-in for refills, stink when the internet is down, ..), and probably they will be able to sell it to you for less money.

I think we're currently in the AOL and CompuServe stage of IoT. Here's hope that there's an equivalent of Tim Berners-Lee out there who will invent an open and simple but good-enough way to integrate all these devices.
 
There will always be the Facebooks and Apples that try to capture their users in a closed system, but eventually the system that gives customers the right balance of simplicity and interoperability will dominate. Think HTML and REST over HTTP vs. Corba, J2EE, SOAP and many other dead sophisticated technologies that were supposed to take over the computer-to-computer communication.
 
On the "widget tied to cloud services" tangent: Today, most hardware startups are pressured by their VCs to come up with a business model with recurring revenue. See the many blog posts about hardware business on Bolt.io to get a taste of it, e.g. this one.
 
I doubt that this model is sustainable in the long run for applications where there's no real benefit for the customer to be tied to a vendor's internet service (locks, lights, litter box, fridge, ...). Having to develop and sustain an internet service adds a significant complexity, cost and time-to-market handicap. There will be hardware companies that copy the good idea (automated odor control for the litter box) without the baggage (vendor lock-in for refills, stink when the internet is down, ..), and probably they will be able to sell it to you for less money.

I think we're currently in the AOL and CompuServe stage of IoT. Here's hope that there's an equivalent of Tim Berners-Lee out there who will invent an open and simple but good-enough way to integrate all these devices.
 
There will always be the Facebooks and Apples that try to capture their users in a closed system, but eventually the system that gives customers the right balance of simplicity and interoperability will dominate. Think HTML and REST over HTTP vs. Corba, J2EE, SOAP and many other dead sophisticated technologies that were supposed to take over the computer-to-computer communication.
 
On the "widget tied to cloud services" tangent: Today, most hardware startups are pressured by their VCs to come up with a business model with recurring revenue. See the many blog posts about hardware business on Bolt.io to get a taste of it, e.g. this one.
 
I doubt that this model is sustainable in the long run for applications where there's no real benefit for the customer to be tied to a vendor's internet service (locks, lights, litter box, fridge, ...). Having to develop and sustain an internet service adds a significant complexity, cost and time-to-market handicap. There will be hardware companies that copy the good idea (automated odor control for the litter box) without the baggage (vendor lock-in for refills, stink when the internet is down, ..), and probably they will be able to sell it to you for less money.

Here's a MSP430F413 in a cheap (< US$100) radar speed gun

http://www.allaboutcircuits.com/news/teardown-tuesday-radar-gun/
 
I'm surprised how little analog and digital processing there is in this product.. I guess all the RF magic happens inside the transceiver module (which is available at Mouser for $50).

Here's a MSP430F413 in a cheap (< US$100) radar speed gun

http://www.allaboutcircuits.com/news/teardown-tuesday-radar-gun/
 
I'm surprised how little analog and digital processing there is in this product.. I guess all the RF magic happens inside the transceiver module (which is available at Mouser for $50).

I've been playing with Adafruit's ADXL345 accelerometer BOB and was able to import and run the Adafruit library code without any edits.
Sweet...
 

Tindie business slowed down considerably over the last two months. Not sure yet if it's the cheap competition that started showing up, or whether everyone's just out sailing.
 
Anyways, the upside is, that I finally have some time to tinker on new things again..

 
Love the new steel stencils from OSH Stencils. I managed to reflow 4 boards without a single bridge, including the big QFN which gave me a lot of grief in the past. Maybe it's the combination with OSH Park PCBs instead of the cheap Chinese ones. Also OSH Park turned around my last few orders in two weeks from ordering to receiving the boards in my mailbox. I seem to remember that this was closer to three weeks in the past. 

Tindie business slowed down considerably over the last two months. Not sure yet if it's the cheap competition that started showing up, or whether everyone's just out sailing.
 
Anyways, the upside is, that I finally have some time to tinker on new things again..

 
Love the new steel stencils from OSH Stencils. I managed to reflow 4 boards without a single bridge, including the big QFN which gave me a lot of grief in the past. Maybe it's the combination with OSH Park PCBs instead of the cheap Chinese ones. Also OSH Park turned around my last few orders in two weeks from ordering to receiving the boards in my mailbox. I seem to remember that this was closer to three weeks in the past. 

I get it from some LCD manufacture at their retail store on taobao
Takes quite some time to find
https://item.taobao.com/item.htm?spm=a1z09.2.0.0.1bs8wy&id=14933583467&_u=j1f5oh4m0dc1
 
 
@@chicken that might be the problem, I've measured current consumption every time I put new part on,
MSP430FR4133 (@LPM3) 1.1uA => SHT21 2uA => BMP180 2.3uA => OPT3002 2.3uA
 
So maybe I'll measure nRF alone to see if it is the problem,
also note that I've seen a strange current curve after transmit

seems to charging some thing, but not sure what happen there.
that also damage the battery quite a lot.

Hi everyone, this is my credit card size wireless sensor node,
with a 7-seg LCD display showing temperature & humidity, update every second.
using MSP430FR4133 with HDC1080,BMP180 and OPT3002, 
transmit by nRF24l01, which sends out temp,humid,pressure,luminosity and also battery voltage per minute.
 

 
It is all power by a CR2032, and thanks to MSP430FR4133, I can manage to have half an year battery life.

also thanks to MSP430RF4133 Launchpad with build-in energyTrace, I can estimate battery life with a click(no more oscilloscope  )

note that I've actually put an RF430 on the down left ot the board(there is an antenna for that),
which will act as a NFC tag, but it draws too much current (~15uA), so I took it off
and at the down right is the battery voltage measurement with a mosfet to cut the power,
but I found out that I can just measure internal voltage reference to calculate its supply voltage, so I've also remove that. 

 
although I'm pretty much satisfy with this power consumption, but I still think that 16.5uA is a little bit too far from estimating from datasheet
and I am still trying to figure that out

Re dual output: use Digikey's parametric search.
http://www.digikey.com/product-search/en/integrated-circuits-ics/pmic-voltage-regulators-linear/2556290?k=&pkeyword=&FV=fff40027%2Cfff80182%2Cc0007c&mnonly=0&newproducts=0&ColumnSort=0&page=1&stock=1&quantity=0&ptm=0&fid=0&pageSize=25

Yeah, just let me rearrange the chairs to make some space on my patio.

Yeah, just let me rearrange the chairs to make some space on my patio.

Yeah, just let me rearrange the chairs to make some space on my patio.

Thanks, But don't be fooled. My setup takes quite awhile to setup. And I'm still learning all the time, The first pass I made on this cutout skipped steps somehow, ruining this enclosure.
I'd love to own some better tools But I'm going to make use of what I have right now.
 
But I took the opportunity to try some cool stuff. (note the mis-aligned cutouts at the bottom and the duplicates on the far side.)

 
Infill on my engravings and engraved pixel fonts!

 
Getting the hang of F360, slowly.


 
Working on some custom parts now. Using a molding technique using milled ren-shape, silicone and polyurethane.
Mold model

 
Blank ren-shape

 
Mid milling

@ Rei Vilo, Thanks for the info.
 
There is a workaround for this problem:
 
http://seeed.cc/Grove-Base-BoosterPack-%26amp%3B-Launchpad-not-working-together-t-5980.html