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

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / Serial bootloader K50 choice in config.h
« on: June 28, 2016, 12:40:39 PM »
Will the serial bootloader project support Kinetis K50DX256?  If so, which hw choice should be selected in the bootloader config.h (K40 w/o ethernet?) and does anything else need to be modified?

2
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 10, 2014, 06:26:31 PM »
Excellent idea!  That worked.

3
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 10, 2014, 06:08:44 PM »
I didn't have a cap on VOUT33, so I added the 2.2uF.  That gets me through enumeration but I have some garbage file names that show up.  I didn't have a cap on VREGIN either, so I tried adding one there (4.7uF) but no help.  The garbage characters seem to be consistent and not random.

4
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 10, 2014, 01:16:24 PM »
As a first try on my hw, I disabled the watchdog and changed the DEMO_LED_1 from bit 7 to bit 6 to line up with an LED on my board.  My K20 device is an 80 pin pkg instead of 100 pin, but otherwise same PN.  My LED blinks in boot loader mode (5Hz), but the dreaded "USB device not recognized" is still a problem.  I double checked the USB connector wiring and don't see a problem there.

5
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 10, 2014, 12:20:07 PM »
Sorry, it did unzip in spite of the "incorrect password" message.  This beta version is much more user friendly in CW 10.5!  I set the target for TWR-K20D72M, and it compiles/downloads/ runs without problem.  After I adjust some of the hw settings for my board, I should be good to go.  Thanks for your help!

6
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 10, 2014, 11:56:06 AM »
I am using CodeWarrior 10.5.  I can't unzip V1.4.4 Beta with the password I have for V1.4.3.

7
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 09, 2014, 10:24:59 PM »
Thanks for the suggestion. I tried flashing uTaskerSerialLoader_K20_72.S19 on the TWR board and it works fine.  My modified code must be the problem!  I started with v1.4.3, and here are the files I changed.

8
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 09, 2014, 09:26:43 PM »
INTERNAL_USB_CLOCK is defined, so I'm ok there.  I have tried the TWR-K20 board and my hw with same USB cable and neither one works, although the same cable works on my TWR-K60.  I will try comparing scope traces on D+ and D- with the working K60 and non-working K20.

9
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 09, 2014, 06:27:00 PM »
Ah, I got the simulation to run/debug.  I had to change the linker output file name to uTasker.exe.  It stopped with a "uMalloc failed!!" exception message.  I increased the OUR_HEAP_SIZE multiplier from 8 to 24 and it runs fine in the simulator, but still getting USB device not recognized when connecting the actual hw.

10
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 09, 2014, 03:39:45 PM »
Forgot I have a TWR-K20D72M... loaded the bootloader and confirmed at least the 72 MHz is correct because the RS232 timing was good for 115200.  Still have the same USB problem. 
I tried the Visual Studio simulation, but it will not run after compiling (Visual Studio Express 2013).  I get an error that it can't find the *.exe file, but there is an extra "." in the path -- D:\uTasker\Applications\uTaskerSerialBoot\Simulator\.\Debug\uTasker.exe.  Without the \., the file is there but I don't know how to fix that yet; this is my first time using Visual Studio.

11
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader with MK20DX256
« on: April 09, 2014, 02:23:43 PM »
I can't seem to find my problem.  Looking at SIM_CLKDIV2 register, USBDIV = 2 and USBFRAC = 1.  USB clock should be 72 MHz x (USBFRAC+1)/(USBDIV+1), which would be 48 MHz.  Is there any external pin or handy method I could use to confirm the 72 MHz core or 48 MHz USB operation?

12
NXPTM M522XX, KINETIS and i.MX RT / Bootloader with MK20DX256
« on: April 08, 2014, 10:42:19 PM »
I am trying to use the MSD bootloader with this uC on custom hw.  I have added #define K20D72M in config.h (added KINETIS_MAX_SPEED 72000000, otherwise same as TWR_K20N50M), and new linker file (copy of included K40 linker file).  The board has an 8MHz crystal, so I used the same #define block as TWR_K20N50M in the app_hw_kinetis.h for the CRYSTAL_FREQUENCY, CLOCK_DIV, CLOCK_MUL, etc.  When I run the bootloader (forced to bootloader mode) and connect the USB port to PC, I get the "USB device not recognized" msg.  It looks like the device is not enumerated, but I am not sure why.  On the debugger, I see that the USB suspend/resume routine is executed right after plugging into the USB port.  Have I missed something in converting to this part?

Pages: [1]