Messages

1

µTasker general / Kinetis Device is Locked.Do you want to unlock it? Mass erase will be executed.

« on: December 16, 2021, 05:38:57 PM »

I am using MK60DX256VLL10 in a circuit. After soldering the controller onto the designed board, I tried to download my code into the controller using Ulink Pro Debugger using Keil MDK. But i encounter "Kinetis Device is Locked. Do you want to unlock it? Mass erase will be executed" to which I press OK. After few seconds, "Invalid ROM table" appears and erase is not performed.

To be cear, the same code is used in another board where same controller is used and in that board, I am able to doanload my code wihtout any "lock isssue" or "invalid rom table" issue.

2

NXP^TM M522XX, KINETIS and i.MX RT / Re: MK60DX256VLL10 RESET pin

« on: July 05, 2021, 06:30:22 PM »

I connected EZP_CS_b port to the ground of microcontroller for just a second and then removed this grounding. Afterwards, I checked the Reset pin and it was showing 3.3V and finally controller was out of reset state. Then I was able to sucessfully download and debug my code to this controller.

3

µTasker general / Re: I2C start condition issue

« on: July 05, 2021, 06:07:55 PM »

After so many hours of hard labour, I finally came to the realization that I was not initiating the pin configuration properly to use I2C functionality of PORTE (pin 0 and 1). I2C_1 is ALT6 of PORTE (pin 0 and 1) which I was overlooking in pin_mux.c file

4

µTasker general / Failure of Start bit generation in I2C

« on: July 04, 2021, 05:54:07 PM »

What are the possible causes of start bit not being generated in I2C using MK60DX256VLL10 though the same code is running fine when using TWR-K60D100M. In my own PCB, MK60DX256VLL10 drives PCA9698 using I2C but could not get it to work becaue microcontroller is not able to generate start bit. When I use I2C signals of TWR-K60D100M (in which accelerometer is being controlled using I2C) to connect to PCA9698, PCA9698 starts working because now the start bit is being generated. Is there any I2C specific setting to initiate in my controller MK60DX256VLL10 ( some settings to initiate I2C or something like that which is not mentioned in manuals) beacuse I am sucessfully using this controller on my same PCB to make use of its GPIO and CAN ports?

5

µTasker general / I2C start condition issue

« on: June 26, 2021, 11:52:15 AM »

I am using TWR-K60D100M-KIT and ran its accelerometer example for I2C. It ran succesffully. Modifying this example for neccessary chnages to establish I2C communication with GPIO expander PCA9698, I am facing a problem. The line of code which generates Start bit in accelerometer example is not generating satrt condition in my GPIO expander case (saw using oscilloscope). The values of I2C related registers just before the line of code generating start condition in both cases (on my pcb and TWR-K60D100M-KIT) are exactly same. So what would be the possible cause of start condition not being generated. SCL and SDA lines of I2C are pulled by 1.5k resistor value (voltage is 3.3V) in my pcb. Address of PCA9698 is 0x40 and I am trying to turn led on/off attached to bank 0, pin 0. Code is attached. Start-condition-code at line 686 of "fsl_i2c.c"

6

µTasker general / PCA9698 I2C Setting

« on: June 21, 2021, 06:05:19 PM »

I am new to I2C protocol and trying to turn LED on/off connected to bank 0, pin 0 in MCUXpresso software by NXP. Would there be any code whihc I can use as reference  for I2C or atleast guide me how to configure PCA9698 for turning LED on/off ? What would be the sequence of device (slave) address, output configuration register and command register for output?

7

µTasker general / Re: Kinetis K60: code imported from TWR-K60D100M to circuit using MK60DX256VLL10

« on: June 16, 2021, 04:24:55 PM »

Thank you for your help. It was really helpful.

In the .scf file, following modifications were made;

#define m_interrupts_ram_start 0x1FFF8000
#define m_interrupts_ram_size __ram_vector_table_size__

#define m_data_start (m_interrupts_ram_start + m_interrupts_ram_size)
#define m_data_size (0x00008000 - m_interrupts_ram_size)

#define m_data_2_start 0x20000000
#define m_data_2_size 0x00008000

After this, code ran successfuly.

8

µTasker general / Re: Kinetis K60: code imported from TWR-K60D100M to circuit using MK60DX256VLL10

« on: June 07, 2021, 06:59:05 PM »

Where can I find these settings in Keil MDk software?

9

µTasker general / Re: Kinetis K60: code imported from TWR-K60D100M to circuit using MK60DX256VLL10

« on: June 06, 2021, 07:07:24 PM »

When target is selected in Keil MDK it automatically adjust these things. Is this not the case? Attached two pictures show that the difference which you are suggesting is there when MK60DN512VMD10 is selected (which is used in development kit) as comapred to MK60DX256VLL10 (used in my circuit). Are there any other settings which needs changing in the code? Is this setting in Keil MDK's target selection enough? If there are changes needed to be done in the code, would you be so kind to point me in that direction.

10

µTasker general / Kinetis K60: code imported from TWR-K60D100M to circuit using MK60DX256VLL10

« on: June 06, 2021, 07:56:38 AM »

I have successfuly run Keil MDK codes provided in "SDK_2.2.0_TWR-K60D100M_board" on TWR-K60D100M-KIT. Now I am trying to write codes for my own design circuit which uses MK60DX256VLL10. In sample code of GPIO, PORTA11 in TWR-K60D100M is used to toggle LED on/off. Now in my own design circuit, same pin PORTA11 is used to toggle LED on/off. The problem is that the code is built successfuly in KEIL MDK 5.34 but when I press the debug button, the code debugs but instead of normal procedure (in which when debug is pressed, code enters in debug mode and you have to press RUN to run the code on your target ) the code shows RUN button as gray (as if without pressing the RUN button, code has entered RUN mode) but nothing happens on design circuit and when I press STOP button, the error appears ( error message is typed in bold as below to distiguish from my question)

Cannot access memory @0x2000fff8, Read, Acc Size: 4 Byte

Cannot access memory @0x2000fffc, Read, Acc Size: 4 Byte

'

'

'

Cannot access memory @0x20011f94, Read, Acc Size: 4 Byte


I have tried to undesrstand this error. 20011f94 minus 2000fff8 = 1F9C = 8092 (decimal) = 8K memory.


Can anybody help me understand this error. Are there any special setting to change in code when exporting from TWR-K60D100M to  MK60DX256VLL10 (apart from target selection in Keil MDK). Project/Code is attached whic is very simple to understand so please have look at it.

11

NXP^TM M522XX, KINETIS and i.MX RT / MK60DX256VLL10 RESET pin

« on: June 01, 2021, 02:25:41 PM »

I have designed a circuit which uses MK60DX256VLL10 based on its development kit "TWR-K60D100M-KIT" . I have pulled up the RESET pin (pn # 52) as shown in figure but when I power up the circuit, RESET pin shows 0.9V due to which this controller is not detected in MCUExpresso for coding. I increased the value of capacitor from 100nF to 300nF but still voltage rises only to 1.1V. Any possible solution for this problem would be highly appreciated.

12

NXP^TM M522XX, KINETIS and i.MX RT / Re: Simulation in MCUXpresso of TWR-K60D100M-KIT board without hardware

« on: May 12, 2021, 04:06:43 PM »

Thank you for your swift response. Will you guide me as to how to simulate TWR-K60D100M in Visual Studio? Or refer me to some document from where I can follow these steps?


Second thing is that "MCULink Debugger" is supported in MCUXpresso IDE and suport devices include K60 as well.

13

NXP^TM M522XX, KINETIS and i.MX RT / Simulation in MCUXpresso of TWR-K60D100M-KIT board without hardware

« on: May 12, 2021, 11:41:14 AM »

I want to test functionalities of TWR-K60D100M-KIT but I don't have the actual hardware of board and I have yet to purchase it. Is there any way to simulate this board in MCUXpreso so that I can test functionalities (SPI, I2C, CAN, GPIOs) of baord before purchasing it?