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

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / Re: Parameter Storage
« on: September 14, 2008, 09:42:52 PM »
Thanks, I will give it a try.

2
NXPTM M522XX, KINETIS and i.MX RT / Re: Parameter Storage
« on: September 14, 2008, 09:11:50 PM »
Thanks for the quick response. So if I remain with SP7, It should work as long as I set the FILE_SYSTEM_SIZE to 0 and the start address to 0x3f000.  Is that right?  There is no PARAMETER_BLOCK_START in SP7?

3
NXPTM M522XX, KINETIS and i.MX RT / Parameter Storage
« on: September 14, 2008, 06:19:03 PM »
Hi,
I am needing to setup the project to store 1K of parameters but do not need to use the file system.  It looks like they are one in the same.  Is this is true?  What values do I need to change in order to set this up so my code space is maximized and my parameters can be stored in internal flash at the very end.

Thanks,

4
NXPTM M522XX, KINETIS and i.MX RT / Serial Upload
« on: August 21, 2008, 04:41:05 AM »
Hi Mark,
In your bootload documentation, it talks about having the ability to serially upload a new image. In my application, I do not have Ethernet capability.  I need a way to connect to Uart 0 and upload a new image through the serial port.  Is that what you were refering to?  I don't have External SPI Flash but I do have IIC EEPROM.  I was wondering if there was a way to send the image serially to the IIC EEPROM and then have it read the new image from there and upload on the next reset. I understand that I will have to write the IIC part for the external memory but I was wondering if the Serial Loader described below was documented or sampled somewhere?

Quote
?Tasker boot-loader strategies
The ?Tasker boot-loader strategy can be configured depending on the project requirements.
The following options are possible:
· TFTP upload support integrated in the boot loader (Ethernet, ARP and UDP)
· Serial loader support integrated in the boot loader
· Override options to force serial or TFTP uploads (eg. Input port state at reset)
· Override of IP configuration option (eg. Input port state at reset) to enable a board
with unknown configuration to be contactable via Ethernet – useful mainly together
with TFTP support
· ?Tasker “bare-minimum” loader

Thanks for your help,

5
µTasker general / Multiple Tasks
« on: August 15, 2008, 02:36:51 PM »
Is it possible to schedule an already scheduled tasks so it runs again a little bit later.  For example, I need one task to have multiple purposes.  I need to schedule the task once for purpose A and before A is able to run I need to schedule the tasks for purpose B.  I still need both of them to run in the order they were scheduled but I don't want A to get canceled since I "rescheduled" the task.  Is this possible?

thanks,

6
NXPTM M522XX, KINETIS and i.MX RT / Re: IIC
« on: August 08, 2008, 09:39:43 PM »
Thanks Mark.

On a side note, If I want to use string.h and stdlib.h functions, is it ok to add those Libraries and if so, do you know how to do that in Codewarrior?  I will create a new thread if need be.

thanks again for your fast response.

7
NXPTM M522XX, KINETIS and i.MX RT / IIC
« on: August 08, 2008, 04:31:03 PM »
Is there an example somewhere of how to setup and read from multiple slaves?  For example, I have a temp sensor and an external RTC that are both on the IIC bus.  I have read the IIC pdf but I am still unsure of how to read from both of them.  In this example, the RTC has a slave address of 0x68 and the temp sensor has an address of 0x49.  Do I need to open two interfaces or can one interface talk with multiple slaves. 

Thanks,

8
NXPTM M522XX, KINETIS and i.MX RT / Re: IRQ Test
« on: August 01, 2008, 08:52:26 PM »
Thanks Mark, I had to add POWER_UP(POWER_EPORT);  in the fnConfigureInterrupt.

9
NXPTM M522XX, KINETIS and i.MX RT / IRQ Test
« on: July 31, 2008, 10:29:47 PM »
If I uncomment #define IRQ_TEST   in application.c, then this should enable the IRQtest.  With the Eval board, sw2 should be mapped to IRQ11.  In the IRQ_TEST it looks like if i press sw2 on the eval board, it should printout to the terminal "IRQ_11"  I am not seeing this.  Is there something else I am missing that needs to be defined before this test will run.

Thanks,

10
NXPTM M522XX, KINETIS and i.MX RT / Re: Debug settings for the Uart
« on: July 31, 2008, 09:02:10 PM »
Thanks Dan,
If it was a snake it would have bit me!

11
NXPTM M522XX, KINETIS and i.MX RT / Debug settings for the Uart
« on: July 29, 2008, 12:28:38 AM »
I am trying to follow the document "First Steps for new users" to simply put a "hello world" printout task in the supplied demo project.  I have the Eval board for the 52235.  I am not using the TCP stack so Ethernet is not defined.  I am able to compile and load on the board but nothing is coming out of port 0.  I do not see where baud rates and other settings are setup for the debug port. I want to test it by looking at hyperterminal but do not know what settings to set it up with. I do have the line #define SERIAL_INTERFACE in config.h.  Please help.  I am admittedly a newbie on any embedded OS.

Thanks,

Pages: [1]