Blog Post Actions
Group Actions
Engagement
  • Author Author: jomoenginer
  • Date Created: Date Created
  • Views 179 views
  • Likes 5 likes
  • Comments 4 comments
Related
Recommended

Safe and Sound Wearables- Hearing Guard System #15: Final Post - Incomplete

jomoenginer

Well, the deadline to submit is here and I suppose I need to get something posted.  

 

I've been stuck in CCS Hell and got stuck trying to tie together my Menu implementation that was written in GNU C++ with the other projects such the BLE and Wi-Fi MQTT project but have had no success.  I've spent many a sleepless night trying to resolve compiler errors as well resolve the differences in function and variable naming that is used between different versions of TI-RTOS as well as the SimpleLink SDKs but just ran out of time.  I had to grossly simplify my project just to get something to work, although not with the functionality I was hoping for.  I had to make a decision last week to step back from my initial design and just go with a more similar approach but I just ran out of time to get the things I wanted to work.  The MQTT and the Java Script code is relatively the same as I had previously posted, so no use in posted that again. 

As far as creating cases for the devices, I bought a 3-d printer but got caught up in the Compiler issues and haven't even unboxed it yet. 

 

So to just get some up by the deadline, this is what I have.  I'm not sure why the ADC values keep popping up, but I guess I need to learn more about how BIOS is keeping track of Tasks and semaphores.

 

Here is my sad result of months of work.

 

Anonymous
  • in reply to DAB

    I have learned a lot and did resolved some issues even with the supplied example code which I passed to TI.   However, I do still have a couple outstanding issues that I have posted at the TI E2E forum and am still waiting for a reply from them. 

     

    Troubleshooting technical issues has been my main job function at the various positions I have held for over 20 years, so I am accustomed to that.  I just got tied up in trying to resolve issues I ran into until it was too late.  I should have pulled the plug a couple of weeks ago and just went with a simpler approach.   Live and learn.

  • in reply to dougw

    Yeah, in hindsight I would have been better off just prototyping what I wanted in Energia and then port that over to CCS and TI-RTOS.  I have resolved some of the issues I was running into and was still fighting with so I will post an update.  I just seen the deadline approaching and wanted to get something posted.

  • Hi John,

     

    Finding issues with the technology is one of the objectives of the challenge.

     

    As the old saying goes "If it was easy, everyone would do it!"

     

    Still I do greatly sympathize with your problems.  Getting sidetracked by a piece of "off the shelf" software is something every engineer experiences.

     

    Reminds of the time they sent me down to Huntsville, Alabama because the project team was stumped trying to run a piece of software to decode some data.

     

    I flew down, met the team and started listening to what they had and what they were doing.  I immediately recognized that the data was in 2's complement form, at which the lead programmer did a face plant, rushed to his computer, added a few lines of code and the problem was solved.  Took me all of about twenty minutes.

     

    Sometimes, you just need a fresh pair of eyes looking at the problem.

     

    DAB

  • You ran smack into my biggest fear: "issues with software I didn't write". You end up spending all your time trying to figure out what they did or didn't do and don't have any time left to do what you wanted to do. It is especially risky with new products and new applications where there aren't a lot of others to learn from. It is good to see you sticking with it all the way to the end. It says a lot about your character.