Jump to content
43oh

spirilis

Members
  • Content Count

    3,394
  • Joined

  • Last visited

  • Days Won

    146

Everything posted by spirilis

  1. There ya go @@bluehash - 1st link showed up right, and links #2, 3 and 4 showed up "unclickable" to me in an off-cyan color. Pic from my browser:
  2. Testing another one: http://www.mouser.com/ProductDetail/Amphenol-Commercial-Products/U77-A1114-100T/?qs=sGAEpiMZZMtLo%252bUrTGGA8Qu%252bjOiyxwrr - blah blah blah - http://www.ti.com/product/ds90lv011a - what about blah blah - http://www.ti.com/product/ds90lv012a and https://en.wikipedia.org/wiki/Small_form-factor_pluggable_transceiver
  3. Looking up the datasheet for some of the SFP's I have laying around (potentially bad)- https://www.finisar.com/sites/default/files/downloads/finisar_ftlf8524p2xny_4.25gbs_rohs_compliant_short-wavelength_sfp_transceiver_product_specification_1.pdf Finisar FTLF8524P2BNV (from a 4Gbps Brocade ED-48000 fiberchannel switch) Sounds like there are different speed-related modes that are switchable via I2C (OR a GPIO toggle) but there is no "Min" in the bitrate...
  4. Noticed on http://forum.43oh.com/topic/8844-questions-on-sfp-transceivers-in-hobbyist-projects/?p=73885 - no matter what I do, the 2nd link won't show up as a clickable hyperlink, not even if I edit the post and use the "link" button in the editor to compose it as such.
  5. I see SFP cage slots aren't hideous - http://www.mouser.com/ProductDetail/Amphenol-Commercial-Products/U77-A1114-100T/?qs=sGAEpiMZZMtLo%252bUrTGGA8Qu%252bjOiyxwrr - and the edge connectors - http://www.mouser.com/ProductDetail/Amphenol-Commercial-Products/UE75A206000T/?qs=sGAEpiMZZMvlX3nhDDO4ADdPO33nqrQcj0jVg%252b39E7Q%3d - also not too expensive. Damn. I might have to get this rolling soon.
  6. Lol... Decided to take another look at this thread, as my boss and I were chatting about how many (potentially bad) SFPs we have laying around the office. So if I'm not mistaken, the SFP has an LVDS interface for the TX and RX side, and you just need an LVDS interface - something like http://www.ti.com/product/ds90lv011a (TX) and http://www.ti.com/product/ds90lv012a (RX) for example (a 400Mbps PHY available for ~$1 at mouser in single qty) - and boom, an LVDS interface you make? Per https://en.wikipedia.org/wiki/Small_form-factor_pluggable_transceiver - there are lines to disable TX, s
  7. Yeah all those sort of REST APIs require an authentication token in the headers. Look more into AWS documentation for this. It might be a key you get from their dashboard GUI for your account.
  8. spirilis

    I

    Yeah my memory is rusty but from past deconstruction and reconstruction of the Energia Wire framework, what you're trying to do isn't possible since the handling of the reads happens within the ISR. Obviously this is the case since there is no specific method within Wire to "end" the transfer, i.e. requestFrom is sufficient all by itself to execute the read operation, and it takes an upfront count argument for how many bytes to read, so it must handle the entire transfer from start to stop by itself, putting it in a temporary buffer that you read when you use Wire.read()
  9. I just sold my old '06 Yamaha Majesty (big scooter) with 34K. I bought it new and rode it a fair amount to work... not too many pleasure trips unfortunately. 175K is Holy Shit!!!!!
  10. I suspect the XDS110's use of SWD (2-wire JTAG) over 4-wire JTAG may play a part. Stellaris/Tiva ICDI is 4W.
  11. A 0.8mm pitch TQFP is crazy easy to solder for those who are just getting into surface mount (SMD) soldering. MSP430 doesn't come in any packages like that fwiw, usually 0.65mm (TSSOP) or 0.5mm (QFN) although there is an MSP430F5172 available in BGA (although pretty fine-pitch I think, called dsBGA) .... but Energia doesn't support that chip.
  12. Yeah it uses an FLL I think to 16x a 16MHz DCO.
  13. Then there's the C2000, a niche-y MCU though, but it has an HRPWM peripheral that can subdivide its 80MHz (or 60, can't recall) PWM clock by 32 for resolution sake.
  14. It's not supported by Energia but there is an MSP430 (F5172) that can pull off a 256MHz timer which can give you awesome resolution at fairly high PWM periods.
  15. It is typically the case that your ISRs set a "signal semaphore" (global "volatile boolean" variable) and the main loop does the remaining processing. Not all that hard to do with a while() loop as your make-shift "scheduler" - or just the loop() function in Energia's case. There would be a set of conditions at the beginning of loop() that would determine whether it's safe to enter sleep() mode or whatever, and if any of those failed it would go through and check each one and run the handler.
  16. Yes the main problem is the I/O pins on most digital devices have ESD protection (electrostatic discharge) which is intended to "drain off" excess voltage above Vcc or below GND into the Vcc or GND planes where it can hopefully get absorbed by capacitors or shunted through the GND plane or whatever.... but those basically involve a pair of diodes reverse-biased. (wish I had a pic handy, too lazy to find one) edit: The problem happens when you apply a legitimate (3.3V we'll say) signal to the I/O pin of a device whose Vcc is at GND potential (i.e. it's powered down). The protection diod
  17. Yeah doing UART TX is not recommended while inside an ISR for the reasons discovered. Beware potential pitfalls from nesting interrupts (setting GIE inside ISRs). Btw it's standard MSP430 hardware behavior to keep GIE cleared by default in ISR context.
  18. Oh yeah duh... I was thinking microseconds Same problem anyhow.
  19. I guess one problem is, the precision... only 1/32768 of a second, and the math if you need absolute milliseconds. 1/32768 = .00003051757812500000 or basically 30.517578125 ms.
  20. IIRC, it does, but only under sleep() and sleepSeconds() mode. Higher resolution is available via DCO which is why it uses it. Just not necessarily the best accuracy I guess...
  21. That is true, millis only updates when the ISR fires, so your sketch may be pulling the millis value some time "after" the last tick. For the purpose of getting a super-accurate clock, I would look into making your "own" millis-style API using one of the Timer_A peripherals and include a direct-read of the TAxR register to compensate for between-ISR timing. You should have free access to declare one of the Timer_A interrupt vector entries in your own sketch without Energia getting in the way. Just be sure you're not using a PWM output pin that happens to use that same Timer_A instance or
  22. Not too terribly accurate as you've found. It would require modifying the Energia core quite a bit to change millis() as it uses the Watchdog timer. Jitter and drift will be caused by the main oscillator (DCO) mostly. It's not known to be all that accurate but can be trimmed. At least with the F5529 there is an FLL driven by the 32.768KHz XTAL to auto-trim it.
  23. Yeah Go really goes about it a bit differently, the "implicitly satisfied interfaces" becomes your rough method of inheritance and class-ishness I guess. It's working well enough for me so far.
  24. What kind of errors? I have Windows 10 Professional (laptop came with it preinstalled though) and no problems, but I will note I made sure to install all the TI drivers in signature-ignore mode (i.e. hold Shift while clicking the Restart menu option under Start>Power, select reboot to options menu, select option 7 after the reboot for booting with no driver signature verification, then install drivers in that special mode). I did the same thing when I installed CCSv6 too.
×
×
  • Create New...