Jump to content

Search the Community

Showing results for tags 'TIVA'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Sparkfun


Github

Found 56 results

  1. Hi, Is there a library available for Exosite and TIVA launchpad in Energia, similar to the qs_iot sample used in CCS IDE? Thanks, TVG
  2. Pardon folks, Right now I'm working on a project that requires aid from tiva's hardware timers for me to schedule everything properly. For this, I imported some of tivaware's API library in to manipulate them. Everything works more or less fine until I have to import energia.h into this little library I've written, and then suddenly I encounter a large amount of errors involving objects and types in energia/bin not being recognized by the compiler. Some samples below: /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:259:8: error: 'uint64_t' does not name a type /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:260:27: error: variable or field 'TimerMatchSet' declared void /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:260:27: error: 'uint32_t' was not declared in this scope /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:260:46: error: 'uint32_t' was not declared in this scope /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:261:27: error: 'uint32_t' was not declared in this scope /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:262:8: error: 'uint32_t' does not name a type /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:263:29: error: variable or field 'TimerMatchSet64' declared void /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:263:29: error: 'uint32_t' was not declared in this scope /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:263:48: error: 'uint64_t' was not declared in this scope /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:264:8: error: 'uint64_t' does not name a type /home/mrdtdev/Bin/Energia/energia-0101E0016/hardware/lm4f/cores/lm4f/driverlib/timer.h:265:30: error: variable or field 'TimerIntRegister' declared void Does anyone have any ideas to get me started on debugging this? I usually use CCS and have recently started experimenting with Energia, so this software's quirks and details are something I am not generally aware of.
  3. Good morning. I have a DS3231 and I want do hibernate Tiva C and wake up It with the rtc alarm. I did the alarm configuration, but, I couldn't configurate the hibernation module using Energia IDE. The microcontroller will has some sensors and sd card. So, It has a cycle: wake up (with rtc alarm) > read the sensors > write the data > hibernate ^------------------------------------------------------------------------------
  4. Got an email today about a new LaunchPad supporting hardware cryptography - mainly aimed at supporting HTTPS for your IoT projects. Promo pricing $16.99, normally $24.99. http://www.ti.com/tool/ek-tm4c129exl
  5. Hi Everyone, I have made available binaries and source code for an RGB lighting project called LightServer that I thought some of you would be interested in. The best way to see what you can do with LightServer is to view the videos on Vimeo here - https://vimeo.com/album/3015956 No coding experience required to set this up and use. Technical Details LightServer uses the Tiva C LaunchPad and the CC3100 Wi-Fi BoosterPack and a custom BoosterPack (Eagle files included
  6. Jrojas28

    SDCard Library (Tiva C Series)

    Hello, I've been looking trough the forums for an SD Card Library that can be used on TM4C123GH6PM micro controller. I came across one (http://embeddedcomputing.weebly.com/microsd-card-boosterpack.html) but the link redirects to the forum main page, so I can't really get my hands on it. Does someone has a low resource library for this? Thanks! Note: In case this is good to know, I'm looking to use the SD Card slot that comes with the ILI9341 2.2" LCD screen sold (mostly) on Ebay. So we're talking about an SPI-Interfaced SD Card.
  7. RobG

    TLC5940 driver for Tiva

    TLC5940 driver for Tiva / Stellaris. Uses 2 Timers, SSI, and DMA. SPI runs @ 20MHz, GSCLK @ 8MHz, update occurs every ~0.5ms Up to 16 TLC5940s can be daisy chained (in theory, I tested only 2.) main.cstartup_ccs.c
  8. Hi, I'm getting to grips with a Launchpad ek-tmc123gxl board, and so far it looks amazing. However I have hit a snag which is pretty painful. Consider the following code: #include <stdbool.h> #include <stdint.h> #include "inc/hw_gpio.h" #include "inc/hw_memmap.h" #include "inc/hw_sysctl.h" #include "inc/hw_types.h" #include "driverlib/gpio.h" #include "driverlib/pin_map.h" #include "driverlib/rom.h" #include "driverlib/rom_map.h" #include "driverlib/sysctl.h" void setup(void); #define delay(x) SysCtlDelay((SysCtlClockGet() / 3000000) * x) uint8_t sequence_1[16] = { 0x4b, 0x4e, 0xcd, ... other 8-bit values }; uint8_t sequence_2[16] = { ... another list of 16 8-bit values like sequence_2 }; int index; int main() { int i, wait; setup(); index = 0; wait = 1000; while(1) { delay(wait); GPIOPinWrite(GPIO_PORTB_AHB_BASE, 0xFF, seq_m1[index]); GPIOPinWrite(GPIO_PORTD_AHB_BASE, 0xFF, seq_m2[index]); if(++index == 16) index = 0; } void setup(void) { // Set the clocking to run directly from the PLL at 80 MHz. SysCtlClockSet(SYSCTL_SYSDIV_2_5 | SYSCTL_USE_PLL | SYSCTL_XTAL_16MHZ | SYSCTL_OSC_MAIN); SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB); SysCtlGPIOAHBEnable(SYSCTL_PERIPH_GPIOB); SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOD); SysCtlGPIOAHBEnable(SYSCTL_PERIPH_GPIOD); GPIOPinTypeGPIOOutput(GPIO_PORTB_AHB_BASE, 0xFF); GPIOPadConfigSet(GPIO_PORTB_AHB_BASE, 0xFF, GPIO_STRENGTH_8MA, GPIO_PIN_TYPE_STD); GPIOPinTypeGPIOOutput(GPIO_PORTD_AHB_BASE, 0xFF); GPIOPadConfigSet(GPIO_PORTD_AHB_BASE, 0xFF, GPIO_STRENGTH_8MA, GPIO_PIN_TYPE_STD); } I am seeing how pins D0 and D1 and B6 and B7 show the following scope trace: Where a normal binary squarish wave should be seen, I'm getting two high states, one at 1.85 V and another at the nominal 3.3 (!). I provide the facts below for context: The Launchpad board is brand-new. This behavior is also what I get when using an equivalent Energia sketch. None of the Port B or D pins are connected to anything. Just to the scope probes. This code is compiled on CCSv6 and arm-gcc. Same behavior. The usage of the AHB was just a "what if..." decision. The behavior is just as present when using the default APB. I suppose I'm missing a very big catch in dealing with the ports, but I thought the TivaWare drivers were written precisely to avoid this sort of unexpected and annoying behavior? As a more basic test, I made a program that toggles all bits of Ports B and D after a 2 ms delay. In that case, the scope showed a clean square wave. The ports configuration is identical to what I showed above. Thanks for the attention!
  9. OzGrant

    Tiva Low Power Mode

    G'day, How can I enter/exit the LPM's on a Tiva? (Can do it OK on the 430) Grant
  10. axsdenied

    Two LCD displays on Tiva

    Hi Has anyone successfully connected two TFT LCD displays to Tiva-C Launchpad? How much work would be to modify the graphics libraries to do so? Would two different LCD models be easier to do? I am aware that parallel connection is probably not possible due to lack of pins. Thanks for any suggestions.
  11. jonram1

    Hello from Louisiana

    Hello everyone, I am living in Louisiana I am currently designing a board with a tm4c123 I have a few launchpads and written a few programs. Im having a bit of trouble and have came here for some help. Jonathan
  12. Hello , I have been trying to play with the recently bartered CC3000 BP with my TIVA C 123 LP using Energia. I noticed the following things: Has the support for CC3000 been depreciated in x13 Update as the information mentions : " Circuit: * CC3200 WiFi LaunchPad or CC3100 WiFi BoosterPack with TM4C or MSP430 LaunchPad" ? When flashing the code to the LP(TIVA C123) with CC3000 BP for "ScanNetworks". The serial data hangs after showing:SimpleLink SDK 0.52 I then tried with the older version (x12) I updated the firmware and it kind of started to talk. Until it stuck at the IP. After running the "SimpleWebClient" i got the following output: Attempting to connect to SSID: mywifi Connected to wifi Waiting for DHCP address.... SSID: mywifi IP Address: 0.0.0.0 Starting connection to server... It doesnt go any forward. I am getting the same IP in other examples also. How should i solve the issue? Do i need to change router settings? I have DHCP Enabled. Thanks a lot,
  13. Two problems with delayMicroseconds on Tiva (and I believe on CC3200) 1) The delay interval is erratic, appearently because delayMicroseconds does not handle rollovers of the systick counter correctly. 2) delayMicroseconds can not work for dealys longer that 10,000 microseconds. (Even though the documentation says that it works up to 16383, and even includes an example.) Details: Issue 1) Code to demonstrate problem: #define DELAY_FOR 5000 void setup() { Serial.begin(9600); Serial.print("Delay"); Serial.println(DELAY_FOR); Serial.print("elapsed tics should be: "); Serial.println(F_CPU/1000000); } void loop() { unsigned long i = micros(); unsigned long systicstart = HWREG(NVIC_ST_CURRENT); delayMicroseconds(DELAY_FOR); unsigned long systicstop = HWREG(NVIC_ST_CURRENT); unsigned long p = micros(); unsigned long o = p-i; Serial.print("Before: "); Serial.print(i); Serial.print(" Systic: "); Serial.println(systicstart, HEX); Serial.print("After: "); Serial.print(p); Serial.print(" Systic: "); Serial.println(systicstop, HEX); Serial.print("After-Before: "); Serial.print(o); Serial.print(" Systic: "); Serial.println(systicstart - systicstop, HEX); Serial.print("Error: "); Serial.print(((long int)DELAY_FOR) - ((long int)o)); Serial.print("\t Systic: "); Serial.println((long int)((systicstart - systicstop) & 0xFFFFFF)-((long int)(F_CPU/1000000))); Serial.println(); } Just loops forever doing a delay, then printing how long the delay took (prints both in micros(), and ticks of the systick counter. (Note that micros() does not use the systick timer.) Example output: Before: 8470600 Systic: B5751 After: 8475601 Systic: 53C94 After-Before: 5001 Systic: 61ABD Error: -1 Systic: 399981 Before: 8599763 Systic: 2735 After: 8599893 Systic: C33E4 After-Before: 130 Systic: FFF3F351 Error: 4870 Systic: 15987457 Before: 8734135 Systic: 7055D After: 8739137 Systic: EAA0 After-Before: 5002 Systic: 61ABD Error: -2 Systic: 399981 While usually the delay is about 5000 microseconds, often it isn't (in the middle reading above the delay is much too short). The code from wiring.c (this is for Tiva, the CC3200 code is somewhat similar). void delayMicroseconds(unsigned int us) { volatile unsigned long elapsedTime; unsigned long startTime = HWREG(NVIC_ST_CURRENT); do{ elapsedTime = startTime-(HWREG(NVIC_ST_CURRENT) & 0x00FFFFFF); } while(elapsedTime <= us * (F_CPU/1000000)); } There are a few suspect things about this code: Since it is subtracting unsigned values, it seems to be the intention to rely on modular arithmatic to get the comparisons right. (As in discussed in this page http://www.thetaeng.com/TimerWrap.htm ). However as I understand it, for that to work the timer needs to overflow at the full width of the values being stored. In this case the timer is at most a 24 bit timer, but the values are 32 bits. If the full timer was being used, it might be possible to fix that by masking off the top 8 bits. elapsedTime = (startTime-HWREG(NVIC_ST_CURRENT)) & 0x00FFFFFF; However in this case the full width of the timer is not being used, it wraps to F_CPU/SYSTICKHZ after reaching 0 (it is a count down timer). So it looks like every time the systick timer rolls over, any delayMicroseconds which is in progress will have an unexpected result. (In the above output, where the delay was short, not the starting the starting value of NVIC_ST_CURRENT is small, and the ending value is close to C3500, which is F_CPU/SYSTICKHZ on a Tiva launchpad, i.e. the counter rolled over). Small side issue: The code also seems to assume that the upper 8 bits of NVIC_ST_CURRENT will always be 0 (the manual warns against making assumptions about such bits). A fix for that would be to add & 0x00FFFFFF to where startTime is set. I do not have a particular suggestion of how to fix the code. I think this issue also applies to the CC3200 (just from looking at the source code, but I have not checked that out in detail, and I do not have one to test.) -- 2) Since the systick counter rolls over every 10000 microseconds, delayMicroseconds can not delay for longer than that. .../energia-0101E0013/reference/DelayMicroseconds.html The documentation says "Currently, the largest value that will produce an accurate delay is 16383." (There is also an example which uses delays of this length.) The documentation may be a holdover from Arduino, which says the same thing, even though it does not appear to apply to the Arduino Due, for instance. (I do not know if this was true of MSP430.) A possible fix for the delay duration issue would be to add something like the following to the beginning of delayMicroseconds if (us > 9000){ delay( us / 1000); us = us % 1000; }; (the 9000 was somewhat arbitrary, rather than a constant it should be calculated based on SYSTICKHZ ). Might also be well to clarify the documentation about which platform the 16383 relates to. This is all on Energia 13, but I believe was also present in Energia 12.
  14. Tiva/Stellaris programs were compiled with optimization -Os in Energia E0012. (Optimize for size). In Energia E0013 optimization is turned off for Tiva/Stellaris and CC3200. (-O0) How do I turn optimization back on in Energia E0013? I have been working on a Arduino/Energia library which has a timing critical interrupt handler. Of course there is the #pragma route to controlling optimization. But is there a way in the IDE, or in preferences.txt, is #pragma the preferred method. On a somewhat related note, are there any release notes for the new version (which might cover changes and how to handle them)? (e.g., where I could have found out about the change in optimization). I have looked around a bit and haven't found any kind of list of what is new. http://www.energia.nu/release.html only goes up through version 12. The readme on github doesn't even mention the CC3200 https://github.com/energia/Energia/blob/master/ReadMe.md After I had problems generating a listing in the new release I did discover that debugging information is turned off by default, and there is a new option for turning debugging information on/off (in File - Preferences). But haven't found anything similar for optimization. Thanks
  15. In at least two places the Energia documentation claims that LaunchPad pins can source or sink up to 40 mA. Is that true of all (or any) of the launchpads supported by Energia? (i.e., Stellaris/Tiva, Tiva Connected, MSP430, Fraunchpad, C2000, CC3200) For the Stellaris launchpad, the documentation for the LM4F120 gives drive strength options of 2, 4, or 8 mA, and says up to 4 pins can sink 18 mA. So where does the 40mA come from (or go to)? Yet energia.nu says: "LaunchPad pins can source (provide positive current) or sink (provide negative current) up to 40 mA (milliamps) of current to other devices/circuits." http://energia.nu/guide/tutorial_digitalpins/ http://energia.nu/reference/constants/ I note that the Arduino documentation says the same 40mA, so suspect this specification may have accidentally been copied from the AVR. If so, seems like an invitation to release the magic smoke. Please someone either point me to where the documentation says that the various launchpads can source/sink that much, or fix the web site to either include the actual numbers for the various launchpads, or remove the misleading number. I previously posted this question on stellarisiti (where it failed to generate any action), but just noticed that the web site says to post documentation corrections on the 43oh Energia forums.
  16. chicken

    SPI bit order on Tiva?

    Tracking down the reason why my SHARP Memory LCD library does not work on Tiva and C3200 LaunchPads, I noticed that Energia's SPI.setBitOrder is not implemented for these platforms. Digging a bit deeper (i.e. TivaWare and datasheet) I can't see a register to control SPI bit order. Two questions: - Did I miss something or does the SSI peripheral not support LSB bit order? - If not, ARM has an RBIT instruction that would be helpful in a workaround. Any way to invoke this with GCC on a variable without resorting to inline assembly?
  17. Hello, I'm planning for a project the use of 12 Channels PWM (Frequency must be above 60khZ, because of driving some VCA´s and not getting into the audio range). As I know, Energia uses "software" PWM with the use of timers (the hardware PWM´s of the new TIVA's is not implimented). So my question is, may I can get some overall performance boost using the driverlib hardware PWM rather than the energia software version? Thanks regards Matthias
  18. WS2812 driver for Tiva is available here
  19. Hello everyone I wrote the following code to run a stepper motor in arduino depending upon a UART signal. The UART signal came from processing 2 code. Now instead of an arduino board i want to run the same code on my TIVA C series tm4c123gh6m launch pad what should i do. Note- I used digital pins 8,9,10,11 of the arduino to run the motor. What does 8,9,10,11 refer to in tiva C series? int a=8; int b=9; int c=10; int d=11; void setup() { Serial.begin(9600); pinMode(a, OUTPUT); pinMode(b, OUTPUT); pinMode(c, OUTPUT); pinMode(d, OUTPUT); establishContact(); } void loop() { int tex; tex=Serial.read(); if(tex=='A') { digitalWrite(a,LOW); digitalWrite(b,HIGH); digitalWrite(c,LOW); digitalWrite(d,HIGH); delay(5); digitalWrite(a,LOW); digitalWrite(b,HIGH); digitalWrite(c,HIGH); digitalWrite(d,LOW); delay(5); digitalWrite(a,HIGH); digitalWrite(b,LOW); digitalWrite(c,HIGH); digitalWrite(d,LOW); delay(5); digitalWrite(a,HIGH); digitalWrite(b,LOW); digitalWrite(c,LOW); digitalWrite(d,HIGH); delay(5); } } void establishContact() { while (Serial.available() <= 0) { Serial.write('A'); // send a capital A delay(300); } }
  20. I got an email about this today - you can order up to 2 Tiva Connected LPs at $19.99 each. Very tempting! https://estore.ti.com/tiva-connected-launchpad.aspx?DCMP=mcu-tivc-ek-tm4c129xl-en&HQS=mcu-tivc-ek-tm4c129xl-em-es-en
  21. Hello, as I was studying the (extremely good written!) driverlib documentation, i noticed the SysCtlPeripheralReady function. Because it is not always clear which Timer (TIMER,WTIMER,WATCHDOG) is currently in use (many of them are used with PWM and other stuff), I wrote this little helper sketch for my Tiva C. The definitions for other peripheral can be read in "sysctl.h", I only used the timers to keep it short. I also included the SysCtlPeripheralPresent function, but I think it is meant, that a peripheral is physically available, so the "ready" function is the key. Try it out with some line of code with PWM stuff (with different pins) for example and see the difference! /* Little timer state helper no (c) by Matthias Diro */ #include <stdint.h> #include <stdbool.h> #define PART_TM4C123GH6PM #include "inc/tm4c123gh6pm.h" #include "driverlib/sysctl.h" void setup() { Serial.begin(9600); } void loop() { Serial.println("---Timertest---"); Serial.println("***Timer***"); for (int x=0;x<=5;x++) { Serial.print("Timer: "); Serial.print(x); Serial.print(" present: "); Serial.print(SysCtlPeripheralPresent(4026532864+x)); Serial.print(" ready: "); Serial.println(SysCtlPeripheralReady(4026532864+x)); } Serial.println("***WTimer***"); for (int x=0;x<=5;x++) { Serial.print("WTimer: "); Serial.print(x); Serial.print(" present: "); Serial.print(SysCtlPeripheralPresent(4026555392+x)); Serial.print(" ready: "); Serial.println(SysCtlPeripheralReady(4026555392+x)); } Serial.println("***Watchdogs***"); for (int x=0;x<=1;x++) { Serial.print("Watchdog: "); Serial.print(x); Serial.print(" present: "); Serial.print(SysCtlPeripheralPresent(4026531840+x)); Serial.print(" ready: "); Serial.println(SysCtlPeripheralReady(4026531840+x)); } Serial.println(); while(1); } Maybe this little code helps some of you! Regards Matthias
  22. Hi Everyone, New to the forum and new to the LaunchPad....but having a lot of fun using them to prototype. I am considering moving from CCS to Energia as my primary development platform and had a few questions to assist me with the decision. Is Energia only for LaunchPad's? Can I develop Energia code using a LaunchPad and then upload this code to a supported MCU using a Programmer, which I will then use on my own circuit board? How similar is the Energia code between the different LaunchPad variants? (does it require major changes?) Is anyone using Energia for a product release? I know it does not have debugging features, but the benefits of quick development and the ability to use in different chips with same/similar code may outweigh these concerns. Thanks! Glenn.
  23. Hello, I tried out basic functionality with the arduino MIDI library 4.1 on TIVA Launchpad TM4C123G (all others should work also) Download Link: https://github.com/FortySevenEffects/arduino_midi_library/ The only thing to do is to setup the serial interface, you can simply do that with insert following line into midi_Settings.h: #define MIDI_DEFAULT_SERIAL_PORT Serial1 "Serial1" defines PC_4 = RX(1) input on tiva, PC_5 = TX(1) output on tiva, so you should choose every serial port you want (untested). my patched midi_Settings.h is included as attachement I´ve tested successfully it with my self build midi interface, sending some random notes from my computer. Here is a basic test code example - it reads midi input notes on channel1 and print it out on the serial monitor (+ led flashing) #include <MIDI.h> #define LED RED_LED // LED pin on Tiva Launchpad TM4C123G void HandleNoteOn(byte channel, byte pitch, byte velocity) { // Do whatever you want when you receive a Note On. if (velocity == 0) { digitalWrite(LED,LOW); // This acts like a NoteOff. } else { digitalWrite(LED,HIGH); } Serial.print("Note ON: Channel: "); Serial.print(channel); Serial.print(" Key: "); Serial.print(pitch); Serial.print(" Velocity: "); Serial.println (velocity); // Try to keep your callbacks short (no delays ect) // otherwise it would slow down the loop() and have a bad impact // on real-time performance. } void HandleNoteOff(byte channel, byte pitch, byte velocity) { digitalWrite(LED,LOW); Serial.print("Note OFF: Channel: "); Serial.print(channel); Serial.print(" Key: "); Serial.print(pitch); Serial.print(" Velocity: "); Serial.println (velocity); } void setup() { pinMode(LED, OUTPUT); MIDI.begin(1); // Launch MIDI and listen to channel 1 MIDI.setHandleNoteOn(HandleNoteOn); MIDI.setHandleNoteOff(HandleNoteOff); Serial.begin(9600); // Energia serial monitor to see events } void loop() { MIDI.read(); // nothing more to do here } Be carful! the "serial.print" lines are only for testing and not recommended within the setHandleNoteOn/Off handler! Hey admin: please let us attach *.ino files! (You aren't permitted to upload this kind of file) regards Matthias midi_Settings.h
  24. Hi. I try to download a program in microcontroller and i receive the next error : CORTEX_M4_0: Trouble Reading Memory Block at 0x708 on Page 0 of Length 0x18: Debug Port error occurred. CORTEX_M4_0: Error: Debug Port error occurred. I use Tiva C Series LaunchPad EK - TM4C123XGL.
×