Recent Posts

Pages: [1] 2 3 ... 10
1
µTasker general / Re: How to distribute my application as a uTasker Simulation?
« Last post by mark on September 15, 2021, 04:35:00 AM »
Yes, that is correct - if you have a key-pad image (originally it was a key pad but in the meantime is used as a general board image for I/O visualisation) it needs to be bundled in the directory that you state. By distributing a zipped image of the directories and files it can be unzipped and executed.
If you want to distribute with a flash image (eg. a file system for web pages etc.) also the flash_xxx.ini can be included so that it loads the internal (or SPi flash, or SD card or memory stick etc.) image when it starts.

The idea is that you can send the project (simulation of "product") so that your customer can test its operation even when the HW is not yet ready - this allows finding deviations from the spec at an early state and have these corrected and verified asap.  It allows front panel and LCD control, various peripherals and networking to be included and test sequences (injecting data on ports or interfaces, for example) to exercise standard operating sequences.

It is one of the main features of the uTasker project but one that is not always given that much attention since many people dismiss simulation as not useful because they are more interested in seeing things running on the HW. But it allows great savings in development time and much more accurate/tested implementations if used as intended.

I am pleased you found it useful.

Regards

Mark
2
µTasker general / Re: How to distribute my application as a uTasker Simulation?
« Last post by tdrobnak on September 14, 2021, 11:36:34 PM »
Thank you, Mark!  I also found that I had to create a directory called "KeyPads" in the application directory (where the uTaskerProject.exe program is located) and put the "FRDM_KE15Z.bmp" in the "KeyPads" directory.  I now have a distributable PC version of my uTasker embedded application which others can use to process the log files using the same (embedded) code that created them.  This is a powerful tool for our application.  My supervisor was very impressed.  The uTasker simulation is really a hidden gem of a feature.  Thank you for designing it in and continuing to support it.
3
µTasker general / Re: How to distribute my application as a uTasker Simulation?
« Last post by mark on September 14, 2021, 11:06:46 PM »
Hi

Add _EXE as a pre-processor define when building the project that you want to distribute.

This will change the path that is used to open the missing image from something like
"..//..//..//Hardware//Kinetis//GUI//kinetis_lan.bmp"
to
"kinetis_lan.bmp"

and allow you to simply 'bundle' the image with the *.exe file. As long as it is in the same directory as the *.exe itself it will be able to load the image.

Regards

Mark

4
µTasker general / How to distribute my application as a uTasker Simulation?
« Last post by tdrobnak on September 14, 2021, 10:46:38 PM »
I would like to build my uTasker application as a distributable simulation on the PC.  I have done this, but the graphics for the Kinetis logo and the FRDM-KE15Z are missing when it is built using a setup project in Visual Studio 2017.  Does anyone know what I need to add to the VS setup project to add the missing graphics.  Also where are the missing items located in the uTasker directory?  I am sure there is a message on this forum that has this information on what is needed, but I cannot find it.  If you know where the message is, please send a link to it.

Thank you
5
µTasker general / Re: IAR EWARM v9 Support
« Last post by BrandonT on July 22, 2021, 01:25:13 PM »
I can confirm that IAR EWARM 9.10 does indeed work as expected.

I did, however, find that the IAR EWARM flashloader balked when attempting to flash my binary to the K60. I was able to determine that the flashloader was failing to handle the f_config section.

In order to allow the flashloader to write flash configuration, I had to modify the existing board file it used. I had to add the --enable_config_write parameter as indicated in the attached file: 
6
µTasker general / Re: IAR EWARM v9 Support
« Last post by mark on July 21, 2021, 02:37:19 PM »
Hi

I have been using 8.50.9.
From experience the exact version shouldn't make any noticeable difference - no code changes have been made for IAR since initial IAR 4 compatibility and the new IAR versions generally are due to changes in he IDE itself (editor, debugger) and the additional of more processor types that it supports.
In addition since the move form IAR4 to IAR5 (which lost compatibility with the IDE projects) subsequent generations have always been backward compatible.

Regards

Mark
7
µTasker general / IAR EWARM v9 Support
« Last post by BrandonT on July 21, 2021, 07:59:39 AM »
What is the latest version of IAR EWARM against which the pre-configured projects have been qualified? I am currently using IAR EWARM 9.10.
8
USB / Re: USB on Windows 10
« Last post by Phil on July 13, 2021, 11:52:49 PM »
Mark,

Thank you. However, this did not resolve the problem.  I will come back to this later and step through the code and report.  It is also obvious that I need to update my copy of uTasker.

I will report back once I get my copy updated to the latest version of uTasker and I have walked through the code.

Best regards,

Phil
9
NXPTM M522XX, KINETIS and i.MX RT / Re: SD Card Format Speed
« Last post by AlexS on July 13, 2021, 07:21:52 PM »
1. It takes about 8ms per run of fnMassStorage() task with 4ms in between iterations. This is how I'm starting the format:
Code: [Select]
utFormat(DISK_SDCARD, VOLUME_LABEL_STR, UTFAT_REFORMAT | UTFAT_FORMAT_32)
2. Is there any specific routines that must be called after the format completes?  I'm calling utAllocateDirectory() after detecting that the disk is mounted again and getting '0' returned.

Alex

10
NXPTM M522XX, KINETIS and i.MX RT / Re: SD Card Format Speed
« Last post by mark on July 13, 2021, 07:13:20 PM »
Alex

That is a long time for the formatting to take - I expect maybe 30s or a minute if doing a quick format (which deletes the FAT but not all sectors - a full format (also wiping out old data in the sectors) will take a lot longer.

The mass storage task will be doing this by deleting a sector at a time and the sector writes (setting content to 0) will usually take about 4ms each. Then the task allows other tasks to run and continues with the next, repeating until finished.

What is the time gap between each iteration? Is there something running between each which slows the overall operation?

Ultimately the format time is the sum of the time to erase each sector in the FAT table (whereby there are 2 copies maintained and so the overall time is double) plus any other time added between iterations.

Regards

Mark

Pages: [1] 2 3 ... 10