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 - Caleb

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / BOOT_MAIL_BOX location
« on: March 22, 2022, 09:01:44 PM »
 Hi there,
   In the i.MX RT series, the BOOT_MAIL_BOX and other persistent memory locations are up at the top of memory, above the stack.  This poses a bit of a problem in that the bootloader and the applications need to have the same memory configuration.  For example, on the 1062, it's up at 0x20077ffe by default, which requires the DTC be set differently from the chip default.

Is there any reason I can't change the fnGetPersistentMemory fucntion to get it from one of the lowest areas in memory, that's not already taken?  This would mean it's independent of how DTC and ITC are configured?

Thanks
 -Caleb

2
NXPTM M522XX, KINETIS and i.MX RT / uTasker v2.0.0 doesn't compile on MCUXpresso v11.5.0 (.text LMA overlaps)
« on: February 03, 2022, 01:19:55 AM »
Hi there,
   I tried compiling the latest V2.0.0 branch (and also master), and both fail when compiling with MCUXPresso 11.5.0.   The error is:

Code: [Select]
arm-none-eabi-gcc -nostartfiles -Xlinker -Map="uTaskerBM_loader.map" -Xlinker --gc-sections -Xlinker -print-memory-usage -Xlinker --sort-section=alignment -Xlinker --cref -mcpu=cortex-m7 -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mthumb -T iMX_RT_10XX_FlexSPI_NOR.ld -L "C:/Users/caleb/cobalt/cobalt-nxp-top-board/utasker/Applications/uTaskerBoot/GNU_iMX" -o "uTaskerBM_loader.axf"  ./uTasker/crypto.o  ./stack/SSL/mbedtls-1.3.10/aes_mbedTLS.o  ./Hardware/iMX/iMX.o  ./Applications/uTaskerBoot/uTaskerBootLoader.o   
c:/nxp/mcuxpressoide_11.5.0_7232/ide/plugins/com.nxp.mcuxpresso.tools.win32_11.5.0.202107051138/tools/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.exe: section .text LMA [60000000,60001a25] overlaps section .text LMA [60000000,60001fff]
c:/nxp/mcuxpressoide_11.5.0_7232/ide/plugins/com.nxp.mcuxpresso.tools.win32_11.5.0.202107051138/tools/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.exe: section .rodata LMA [60000000,60000029] overlaps section .text LMA [60000000,60001a25]

By going back to V11.4.x, it does compile.

Thanks,
 -Caleb

3
µTasker general / Re: uTasker USB audio capabilities
« on: May 29, 2021, 02:44:23 AM »
Ah, so sounds like it's not too straightforward.  I have run the sai demo from NXP, and I can actually get enough channels running, and they support UAC 2.0.  I would prefer to be a utasker project, but I also need to get it done quickly, so really need to start with a working example.

Thanks,
  -Caleb

4
µTasker general / Re: uTasker USB audio capabilities
« on: May 28, 2021, 08:01:17 PM »
I did just try compiling and ... it doesn't compile on i.MXRT1060 when I enable either USE_USB_AUDIO or USE_HS_USB_AUDIO.

Several errors, but as a generality:
```../usb_Audio.h:60:50: warning: "SAMPLING_FREQUENCY" is not defined, evaluates to 0 [-Wundef]
../usb_Audio.h: In function 'buffer_wrap':
../usb_Audio.h:60:50: warning: "SAMPLING_FREQUENCY" is not defined, evaluates to 0 [-Wundef]
   60 |     #define _PLL_COMPENSATION  (PIT_FREERUN_FREQ(SAMPLING_FREQUENCY)/200)// 0.5% adjustment
      |                                                  ^~~~~~~~~~~~~~~~~~
../../../Hardware/iMX/iMX.h:12338:46: note: in definition of macro 'PIT_FREERUN_FREQ'
12338 | #define PIT_FREERUN_FREQ(Hz)    ((PIT_CLOCK/(Hz)) - 1)
      |                                              ^~
../usb_Audio.h:61:9: note: in expansion of macro '_PLL_COMPENSATION'
   61 |     #if _PLL_COMPENSATION == 0
      |         ^~~~~~~~~~~~~~~~~
../../../Hardware/iMX/iMX.h:12338:45: error: division by zero in #if
12338 | #define PIT_FREERUN_FREQ(Hz)    ((PIT_CLOCK/(Hz)) - 1)
      |                                             ^
../usb_Audio.h:60:33: note: in expansion of macro 'PIT_FREERUN_FREQ'
   60 |     #define _PLL_COMPENSATION  (PIT_FREERUN_FREQ(SAMPLING_FREQUENCY)/200)// 0.5% adjustment
      |                                 ^~~~~~~~~~~~~~~~
../usb_Audio.h:61:9: note: in expansion of macro '_PLL_COMPENSATION'
   61 |     #if _PLL_COMPENSATION == 0
```

among other errors.  Is this expected to work?  Trying to compile for MIMXRT1060 EVK.

Thanks,
 -Caleb

5
µTasker general / uTasker USB audio capabilities
« on: May 28, 2021, 07:13:29 PM »
Hi Mark, all,
   I'm starting a new project that needs to have multi-channel, full-duplex USB audio.  This will collect many microphone channels, as well as have simultaneous loudspeaker channels too.

Needs for the immediate project:
 16kHz sample rate
 9 channels of capture (USB IN, SAI RX via i.MXRT SAI1, with 2 rx data pins on 8 slots/pin TDM bus)
 2 channels of playback (USB OUT, SAI TX via SAI1 tx pin, TDM bus)

I believe this requirement can fit into a standard USB Audio Class 1.0 with no problem.  However, UAC 1.0 was crazy, and specifically seems to disallow high speed.  Not sure why that is...

Anyway, I'd like to use uTasker as a platform for USB audio going forward, with potentially *many* more channels in both directions, say up to at least 32in and 8 out or so, which will require USB Audio Class 2.0 to run on a high speed USB bus. 

So, my questions are:
* What's the state of the USB Audio class drivers currently (I will be building and testing momentarily to try things out, but I figured I'd get this question off into the ether)
* Will uTasker work well for the current project (UAC1.0 minimum project, multiple SAI channels)
* Will uTasker work well for the future projects (high speed USB).

Thanks,
  -Caleb

6
NXPTM M522XX, KINETIS and i.MX RT / Re: What's the syntax 0x100000[0x100-FALLBACK_LD] in Build_iMX_RT.bat mean
« on: February 05, 2021, 09:23:20 PM »
Thanks Mark.  Makes sense now.

-Caleb

7
NXPTM M522XX, KINETIS and i.MX RT / What's the syntax 0x100000[0x100-FALLBACK_LD] in Build_iMX_RT.bat mean
« on: February 04, 2021, 02:31:00 AM »
I'm updating my build scripts, but I don't understand the syntax in   Applications/uTaskerSerialBoot/GNU_iMX/Build_iMX_RT.bat.

The line looks like this:
Code: [Select]
.. 0x40000[0x100-FALLBACK_LD] ...

What's that syntax mean?  Does the BAT file interpret FALLBACK_LD as something?  If so, where's it set?

Thanks,
 -Caleb

Pages: [1]