Hi, @venkatm,
Could you verify what is the download method configured in your Simulink example?
By default, the examples delivered with our toolbox are set on OpenSDA.
In this case, you have to ensure a USB connection between the evaluation board's OpenSDA port and your computer. Using this method, our script copies the executable .bin file to the evaluation board's OpenSDA drive, in my case, drive (D:).
You could also try to manually copy the .bin to the drive associated with your evaluation board.
This way, we can determine if there is a problem with our download script or the OpenSDA's bootloader needs an update.
Best regrads,
Victor
Hi, @venkatm,
The next step that we will need to follow is to verify your current bootloader version on the I.MX RT1010 board. To do that, open the DETAILS.TXT file from the virtual drive associated with your board and check the Bootloader Version and Interface Version fields.
My board has the latest versions for both the Bootloader Version (0244) and the Interface Version (0246).
The OpenSDA update procedure can be found on the following NXP page: OpenSDA Serial and Debug Adapter.
Here you can download the latest bootloader firmware (0244) and the latest application firmware (0244)
Tips for the update procedure:
1. To start your board in bootloader mode, you need to set the J27 jumper on 1-2 in order to send the reset signal to the OpenSDA chip. The following picture is from the I.MX RT1010 schematic:
2. The bootloader version can be updated using an external debugger connected to the OpenSDA's JTAG interface found at J16:
3. The application firmware (Interface Version) can be updated by copying the .bin file onto the board's virtual drive when it is in bootloader mode.
Let me know if this helped.
Cheers,
Victor
Hi, @venkatm ,
The evaluation board programming is performed successfully. The download process within our toolbox is followed by a pop-up window that informs the user to reset the board. This Simulink pop-up will not automatically go away after the reset button is pressed and may cause confusion.
The PiL and External Mode functionalities usage with the i.MX RT 1010 EVK require additional steps that need to be performed.
Our toolbox provides a default .mex configuration for i.MX RT1010 that is brought next to a model configured for this microcontroller. The OpenSDA chip uses the LPUART1 instance of the board for the serial communication. In the McuExpresso configuration, the LPUART1 settings has the RX FIFO watermark configuration that is set to 1. This means that the interrupt for data receive will occur only after the watermark value is reached. This setting causes a communication delay between the Simulink environment and the board and finally, a Simulink timeout error.
There are two options to solve the issue:
- replace the default .mex configuration for the i.MX 1010 MCU found in mbdtbx_imxrt\devices\MIMXRT1011 with the attached one (mimxrt1011.mex). In this case, all new models set for this MCU will use the updated configuration file.
- update the RX FIFO watermark configuration in your particular project by pressing the Configure button in one of our blocks to open McuExpresso.
Hope this helps,
Victor
Hi, @venkatm,
I have attached two examples that illustrate the PIL and External Mode functionalities for i.MX RT1010.
To run a PIL simulation, open the evkmimxrt1010_pil_harness model. In the SIL/PIL group, select Model blocks to get the referenced model, evkmimxrt1010_pil_target under test. Make sure that you have previously opened Hardware settings and selected the corresponding COM port in the PIL group for both the harness and target models in accordance with your hardware connection. The OpenSDA download drive has to be selected to download the executable file onto the board. The default LPUART1 instance selected in the model is the same as the one in the configuration project, so there is no need to update it.
The logic of the examples is the same as that of the other hardware parts examples included in the toolbox. You can easily start from another example, update the Hardware Board in the model settings, and refresh the blocks' parameters within the model in accordance with the new configuration.
Let me know if you have managed to successfully run the PiL simulation using your evaluation board.
Cheers,
Victor
