Jump to content
43oh

spirilis

Members
  • Content Count

    3,394
  • Joined

  • Last visited

  • Days Won

    146

Everything posted by spirilis

  1. Yes and progressing from having a non-prioritized, finite-time-slice scheduler to a "priority" scheduler in lab 4 illustrates the "why" behind a lot of what modern priority-based RTOS's are about...
  2. My current projects have all used TI-RTOS since the platform basically requires it and/or is unsupported without it (CC1310), so the course has been mostly educational experience, however, I will pay closer attention to the Clock module and use of hardware timer interrupts for clocking any hard-real-time stuff from now on. The practical advice on handling DSP process flow was useful and I can see that coming into play, the PID stuff too. I think the use of some sort of tick or GPIO toggle to indicate task switching/execution bears serious consideration -- if TI-RTOS has a "hook" you can exec
  3. One of the cooler things about the course is the casual introduction to various use-cases, section 4.1 particularly. 4.1.4, "Real-Time Control Systems" had one of the best descriptions of PID control that I've seen as it involved both practical descriptions and math--including casual mention of such scary terms as "Lorenz transforms" (which I still don't understand) but no requirement that you truly grok them, as the page included very practical advice on what the P/I/D segments do. The 4.1 subsections prior talk about DSP and introduce the MACQ, or Multiple Access Circular Queue, alon
  4. Both, although some of the videos I might skim the text interpretation and then skim the content after... all depends. Excited for lab 4, we get to run a game!!
  5. Yeah in your scenario I think using I2C for this purpose is fine. Probably makes sense to have a GPIO on the F2013 signal to the F5529 that it has SD16_A data to report (as a matter of flow-control).
  6. I2C is pretty awkward to implement (performs well enough but, you're managing a hardware state machine). Pretty much requires an ISR, although @@Rei Vilo did write a software master-only I2C library that's included in Energia these days.
  7. I'm doing Lab #2 right now, which is where you write your first RTOS scheduler and make the whole time-slicing scheduled thread concept work for the first time... and I just want to add, this is a ton of fun!!! Class is taking more time to go through than I thought it would, mostly the lectures, but I'm making time for it here and there. There are 6 sections to the class and only 1-5 are up right now, #6 I think is the actual communication with the CC2650 Bluetooth Low Energy coprocessor (where you use either the TI CC2650 BoosterPack or the CC2650 LaunchPad in boosterpack mode). The bul
  8. Well that was nice, someone called me back and gave me a 10% off code for the inconvenience and his email in case I have any more issues. So at least they're good about turning around the customer service communication.
  9. I had a somewhat lousy experience with Arrow during the RPi3 promo; while I ended up getting all my goods (although the Pi T-Cobbler adapter I bought evidently was the wrong kind, which wasn't obvious on their site at the time), they shipped it in 4 separate shipments that appeared to come from the same location, thus inflating the shipping costs. I went along with it anyhow (as the total shipping cost at $16 was still less than a Pi3) thinking they just source from lots of locations but that was not the case. For kicks, I decided to try the free shipping today (since it's the last day fo
  10. Looks like the XMS rev C is a minor pre-production release, whose differences from production are: http://www.ti.com/lit/an/slaz691a/slaz691a.pdf
  11. Nevermind it's just what bluehash's message said, they're restricting it. My email domain ends with .net so that must flag TI's order system from allowing me to sample for free. I remember this change occurred when the TI store started selling individual chips and the free shipping disappeared...
  12. Well come to think of it, IIRC, TI did do a swapout for the FR5969 launchpads when the old ones were no longer supported, maybe something like that is TBD...
  13. I thought they weren't doing samples anymore...
  14. I think it would be nice if TI could provide free MSP432P401R production silicon samples for folks who bought a black LaunchPad and want to try replacing the chip. Not everyone's got the tools but many of us probably do...
  15. nice! Those FCC certified modules make things convenient. They started with the CC3100MOD a while back and now they have the CC2650MOD. I vaguely recall Trey German using that CC2650MOD (I think, or something like it?) in his upcoming product he's making (now that he's not working @ TI any longer)...
  16. haha wow, only issue may be the MSP432 red LaunchPad is currently out of stock:
  17. I think having specific support on the board for "daughterboards" providing advanced power support is a great idea. A pinout giving access to 5V, GND, maybe 3.3V, and I2C along with perhaps a GPIO or 2 (maybe for the circuitry to "interrupt" the Sitara without requiring I2C polling?)
  18. I never bothered to follow up with my idea below but I do think a switching regulator for 12V (maybe modifiable to work up to 60Vin for flexibility with different offgrid DC power systems) is a good idea. I designed and built one copy of a 12VDC PFET power MOSFET cape which had an off-the-shelf 12V (7-36Vin) to 5V out switcher onboard. It worked great. I highly recommend including one for your design. The idea behind my cape is 12V could be switched on/off to up to four outputs for remotely controlling power for various sub-5A sources e.g. a low flow pump. The beaglebone is powered
  19. Just got my RPi3 and had a chance to play with it today. Stupidly simple to set up... a simple uncommenting of lines in /boot/config.txt to enable SPI, I2C, I2S etc. The bcm2835 library seems to support hitting SPI et al from C easily enough. http://www.airspayce.com/mikem/bcm2835/ So it's easy to get started with and stupidly simple for any reasonably experienced Linux admin to use. The current Raspbian doesn't support the ARM Cortex-A53's 64-bit mode yet, so it runs in armv7l 32-bit mode, but it's still quad-core. Looks like the RPi foundation supports the GPGPU project for writi
  20. hahahaha, thank you for putting the right phrase to this feeling (never could put a good phrase to that...)
  21. That might be TI's way of admitting that the money they spent on the msp430-elf-gcc port was an epic waste, so they should just give away the TI MSP430 compiler for free (like they already do with the TI optimizing ARM compiler) and get it overwith.
  22. Sounds like a level shifter, like a TXB0102 or similar? I've had some experience with those. Yeah the whole idea is A1 & B1 talk together, A2 & B2 talk together. If it's a bidirectional "sensing" type of chip like the TXB, on top of that you have to acknowledge that the drive strength on the outputs are limited, e.g. they don't recommend using pullups or pulldowns lower than 50K ohms in value on any of the pins intended to receive output from one of the channels... Where I've used the TXB is to power down the A-side voltage (on the TXB at least, VccA must be <= VccB, also the
  23. Actually another idea could be to use SPI, transmitting debug info over SPI would be loads quicker than Serial UART and you could get full bytes of information sent that way. Pick it up with the logic analyzer and use the protocol decode feature in the software.
×
×
  • Create New...