Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Anton

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / Re: McuXpresso integration
« on: May 24, 2020, 09:22:01 AM »
Mark,

It could very well be that the files mentioned were excluded originally. I've previously managed to screw up the exclude list in multi-configuration projects in Mcuxpresso by having Dropbox application on and syncing files in background, while working in Mcuxpresso, maybe it is the case here is well.  I have to make habit of pausing Dropbox sync before starting McuX.

Thanks.

Anton

2
NXPTM M522XX, KINETIS and i.MX RT / Re: McuXpresso integration
« on: May 23, 2020, 09:34:40 PM »
Mark,

Excluding CO_OD.* from build did the trick.

BR

Anton

3
NXPTM M522XX, KINETIS and i.MX RT / Re: McuXpresso integration
« on: May 23, 2020, 03:35:48 PM »
Mark,

I ended up excluding CMSIS_DSP. But the problem still persists with CO_driver.h not being able to see defines within types.h, include paths are there pointing to correct directory. Just to test I've cloned the repository https://github.com/uTasker/uTasker-Kinetis and it seems to compile without issues.

4
NXPTM M522XX, KINETIS and i.MX RT / McuXpresso integration
« on: May 21, 2020, 09:44:14 PM »
Hi Mark,

I've been following your video here on importing and compiling uTasker in McuXpresso (11.1.1_3241).
However I ran into some issues during compilation process (FRDM-K22F):

1. Bunch of errors related to redefinition of arm_math related functions. I suppose the correct way of handling this is just to exclude CMSIS_DSP from build, right?

Code: [Select]
Description Resource Path Location Type
#error "Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)" core_cm0plus.h /uTaskerV1.4/Hardware/CMSIS_DSP line 88 C/C++ Problem
expected identifier or '(' before '{' token cmsis_gcc.h /uTaskerV1.4/Hardware/CMSIS_DSP line 1020 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_abs_f32.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_bitreversal.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_cfft_f32.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_cfft_q15.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_cfft_radix4_q15.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_cfft_radix8_f32.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_cmplx_mag_f32.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** [Hardware/CMSIS_DSP/subdir.mk:54: Hardware/CMSIS_DSP/arm_common_tables.o] Error 1 uTaskerV1.4 C/C++ Problem
make: *** Waiting for unfinished jobs.... uTaskerV1.4 C/C++ Problem
redefinition of '__QADD' arm_math.h /uTaskerV1.4/Hardware/CMSIS_DSP line 930 C/C++ Problem
redefinition of '__QADD16' arm_math.h /uTaskerV1.4/Hardware/CMSIS_DSP line 778 C/C++ Problem


2. QUEUE_HANDLE error in uCANopen. It is defined in types.h so I'm not sure why McuXpresso can't see it.

Code: [Select]
unknown type name 'QUEUE_HANDLE' CO_driver.h /uTaskerV1.4/uTasker/uCANopen line 382 C/C++ Problem

3. Project properties -> C/C++ Build -> MCU Settings show that target is Generic M4 with only RAM definition present. Is this correct?


Thanks,

Anton

5
µTasker general / Adding new task
« on: April 30, 2020, 11:41:56 AM »
Hi,

I've been following the uTaskerV1.3_user_guide.PDF attempting to add new task but:

1. ctTaksTable in TaskConfig.h is guarded by OPSYS_CONFIG define which is not defined in my case and therefore the code in between is excluded (I'm building for Utasker Kinetis plus GNU Build). What does it do? `this is only set in the hardware module` is a bit cryptic comment.
2. How should i go about adding a new c file to the project? How should I update make file to reflect this change?

Best Regards,

Anton

6
NXPTM M522XX, KINETIS and i.MX RT / Re: WDOG operation
« on: April 12, 2019, 05:03:55 PM »
Mark, thanks a lot. #define WATCHDOG_DISABLE()    1 definitely helped.

7
NXPTM M522XX, KINETIS and i.MX RT / WDOG operation
« on: April 12, 2019, 10:09:11 AM »
Mark,

I have now more or less a working bootloader + application image running on FRDM-K22F board, where application starts if SW2 is not asserted or application can be started via `go` command after entering bootloader. The thing that bothers me is that if bootloader is entered and then application is executed via `go` command everything works as expected, but if pure reset is performed and application starts directly, then a get a reset every couple of seconds due to wdog (RCM reports 0x20 as the cause of reset). WDOG->STCTRLH register after application boot-up indicates that watchdog is disabled (bit 0 is at logic zero). I've attempted to disable wdog after application start, but that does not seem to help, when jumping directly to applicaton.

8
Mark, thanks a lot. Everything works as expected with the new files.

9
Mark,

Just to report back. After I've pulled down new version, the cross-compilation process works and I'm actually able to run bootloader on frdm-k22f board.
I've reviewed ?Tasker – Serial Loader User’s Guide in order to compile bootloader as specified in the in section 4, where SREC mode is enabled and menu is available via UART, but compilation fails once SERIAL_INTERFACE is uncommented with the following error:

Quote
unresolved external symbol _fnPerformBlankCheck referenced in function _fnApplication

but if SERIAL_INTERFACE and KBOOT_LOADER are uncommented, then compilation runs fine and I'm able to access target via KinetisFlashTool. What additional settings I need to adjust to get the same functionality as described in section 4?

The same applies if I attempt to enable, for instance, USB_INTERFACE and USE_USB_CDC which fails on

Quote
unresolved external symbol _fnPerformBlankCheck referenced in function _fnApplication

or USB_INTERFACE  and USB_MSD_DEVICE_LOADER

Quote
unresolved external symbol _fnAddSREC_file referenced in function _fnLoadTerminate


10
Mark, thank you! I've just pulled the latest version and will try it out, thanks a lot.

11
Mark,

I've downloaded an evaluation version from private GIT, but haven't used it untill now. Seems that the last commit was on 26th of July, last year.

I've tried to match the contents of both batch files, so they both have the same entry:

Quote
SET PATH=%PATH%;C:\nxp\MCUXpressoIDE_10.3.0_2200\ide\tools\bin
SET PATH=%PATH%;../../../Tools

But for some reason this entry into batch file does not work for uTaskerSerialBoot project.

12
µTasker general / uTaskerSerialBoot fails on cross-compilation step
« on: April 03, 2019, 03:57:09 PM »
Hi,

I'm attempting to compile uTaskerSerialLoader using VS 2017 Professional but it seems that it fails during a call to Build_Kinetis.bat with the following error:

Quote
make: *** No rule to make target `make_uTaskerV1.4_GNU_Kinetis', needed by `Build/serial_loader.o'.  Stop

The strange thing is that Applications\uTaskerV1.4 cross-compiles just fine without any issues.
Both projects are set with `kinetis plus GNU build` options.

Thanks.

Pages: [1]