Forum Rule: Always post complete source code & details to reproduce any issue!
Page 3 of 3 FirstFirst 1 2 3
Results 51 to 60 of 60

Thread: Teensy 3.1 & Teensyduino 1.17 Released

  1. #51
    Senior Member
    Join Date
    Jun 2013
    Location
    So. Calif
    Posts
    2,828
    re "Yesterday and today though Norton started to block downloads, so you probably need to look at this."
    Long ago I switched to Microsoft Security Essentials (MSE) for security software. Free. Good. Unobtrusive.
    I rationalize that MS has at least as much, or more, incentive to protect Win 7 for me than do Norton $ or McAffe $ et al.

  2. #52
    Senior Member Jp3141's Avatar
    Join Date
    Nov 2012
    Posts
    458
    On my Mac, I have two user accounts (say 'home' and 'work'). While logged in as 'work', Teensyduino wouldn't install (error like 'teensyduino error unable to write file contents/resources)'. It turns out that I must have installed Arduino as 'home' and when I switched to that user, it installed fine.

    Is that expected ? Are the Arduino files 'owned' by one user ?

  3. #53
    Senior Member
    Join Date
    Nov 2012
    Location
    Boston, MA, USA
    Posts
    1,108
    Quote Originally Posted by ChrisH View Post
    Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.
    Yes, the Teesyduino modifies executable files. That means Norton "guesses" it might be a virus. It isn't.

  4. #54
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,574
    The Windows and Linux installers are compressed with UPX.

    http://upx.sourceforge.net/

    Apparently Norton and others occasionally mistake the UPX self-decompression for malware.

    Of course, Nantonos is absolutely correct, anti-virus heuristics assume no program should ever modify another program, but that's exactly what the Teensyduino installer does as it adds Teensy support into Arduino.

    The installer never uses network connections, so you can disconnect from the internet, and temporarily disable anti-virus while running the installer. Be sure to turn your protection back on before you plug back into the network.

  5. #55
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,574
    You could also report this to Norton....

    https://submit.symantec.com/false_positive/

  6. #56
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,256
    Paul, I happened to notice that in the summary of features page: http://www.pjrc.com/teensy/index.html, Teensy 3.1 only lists 1 I2C device, instead of 2.

  7. #57
    Junior Member
    Join Date
    Dec 2013
    Posts
    10
    Quote Originally Posted by PaulStoffregen View Post
    Yes, 4000 RGB LEDs.

    The 1000 recommendation was based on allocating at least the 3K frame buffer in the lower 8K of memory on Teensy 3.0. That lower half of the RAM is optimized for DMA, with a separate bus. The USB stack also allocates about 3K of buffers in the lower half. The upper half contains the stack holding local variables, function return addresses, and interrupt context. RAM size was the limiting factor.

    Teensy 3.1 has 64K of RAM. The lower half is now 32K, with the USB stack leaving about 29K free. Both the frame buffer and drawing buffer can easily fit in the lower half of RAM.

    4000 LEDs means about 500 on each pin. 500 LEDs at 30 us each will make the update time approx 15 ms, which gets pretty close to the limit for achieving 60 Hz progress refresh. You might be able to use 8000 if 30 Hz refresh is ok. That would allocate 48K of RAM for the 2 buffers, so I would definitely not try to push much farther than 8000. If you do connect so many to one Teensy 3.1, please post photos!!!
    That is awesome news! The 30hz refresh rate is even probably faster then really needed for this purpose. The leds are on a robotic performers suit and are running animations based on live music being played. The original suits I made for personal use utilized a few teensy 2.0 boards linked together just to get a 1000 rgb leds working together. Being able to push the teensy 3.0 to 4000-8000 rgb leds makes the task of putting 20,000 on a single suit Sooooooo much easier. Here's some links to some of the original suit parts running on Teensy 2.0 and using fft to generate effects on the leds. The new suits will be traveling around the world and being seen by thousands of people 3 nights a week starting early part of 2014. I Would have never gotten the chance to do this without the help of these amazing little micros!

    LED Suit being controlled by an old school nes powerglove connected to a teensy 2.0
    https://www.youtube.com/watch?v=gvFR...e_gdata_player

    Teensy 2.0 with audio input mic using fft to generate led visuals in real time
    https://www.youtube.com/watch?v=uLKN...e_gdata_player

    Matching helmet running modified adafruit led effects on Teensy 2.0
    https://www.youtube.com/watch?v=WaZp...e_gdata_player

    And lastly... Demo of ability to use led finger gloves and rods to generate patterns using POV during live performance. (being done on a teensy 2.0 of course)
    https://www.youtube.com/watch?v=Nbwo...e_gdata_player

  8. #58
    Junior Member
    Join Date
    Feb 2014
    Posts
    16
    I just wanted to say THANK YOU!
    Teensy 3.1 is what I was waiting for!!

  9. #59
    Junior Member
    Join Date
    Jan 2014
    Posts
    3
    When will Teensyduino support the programming of the lock bits in order to prevent read out from the flash program memory?

  10. #60
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,574
    Quote Originally Posted by MichaelMeissner View Post
    in the summary of features page: http://www.pjrc.com/teensy/index.html, Teensy 3.1 only lists 1 I2C device, instead of 2.
    Opps. It's updated now. Thanks!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •