![]() This points to function AdcLdd1_CreateSampleGroup().ģ71 if (SampleGroupPtr. Res = FX1_Enable() /* enable accelerometer (just in case) */ To keep things simple, I’m using global variables: The TRAVEO T2G CYT2CL family products contain embedded peripherals supporting controller area network with flexible data rate (CAN FD), local interconnect. PORT_PDD_SetPinPullEnable(PORTE_BASE_PTR, 6, PORT_PDD_PULL_ENABLE) įor the file system I need to have a file system object and a file pointer. PORT_PDD_SetPinPullSelect(PORTE_BASE_PTR, 6, PORT_PDD_PULL_DOWN) * SD card detection: PTE6 with pull-down! */ Because the BitIO component has no methods to change the electrical characteristics, I’m using PDD macros (see “Low-Level Coding with PDD (Physical Device Driver”)): Then it gets the accelerometer data and logs it to a file every second.įirst, I need to make sure I have a pull-down enabled for the SD card detection pin (PTE6). Use the menu File > New > C Project to create a new project:ĪPP_Run() implements my logger loop: initialize the accelerometer and mount the file system. Create a Processor Expert project for the MK64FN1M0xxx12. ![]() Note that the wizard pages are different. If using CodeWarrior for MCU10.6, then use the File > New > Bareboard project. If you are using Kinetis Design Studio (KDS), then use the File > New > Kinetis Design Studio menu. ❗ The steps below are for standard DIY Eclipse Kepler IDE and GNU ARM Eclipse. An RTOS with tasks then can be easily added to the project. ![]() While it would make sense to use an RTOS like FreeRTOS for a data logger, I’m showing here a ‘bare metal’ data logger. In principle, this tutorial can be applied to any other board: Just make sure you select the microcontroller on your board, and adopt the pin settings for the devices you have. The project created in this tutorial is available on GitHub. For now I simply included the header and C-File in the project directory. The file seems to be included since it shows up in the dependencies. Right now trying to call a function of a included header file. Make sure you have loaded the latest Processor Expert components from GitHub (see “ Processor Expert Component *.PEupd Files on GitHub“). I am just starting out with Segger Embedded Studio. The principle is the same, but the project creation steps will be somewhat different. □ This tutorial can be used with CodeWarrior for MCU10.x, Processor Expert Driver Suite or Kinetis Design Studio too. Freescale FRDM-K64F board with USB cable Hi all, I am deciding on whether I should purchase the BM-CS5SR for monitoring heart rates and was wondering if there are any examples as I would like to.Eclipse Kepler with Processor Expert as outlined in “ Constructing a Classroom IDE with Eclipse for ARM“.I moved to Eclipse Kepler (see “ Constructing a Classroom IDE with Eclipse for ARM“), so here is an updated tutorial: how to create a data logger application with the FRDM-K64F and Eclipse Kepler. In the special case of segger embedded studio there are, as I know by now, two ways to reference extern files. Basically the same can be applied to the FRDM-K64F. No difference.ġ0) I also notice that something is been send to the Debug Terminal because the cursor moves to a new line every time a new NRF_LOG should be displayed.In “ Arduino Data-Logger Shield with the FRDM-KL25Z Board” I already used the FRDM-KL25Z with the Arduino Data-Logger shield with CodeWarrior. SoC family along with demo application and Segger Embedded Studio project files for nRF52832 and nRF52840. Ozone currently does not support the color feature. Create and print a log for delivery stops. 3) When debugging the project with SEGGER's Ozone, the terminal shows the RTT messages without the color settings. However printf works just fine on the SES Debug TerminalĪfter reading lots of posts and documentation that's what I've done so far:ġ) tried many other examples and got the same problemĢ) NO, I'm not using RTTviewer and SES Debug Terminal at the same timeģ) On SDK_Config.h made sure that settings are:Ĥ) Tried to build clean, build Debug, build ReleaseĦ) If instead of NRF_LOG_INFO I use printf the SES Debug Terminal prints my message just fineħ) If I open the SES J-Link Control Panel Window while debugging, I can see the message on the RTT tab, but still not in Debug Terminal:ĩ) Tried changing NRF_LOG_FLUSH() to NRF_LOG_PROCESS(). Yes, that is what it was meant for in the first place, to replace SWO printf debugging so you do not waste another pin for debugging. Basically, I can see the logs with RTTviewer but not in SES Debug Terminal. I'm having some trouble displaying logs to the SES Debug Terminal.
0 Comments
Leave a Reply. |