1
µTasker general / Re: DMA & SPI
« on: July 19, 2013, 08:38:13 PM »
Thanks Mark. Probably Freescale Kinetis would be the best option to do DMA transfer functionalities across the usb/ethernet to SPI master bus.
News:
Nov 2020: uTasker i.MX RT V1.4.12 is productive - with complete secure loading concept.
Follow uTasker updates at www.twitter.com/uTasker !!
Online Forum registration has now been disabled. Please send an email to an address at the bottom of the home page with your preferred user name and email address if you would like an account.
Return to uTasker main site: www.utasker.com
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.
2
µTasker general / DMA & SPI
« on: July 05, 2013, 01:18:55 PM »
Hi,
Does the current uTasker for Freescale MCF5223x supports the DMA transfers to SPI Master?. If so,
1. how to do buffer transfer (perhaps use DMA?)
- from USB to the SPI ?.
- from Ethernet MAC to SPI ?
2. Does the uTasker OS support variable clock speeds on the SPI interface? What is the granularity? What is the min speed?
3. Does that above feature works for uTasker OS on STM32F407 as well ?/
Thanks.
Does the current uTasker for Freescale MCF5223x supports the DMA transfers to SPI Master?. If so,
1. how to do buffer transfer (perhaps use DMA?)
- from USB to the SPI ?.
- from Ethernet MAC to SPI ?
2. Does the uTasker OS support variable clock speeds on the SPI interface? What is the granularity? What is the min speed?
3. Does that above feature works for uTasker OS on STM32F407 as well ?/
Thanks.
3
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 23, 2012, 12:34:33 PM »
Hi Mark,
The problem is fixed.
As you said, CS line was set to wrong bit of PORT_QS. In the earlier version of the code ( uTasker v1.4.0), CS0_LINE was mapped against PORT_QS_BIT3, but it has been changed to PORT_QS_BIT5.
Thanks for your support.
Cheers
The problem is fixed.
As you said, CS line was set to wrong bit of PORT_QS. In the earlier version of the code ( uTasker v1.4.0), CS0_LINE was mapped against PORT_QS_BIT3, but it has been changed to PORT_QS_BIT5.
Thanks for your support.
Cheers
4
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 14, 2012, 12:29:48 PM »
Hi Mark,
I don't see the board gets reset, because after CTRL+C, the board is still reachable. Let me check whether SPI is detected or not ?,.
I don't see the board gets reset, because after CTRL+C, the board is still reachable. Let me check whether SPI is detected or not ?,.
5
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 13, 2012, 11:07:53 AM »
I have attached the pcap file which was captured when the "dir" command was issued after logging-in FTP. 192.168.15.109 is the device IP address.
6
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 12, 2012, 07:54:06 PM »
Hi Mark,
Please find attached the header files config.h ,app_hw_m5223x.h and the linker file. The target is 52232 with STM25P16 SPI flash.
I haven't taken the patch code for TCP and fnEraseFlashSector(). I will try with this patch ( I am not using IPV6, so TCP patch may not be relevant ). Let me try with the patch and post you the status.
I also tried with simulator, but did't see any problems. Both FTP and webserver works.
Thanks.
Please find attached the header files config.h ,app_hw_m5223x.h and the linker file. The target is 52232 with STM25P16 SPI flash.
I haven't taken the patch code for TCP and fnEraseFlashSector(). I will try with this patch ( I am not using IPV6, so TCP patch may not be relevant ). Let me try with the patch and post you the status.
I also tried with simulator, but did't see any problems. Both FTP and webserver works.
Thanks.
7
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 11, 2012, 11:48:52 PM »
Few more updates on this topic.
1. I have tried with CW 7.1, the behaviour is same. i.e, the filesystem from external SPI flash(M25P16) doesn't work. I can't execute "dir" command in FTP. It hangs. Not able to upload any files.
2. FTP works with internal flash memory ( by disabing SPI_FILE_SYSTEM). But, when I upload(ftp) more than 2K file size ( 3594 bytes) , I can get back only 2k bytes. Files below the size of 2920 bytes can be retrieved safely.
3. During the filesystem testing on internal memory, I have left 24K size for filesystem in the internal memory.
4. Both CW 7.1 and 7.2 works same when the filesystem is tested on external spi flash..
Everything working perfectly fine on uTasker 1.4.0 ( even it is compiled on CW 7.2 ).
1. I have tried with CW 7.1, the behaviour is same. i.e, the filesystem from external SPI flash(M25P16) doesn't work. I can't execute "dir" command in FTP. It hangs. Not able to upload any files.
2. FTP works with internal flash memory ( by disabing SPI_FILE_SYSTEM). But, when I upload(ftp) more than 2K file size ( 3594 bytes) , I can get back only 2k bytes. Files below the size of 2920 bytes can be retrieved safely.
3. During the filesystem testing on internal memory, I have left 24K size for filesystem in the internal memory.
4. Both CW 7.1 and 7.2 works same when the filesystem is tested on external spi flash..
Everything working perfectly fine on uTasker 1.4.0 ( even it is compiled on CW 7.2 ).
8
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 10, 2012, 11:57:21 PM »
Hi Mark,
I tried with the workournd, but no luck. I am using Codewarrior 7.2. I don't have any problem with uTasker v1.4.0 ( haven't tried the other versions ).
- Franklin
I tried with the workournd, but no luck. I am using Codewarrior 7.2. I don't have any problem with uTasker v1.4.0 ( haven't tried the other versions ).
- Franklin
9
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: November 07, 2012, 04:28:59 PM »
Hi Mark,
I have tried the latest code ( v1.4.11) with the CodeWarrior. I am able to bring-up the application in the following scenario.
1. Bootloader, built using uTasker v1.4.0
2. BareMinimum image built using uTasker v1.4.0.
3. Upgraded application, built using uTasker 1.4.11.
After the new image is up and ready, FTP and Webinterface didn't work.
In FTP case, i can login the device, but failed to execute "dir" command. Also, not able PUT any files.
In webserver, nothing works ( since not able to upload any files via FTP ).
so, in a nutshell, I can upgrade the image ( which is built using v1.4.11) from the earlier version of the uTasker image ( built using v1.4.0). The bootloader was built using v1..4.0. ( in fact I don't want replace the existing bootloader).
Running the latest uTasker via Simulator works fine with FTP and webserver files. So, time being, I would like to solve the CodeWarrior problem, then move onto GNU.
In the configuration side, both FLASH_FILE_SYSTEM and SPI_FILE_SYSTEM are enabled in addition with SPI_FLASH_STM25P16. The relevant flags which points MCF52232 also enabled.
Please note that uTasker v1.4.0 works fine in all the cases ( ftp, web, upgrade etc ).
I have tried the latest code ( v1.4.11) with the CodeWarrior. I am able to bring-up the application in the following scenario.
1. Bootloader, built using uTasker v1.4.0
2. BareMinimum image built using uTasker v1.4.0.
3. Upgraded application, built using uTasker 1.4.11.
After the new image is up and ready, FTP and Webinterface didn't work.
In FTP case, i can login the device, but failed to execute "dir" command. Also, not able PUT any files.
In webserver, nothing works ( since not able to upload any files via FTP ).
so, in a nutshell, I can upgrade the image ( which is built using v1.4.11) from the earlier version of the uTasker image ( built using v1.4.0). The bootloader was built using v1..4.0. ( in fact I don't want replace the existing bootloader).
Running the latest uTasker via Simulator works fine with FTP and webserver files. So, time being, I would like to solve the CodeWarrior problem, then move onto GNU.
In the configuration side, both FLASH_FILE_SYSTEM and SPI_FILE_SYSTEM are enabled in addition with SPI_FLASH_STM25P16. The relevant flags which points MCF52232 also enabled.
Please note that uTasker v1.4.0 works fine in all the cases ( ftp, web, upgrade etc ).
10
NXPTM M522XX, KINETIS and i.MX RT / uTasker FileSystem with FTP
« on: October 31, 2012, 01:00:02 PM »
Hi,
I have MCF52232 based custom board with STM25P16 SPI flash.
In one of my earlier attempt, I built the uTasker v1.4.0 image with Codesourcery GNU tool chain. The board was successfully brought-up with this image. Once it is done, I tried to upgrade newer image ( which was built using same codesourcery, with the size of 85KB), the upgrade never happened.
During my investigation, I tried to upload the HS.BIN image via FTP. I would expect this image will occupy location "H" and "I". in the file system. When I tried to get the FTP image using "GET" command of ftp, I can fetch only 64K of the image.
ftp> put H_Upload_Enc.bin
200 OK.
150 Data.
226 OK.
ftp: 88506 bytes sent in 0.35Seconds 252.15Kbytes/sec.
ftp> get H.BIN
200 OK.
150 Data.
226 OK.
ftp: 65531 bytes received in 0.18Seconds 362.05Kbytes/sec.
Could you please help me to understand this problem, why I couldn't fetch the entire file ?. I believe the bootloader is failed to load the entire file from the uTasker file system into the internal flash ( location 0x1000).
I have MCF52232 based custom board with STM25P16 SPI flash.
In one of my earlier attempt, I built the uTasker v1.4.0 image with Codesourcery GNU tool chain. The board was successfully brought-up with this image. Once it is done, I tried to upgrade newer image ( which was built using same codesourcery, with the size of 85KB), the upgrade never happened.
During my investigation, I tried to upload the HS.BIN image via FTP. I would expect this image will occupy location "H" and "I". in the file system. When I tried to get the FTP image using "GET" command of ftp, I can fetch only 64K of the image.
ftp> put H_Upload_Enc.bin
200 OK.
150 Data.
226 OK.
ftp: 88506 bytes sent in 0.35Seconds 252.15Kbytes/sec.
ftp> get H.BIN
200 OK.
150 Data.
226 OK.
ftp: 65531 bytes received in 0.18Seconds 362.05Kbytes/sec.
Could you please help me to understand this problem, why I couldn't fetch the entire file ?. I believe the bootloader is failed to load the entire file from the uTasker file system into the internal flash ( location 0x1000).
11
NXPTM M522XX, KINETIS and i.MX RT / Re: Latest uTasker code for M522XX with GNU compilation
« on: October 24, 2012, 07:26:37 PM »
Hi Mark,
I tried with the latest uTasker code on my custom board ( based on MCF52232 with STM25P16 SPI flash). I couldn't get the uTasker working in my board.
Not sure where to start..
I tried with the latest uTasker code on my custom board ( based on MCF52232 with STM25P16 SPI flash). I couldn't get the uTasker working in my board.
Not sure where to start..
12
NXPTM M522XX, KINETIS and i.MX RT / Latest uTasker code for M522XX with GNU compilation
« on: October 16, 2012, 11:16:49 PM »
Hi Mark,
What is the latest uTasker code for M522XX processor ?. Can you please let me know your recommended GNU tool chain as well ?. I am not planning to use Code Warrior.
Thanks
What is the latest uTasker code for M522XX processor ?. Can you please let me know your recommended GNU tool chain as well ?. I am not planning to use Code Warrior.
Thanks
13
NXPTM M522XX, KINETIS and i.MX RT / Re: Failed to upgrade image which was built using Codesourcery G++ Lite
« on: July 13, 2011, 10:09:19 PM »
In my case, UTASKER_APP_START is assigned with 0x1000 in uTaskerBootLoader.c file.
When I compiled the uTasker project in Codewarrior, I was using the following setting in M52235EVB_BOOT_APP_FLASH_SPI.lcf file.
MEMORY
{
flash (RX) : ORIGIN = 0x00001000, LENGTH = 0x0001F000 /* 4k reserved for SPI FLASH boot loader */
vectorram(RWX) : ORIGIN = 0x20000000, LENGTH = 0x00000400
sram (RWX) : ORIGIN = 0x20000400, LENGTH = 0x00007C00
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
( this works ).
So the equivalent GNU linker script has the following setting.
MEMORY
{
rom (rx) : ORIGIN = 0x1000, LENGTH = 124K
vectorram(RWX) : ORIGIN = 512M, LENGTH = 0x00000400
ram (rwx) : ORIGIN = 512M + 0x400, LENGTH = 32K - 0x400
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
which doesn't work.
Hopefully I am not missing anything.
When I compiled the uTasker project in Codewarrior, I was using the following setting in M52235EVB_BOOT_APP_FLASH_SPI.lcf file.
MEMORY
{
flash (RX) : ORIGIN = 0x00001000, LENGTH = 0x0001F000 /* 4k reserved for SPI FLASH boot loader */
vectorram(RWX) : ORIGIN = 0x20000000, LENGTH = 0x00000400
sram (RWX) : ORIGIN = 0x20000400, LENGTH = 0x00007C00
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
( this works ).
So the equivalent GNU linker script has the following setting.
MEMORY
{
rom (rx) : ORIGIN = 0x1000, LENGTH = 124K
vectorram(RWX) : ORIGIN = 512M, LENGTH = 0x00000400
ram (rwx) : ORIGIN = 512M + 0x400, LENGTH = 32K - 0x400
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
which doesn't work.
Hopefully I am not missing anything.
14
NXPTM M522XX, KINETIS and i.MX RT / Re: Failed to upgrade image which was built using Codesourcery G++ Lite
« on: July 12, 2011, 11:39:43 PM »
all I did was changing the below table
MEMORY
{
rom (rx) : ORIGIN = 0, LENGTH = 256K
vectorram(RWX) : ORIGIN = 512M, LENGTH = 0x00000400
ram (rwx) : ORIGIN = 512M + 0x400, LENGTH = 32K - 0x400
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
with
MEMORY
{
rom (rx) : ORIGIN = 0x1000, LENGTH = 124K
vectorram(RWX) : ORIGIN = 512M, LENGTH = 0x00000400
ram (rwx) : ORIGIN = 512M + 0x400, LENGTH = 32K - 0x400
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
but still it didn't work. It looks like the boot loader loads the image (i believe it must have been upgraded the new firmware in the flash ).
- Frank
MEMORY
{
rom (rx) : ORIGIN = 0, LENGTH = 256K
vectorram(RWX) : ORIGIN = 512M, LENGTH = 0x00000400
ram (rwx) : ORIGIN = 512M + 0x400, LENGTH = 32K - 0x400
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
with
MEMORY
{
rom (rx) : ORIGIN = 0x1000, LENGTH = 124K
vectorram(RWX) : ORIGIN = 512M, LENGTH = 0x00000400
ram (rwx) : ORIGIN = 512M + 0x400, LENGTH = 32K - 0x400
ipsbar (RWX) : ORIGIN = 0x40000000, LENGTH = 0x0
}
but still it didn't work. It looks like the boot loader loads the image (i believe it must have been upgraded the new firmware in the flash ).
- Frank
15
NXPTM M522XX, KINETIS and i.MX RT / Re: Failed to upgrade image which was built using Codesourcery G++ Lite
« on: July 12, 2011, 11:34:11 PM »
Hi Mark,
There are multiple linker scripts used in the makefile ( make_uTaserV1). Should I refer m52235evb-rom.ld ( for upgrade image ) ? .
Regards
Frank
There are multiple linker scripts used in the makefile ( make_uTaserV1). Should I refer m52235evb-rom.ld ( for upgrade image ) ? .
Regards
Frank