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

Pages: [1] 2
1
Great MARK !!!
I didn't update the SP5 with the service pack note...in particular the point 4. that you have signed in the previous message.

Now I want to understand the differences between the 2 versions..

THANK YOU VERY VERY MUCH

Fabio

2
Perhaps there is some location that I mustn't overwrite, like the 0x400-418.
A register located in the middle of the flash...

I have noted that if in my bootloader I comment all the code, except the jmp 0x5000
(In other words if my bootloader make the only jump instruction to the application program) the application program doesn't go, if it is greater than 128k. If it is less than 128k it goes well.

I think this fact is important to say that it isn't a problem in bootloader but a problem in compiler/linker...some #pragma ...

my little brain is burning...:-)

3
I have noted that it isn't a runtime error, it isn't an error of accessing the flash over the 128k.
But it is an error of the bootloader.
In the first location I have the code, in the higher memory I have the const, the const string that I use to draw the graphics in the display..and these, over the 128k, are written bad from the bootloader. It is very strange

Now I try to define these like "const far" or something of similar...
I don't understand...
bye
Fabio

4
Hi Mark,
1- I think CW is full version because if I compile the 200k of program it goes well, without the bootloader.
2- If I compile a smaller file the program goes well with the bootloader. And I have looked to the flash memory and the bootloader is located in the first locations, and the program is the same in the two different version, it is only shifted of 5000 in the bootlader version...

My bootloader is a semplification of your SPIMODE. I use fyle system instead of the direct hardware command read/write of the spi eeprom..

I have looked to the Device errata, and I have noted you have setted the workaround 1 that is the best solution.

Is there some settings in utasker that reduce the program memory? due to the fact that a
part is for the web pages (I don't use http but it is enabled)
or some settings in the compiler/linker that you don't have considered because utasker don't exceed the 128k because in the FLASHMODE it is considered that the greater part is destinated to the program that must be copied by bootloader?

today I do many test...
Mark, best regards and many thanks to you

Fabio

5
I use MCF52233 (256k of flash) and Codewarrior 6.3
I have a program greater than 128k of flash and this problem:
If I compile from address 0 the program goes well.
If I compile from address 0x5000, because I have implemented a bigger bootlader (sd-card bootloader..), some const (that are allocated over 128k) result corrupted. I can say this because I see on the display some const (graphics) wrong. Variables are well shown on the display.

If I compile from addess 0x5000 and the program is less than 128k it goes well.

Code mode and data mode is already far (32bit)

Can someone help me?
best regards
Fabio

7
NXPTM M522XX, KINETIS and i.MX RT / Re: SD-CARD
« on: November 14, 2007, 09:27:48 AM »
Now I have the time to continue my work with sd-card...
I have to do the sd-card bootloader.
I think I can use the SPI EEPROM file system to start but instead of the spi EEPROM I use the spi sd-card.
A first problem is that at the start of the bootloader it looks for a new file in the sd-card with fat32 so I have to add the 18k of the sdcard file system in the utasker-boot and add 18k to the flash2 in the .lcf file.

Then I have to understand very well how the bootloader works... I try now..but for me is very difficult...

Please MArk, if you have some suggestion please give me.. if you think this is a wrong way...

thank you very much and best regards
Fabio

8
NXPTM M522XX, KINETIS and i.MX RT / Re: default 4 byte integer
« on: November 13, 2007, 05:38:42 PM »
I can confirm that some parts of utasker doesn't go with deselection of 4-byte integer. for example the FTP
So I have corrected the others library

best regards
Fabio

9
NXPTM M522XX, KINETIS and i.MX RT / Re: default 4 byte integer
« on: September 28, 2007, 08:20:10 AM »
Hi Mark.
because the others libraries that I have included in my project and that was originally compiled for a 8bit micro, with the 4byte-integer, don't work...

It seems me too that utasker work also with the 2byte-integer, so I could use this option..but I am a little worry...

regards
Fabio


10
NXPTM M522XX, KINETIS and i.MX RT / default 4 byte integer
« on: September 26, 2007, 08:18:12 AM »
In codewarrior In the project "console debug setting" there is a check box in "Coldfire Processor" that enable or disable 4byte integer. Default an integer use 4byte like in utasker project.
Can I pass to 2byte integer in the utasker project or I will have errors?

best regards
Fabio

11
Perhaps this is obvious, but I have made this little discovery and I hope to help some students that cannot spend much money..
I have bought the MCF52233 DEMO BOARD for 90€.
In this board there is a full MCF52233 system plus a USB-BDM debugger.
If you buy only this USB-BDM debugger from the producer, certanly it has a more beautifull package.. but you pay 250€ !!

If you want use this onboard BDM with your custom circuit (instead of the demo board) it is sufficient:
1- weld few wires from the 26 pin BDM connector on the Demo board to the BDM interface of your circuit
2- Instead of EDSI on the BDM you have to find and connect the TDI/SDI
3- cut the jumper CT1-6 on the demo board to isolate the micro on the demo board.


It is incredible that the USB-BDM plus a Demo board cost much less than the only USB-BDM

bye
Fabio


12
NXPTM M522XX, KINETIS and i.MX RT / Re: SD-CARD
« on: September 21, 2007, 12:47:54 PM »
I have finished with the SD-CARD.
If someone is interested he can found all at
http://sourceforge.net/projects/efsl/

with described all in this post
"EFSL with FREESCALE 52233 and Codewarrior"

best regards
Fabio

13
NXPTM M522XX, KINETIS and i.MX RT / Re: SD-CARD
« on: August 01, 2007, 07:46:01 AM »
I have found an interesting library in sourceforge.net
"efsl.0-2-8"
The library currently supports FAT12/16/32 reading & writing on SD-cards, I try to use this and convert for codewarrior..
Regards
Fabio

14
NXPTM M522XX, KINETIS and i.MX RT / SD-CARD
« on: July 30, 2007, 04:40:08 PM »
Hello
I have a communication with SD-card with FAT and bootloader too to do with M52233.
if someone has some libraries that I can use to start..will be very appreciate...

best regards

Fabio

15
µTasker general / Re: tftp tests
« on: July 30, 2007, 04:35:48 PM »
Thank you Mark.
Now it is ok! I have disabled the   //#define USE_DHCP,
installed a free TFTP server called TFTPD32.exe and the demo go well, it has transferred the file text1.txt to the server.

Now I'd like transfer a file to the target and make with this a TFTP bootloader...
If you have any suggestion it will be very appreciate, sorry if it is out-of-topic...

best regards
Fabio

Pages: [1] 2