Search results

  1. M

    Debugging with Visual Studio and Visual Micro extension.

    Not mentioned so far, but the vMicro appears to re--- compile only the new code. Consequently the compiles are really fast afterwards. That includes changing from debug to release and vice-versa.
  2. M

    Debugging with Visual Studio and Visual Micro extension.

    The vMicro properties seems to indicate that the Gcc compiler is being used. The default properties appear to support backwards compatibility to Arduino. One issue that I still want to confirm is whose compiler is being used in the vMicro environment with the Arduino extension. If the...
  3. M

    Debugging with Visual Studio and Visual Micro extension.

    Installing the Visual Micro extension is easy. After installing the Visual Studio IDE, use the extension system to install Arduino extension and the Serial extension. Do not install except by using the extension support system. The cost of these components is reasonable. About $50 or so...
  4. M

    Context of HardwareSerial lost when passed as a parameter

    Paul, I read your comment as implying that including the Arduino.h file eliminates the need to include the HardwareSerial.h file. But, I had to include the Hardware.... h file to fix the problem where the library file did not know about HardwareSerial. I just tested removing the .h file from the...
  5. M

    Context of HardwareSerial lost when passed as a parameter

    No, I am not suggesting that the functions be given different names. Although that would be one line of attack. Frankly, my suggestion that the .h file be included is all that I think ought to be done. If nothing else, it would be a clue, to anyone working on the code years later. That there is...
  6. M

    Context of HardwareSerial lost when passed as a parameter

    Debugging an issue by someone unfamiliar with the code. Reading Egyption Hyroglyphics Your statement is exactly correct. And is what I stated, that if you mistakenly declare the type as Serial in the called function, it will compile as long as the function does not use any of the hardware...
  7. M

    Context of HardwareSerial lost when passed as a parameter

    The code example at URL: https://www.pjrc.com/teensy/td_uart.html See below. Has a problem in that if you a add HWSERIAL.clear(); it will compile, as the HWSERIAL still has the context of hardware serial versus plain serial. A warning: plain serial has no: "clear();" Note that HWSERIAL is...
  8. M

    cmsis_version.h, missing.

    core cm7.h and the unthinkable. Your explanation is beginning to make sense. It figures that there is some sort of contorted answer that only a gaggle of geese or a squad of programmers could imagine. And that only another programmer could stumble into. An outsider might conclude that this is...
  9. M

    cmsis_version.h, missing.

    I appreciate your comment to not include the cm7 code unless bringing in more the CMSIS libary. However, the cmsis_version.h file is nowhere to be found, at all. So, where does that leave us? Here is the dir /s listing: C:\Program Files (x86)>dir cmsis*.h/s Volume in drive C has no label...
  10. M

    cmsis_version.h, missing.

    core_cm7.h and missing include I stumbled into this issue, when I tried to include core_cm7.h below <Arduino.h> There was some code in it that I wanted to use, but it's too many days and too many compiles since to remember just what I was after. But, cm7 can't be included like I noted...
  11. M

    cmsis_version.h, missing.

    TeensyDuino v 1.56, Arduino v 1.8.19 If include: #include "core_cm7.h" C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy4/core_cm7.h:63:27: fatal error: cmsis_version.h: No such file or directory Also: core_cm4_simd.h, may be missing? Teensy3 has it.
  12. M

    Debugging Teensy code with B4R, from Anywhere software

    The B4R ide supports development for most teensy boards. I have just built and loaded a small test program built in B4R and loaded it to a Teensy 4.1. The setup is trivial, if you have the Arduino ide installed. It supports gdb, which I am not familiar with. It appears to be running in a DOS cmd...
  13. M

    SPARKFUN BNO080 library Issues

    I have been working with the Sparkfun library BNO080, I report some findings regarding it's use. Last year I posted some comments about difficulty in using the SPI interface. I gave up on the SPI and went to using the I2C interface. The MBED github has a library based on the Sparkfun. There is a...
  14. M

    Teensyduino 1.56 Beta #2

    Tested 1.56 beta. In a VMWare 16.2 virtual machine running Windows 10 home. Arduino 1.8.16 Compiled without a hitch our largest, most complicated sketch.
  15. M

    GPS and DMA

    An update to this thread. The active antenna for L5 arrived a couple of days ago. Notice that it only took 3 months. And the first one sent out is still sitting in Memphis at FedEx, after a week delay. Wonder not, why, as it will boggle your mind. The L5 antenna (TAOGLAS) improves fix error by...
  16. M

    Using GDB with Teensy without hardware debugger, first Beta

    I ran into the same problem with the install. The issue was that the ardunio/teensy stuff was installed in a folder like arduino-1.8.15. Also, the teensy_debug.exe file had to be hand installed in the "libraries" folder in a custom made folder "TeensyDebug". Then the .exe file has to be run and...
  17. M

    Teensy4.1 Serial RX to DMA problem

    I don't understand the connection between the Serial8.begin and the LPUART5. LPUART6 or 8 if used in place of the 5 strings does not work, but 5 does. I can find no documentation in the IMXRT1062 that shows the connection or how the LPUARTx relates to the Serial ports on the teensy 4.x...
  18. M

    GPS and DMA

    The code that I have built to do the DMA to Serial.5 is below. It is based on the link id 22 below. The GPIO1_DR in the "source" line needs to be changed. It is not clear why LPUART5 is associated with Serial8 in the code I have built that does a DMA read from Serial8. I can find no...
  19. M

    GPS and DMA

    The load on the T4 is very high. The DMA is very necessary. I think I have identified the major issue holding up progress. The DMA .h file allows a call to set the destination using a register, rather than a buffer. I have not figured out what the register name is, yet. Otherwise, the code...
  20. M

    GPS and DMA

    First some preliminary background that may be useful to someone else doing something similar. A teensy 4.1 at 800 mhz and a TAU1202 GPS unit outputting at 115k baud to the teensy on serial8. I used the DMA code sample from the PJRC forum and it worked with minor tweaking. My tests indicate that...
  21. M

    Bootloader Chip For Teensy 4.0

    I notice that there is serious interest in a Teensy 4.x hardware debug environment. I and my partner are interested. Reading this thread highlights several impediments to such a solution. The design files that Paul uses are in a format that may not be importable into new board layout programs...
  22. M

    BNO080 and Teensy 4.1 and SPI issue

    The change of pins from 36 to 10 did the trick. But, we are going to drop SPI and convert to I2C as the SPI timeout problem is too unstable for our purposes. And we don't need the SPI, so... Thanks for the suggestion. By the way, what was your reasoning for the change? The 10 pin is obviously...
  23. M

    BNO080 and Teensy 4.1 and SPI issue

    I have been gone for a week, just getting back to this. Your Pinouts are the same for 11,12,13 as we have our board. The PS1 is -> 3.3v. Your Pinouts for 7,8,9, 10 are different as we are using: 40,5, 41, 36. Are you saying that we must use the pinouts as you describe? I have installed the...
  24. M

    BNO080 and Teensy 4.1 and SPI issue

    I may have the wrong SPI library in use.
  25. M

    BNO080 and Teensy 4.1 and SPI issue

    The board is a FSM305 with the BNO080 chip on it. For some strange reason I did not get any of the notices on the 6th as emails, was not aware of these posts. I will double check all of the details, pins, etc. I am using the Sparkfun lib, latest from a few days(?) ago. THe init seems to happen...
  26. M

    BNO080 and Teensy 4.1 and SPI issue

    Correct me all to pieces, it's the SparkFun lib. SparkFun_BNO080_Arduino_Library.h In any event, further testing: there are delays in the spiWait routine that are cpu dependent. The counter is 8 bits and I have tested with 16 bits using 25000 instead of 120 or so. Results in no timeouts...
  27. M

    BNO080 and Teensy 4.1 and SPI issue

    I have studied all of the posts about 4.x and I2C here on the forum. I am seeing similar problems with SPI to those mentioned in posts that data back to the first of this year. The Adafruit 80 library and various init routines from various forks all are about the same, even the I2C versions are...
  28. M

    vsCode build results in HEX file that won't upload

    The issue here was not having the latest TyTools. 9.8.1 or later appears to solve the problem.
  29. M

    vsCode build results in HEX file that won't upload

    4.1 board. And the latest Arduino and Teensyduino. As well as the latest vsCode and tools. I may have found the answer. The vsCode generates a file with ".hex" extension. The Arduino generates ".ino.hex". The latter version uploads. The vsCode version uploads if it is renamed. The Teensy...
  30. M

    vsCode build results in HEX file that won't upload

    I had a little trouble installing vsCode, but the only issue that I can't seem to find a way around or any references online about is the following message: Firmware too big (max 1048576 bytes) Uploads of this source compiled from the Teensyduino IDE work without problems, if the source is...
Back
Top