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

Pages: 1 [2] 3
16
Hi mark

I resolved the PHY adress reading issue, in fact the problem was caused by a capacitor on the reset line of the PHY , utasker try to read the value meanwhile the PHY is under reset.

Removing the capacitor have resolved the problem.

But i still had some connection problem when i connect directly the board to my computer and i don't have any idea from it come from.

Best regard

17
Hi mark thanks for your answer

I use a M52259 chip on a custom board but i also have the 52259 demo board.

My custom board use the same external PHY than the one used in the demo board , in fact i reuse the hardware design of the demo board for the ethernet part.

When i try the same program on my board and on the demo board for a direct connection test, the demo board work but no my board, and if i plug them on a switch they will both work.

I've tried many parameter like sepcify the speed, disable the full_duplex but they won't change anything.

One strange thing with utasker and my board is that utasker is don't be able to read PHY adresse during initialisation phase and return a 0xFFFFFFFF adress and so on shut down the ethernet so i forced to bypass this test to enable ethernet.

I don't think's it's involved in the probleme but i'm no sure.

Best regard   

18
NXPTM M522XX, KINETIS and i.MX RT / ethernet direct connection problem
« on: February 24, 2010, 04:06:00 PM »
Hi

I actually try the utasker demo with the web server, when i plug the board and my computer to a switch everything work's fine, the ftp and the web server.
But when i connect directly the board to the computer with a crossover cable the connection is unstable and some time i lost the connection when i tried to access to the web server.

When i look what happen with wireshark it seem that some tcp segment was lost.

Did they have some special option to set for a direct connection ?

Thank's

19
utFAT / Initialisation failure
« on: February 23, 2010, 05:19:39 PM »
Hi

I'm trying to use utFAT with the demo provided with utasker.

But during the card initialisation the command ACMD41 return an error, i read the SDRAM datasheet but i don't see why this command could give an error.
As this state of the initialisation the voltage and the card version was already checked.
The problem could be caused by an incompatible card ?


Thank's 

20
NXPTM M522XX, KINETIS and i.MX RT / Re: Utasker interrupt handle
« on: July 23, 2008, 02:17:54 PM »
Thank's mark

the idea to use a timer to generate an interupt, and in this interupt store the data was good but i could be sur that an other utasker interupt was not allready activate when the timer interupt occured.
The priority of this application is to do a sample every 10µs so i need to be sur that the timer interupt would be take in care by the system a soon as they apear.
The solution of the dma see better, I will look on it.

 

21
NXPTM M522XX, KINETIS and i.MX RT / Utasker interrupt handle
« on: July 23, 2008, 08:39:32 AM »
Hi mark

The idea is to sample a data every 10µs, when it's done in the scan complete interupt i would like to store the data and drive an output.

So my question is :

- Where is the interupt handle called when a scan is complet ?
I think's is _ADC_convertA_interrupt bu I'm not certain.

Code: [Select]
adc_setup.int_type = ADC_INTERRUPT;                                  // identifier when configuring
    adc_setup.int_adc_bit = 7;                                        // ADC channel 7
    adc_setup.int_adc_mode = (ADC_CONFIGURE_ADC | ADC_CONFIGURE_CHANNEL | ADC_SEQUENTIAL_MODE | ADC_SINGLE_ENDED | ADC_LOOP_MODE | ADC_START_OPERATION); // single ended configuration in loop mode
    adc_setup.int_adc_speed = (unsigned char)(BUS_CLOCK/100000);         // 100KHz sampling (must be between 100kHz and 5MHz)
    adc_setup.int_priority = CAN15_INTERRUPT_PRIORITY; // Priorité de l'interuption généré
    adc_setup.int_adc_int_type = ADC_END_OF_SCAN_INT;                    // Interuption a la fin de chaque echantillonage
    fnConfigureInterrupt((void *)&adc_setup);                            // configure and start operation
 

I do it but i'm no certain to go in the right way

Thank's mark

22
NXPTM M522XX, KINETIS and i.MX RT / SPI Crash
« on: June 30, 2008, 02:32:21 PM »
Hi mark

I tried to use the SPI and the file system too, to put the file system in the spi flash.
I got a ST 25P16 spi memory on my personal board so i use the setting included for this memory on my project and when i tried to upload a web page into the spi flash the softward crash.

I don't find where the software crash, have you any track i can explore to find why they crash ?

Thank's a lot 
 

23
NXPTM M522XX, KINETIS and i.MX RT / Re: UART Interupt
« on: June 24, 2008, 03:31:35 PM »
Excuse me what do call a "line feed " ?

24
NXPTM M522XX, KINETIS and i.MX RT / UART Interupt
« on: June 23, 2008, 04:11:51 PM »
Hello mark

I trie to generate an interupt on a received data but they don't work.

I configure the handler :

Code: [Select]
extern QUEUE_HANDLE fnSetRS485(unsigned char ucDriverMode, uint8 Baud_rate ,uint8 ER )
{
    TTYTABLE tInterfaceParametersRS485;                                       // table for passing information to driver
    tInterfaceParametersRS485.Channel = RS485_UART;                           // set UART channel for serial use
    tInterfaceParametersRS485.ucSpeed = Baud_rate;   // baud rate
    if(ER == RECEPTION)
    {
    tInterfaceParametersRS485.Task_to_wake = TASK_MODBUS;
    }
    tInterfaceParametersRS485.Rx_tx_sizes.RxQueueSize = MODBUS_RX_BUFFER;       // input buffer size
    tInterfaceParametersRS485.Rx_tx_sizes.TxQueueSize = MODBUS_TX_BUFFER;       // output buffer size                        // wake self when messages have been received
    tInterfaceParametersRS485.usConfig = (CHAR_8 | NO_PARITY | ONE_STOP | NO_HANDSHAKE);
    tInterfaceParametersRS485.ucMessageTerminator = '\r';

    if ((SerialPortID = fnOpen( TYPE_TTY, ucDriverMode, &tInterfaceParametersRS485)) != 0) // open or change the channel with defined configurations (initially inactive)
    {
    if(ER == RECEPTION)
    {
    fnDriver( SerialPortID, ( TX_OFF | RX_ON ), 0 );
    }
    if(ER == EMISSION)
    {
    fnDriver( SerialPortID, ( TX_ON | RX_OFF ), 0 );
   
    if(ER == (EMISSION|RECEPTION ))   
    {
    fnDriver( SerialPortID, ( TX_ON | RX_ON ), 0 );
    }
    }
    return SerialPortID;
}

And in the "TASK_MODBUS" i handle the interupt :

Code: [Select]
void fnTacheModbus(TTASKTABLE *ptrTaskTable)
{
QUEUE_HANDLE        PortIDInternal = ptrTaskTable->TaskID;           // queue ID for task input
    unsigned char       ucInputMessage[RX_BUFFER_SIZE];                  // reserve space for receiving messages
   
    while ( fnRead( PortIDInternal, ucInputMessage, HEADER_LENGTH )) // check input queue
    { 
        switch ( ucInputMessage[MSG_SOURCE_TASK] ) // switch depending on message source
        {                 
        case TIMER_EVENT:
            fnRead( PortIDInternal, ucInputMessage, ucInputMessage[MSG_CONTENT_LENGTH]); // read the complete message
            if ((TIME_OUT_FIN_TRAME == ucInputMessage[0]) || (TIME_OUT_NON_REPONSE == ucInputMessage[0]))
            {
            C_Sys_MaitreModbusSci1_Timeout(); // Lancement de la fonction utiliser pour la gestion des 2 TimeOut
            }
        break;   

        case INTERRUPT_EVENT:   
        C_Sys_ModbusSci1Reception(); // Lancement de la fonction de reception a chaque fois qu'un octet et recu
        break;
       
            default :
            break;
        }
    }
}

But the case INTERRUPT_EVENT is not activate when a data is received on the UART.

Did i forgot something ?

Thank's

25
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader question
« on: June 05, 2008, 01:23:11 PM »
In fact my really probleme is i can't use the code warrior programmer (I got : Error:  System clock check failed  See Details for additional information).

So i use the CFflasher to proramme my board, it work fine with the stand alone code but when i want to programme the bootloader and after the programme code i think's that CFflasher erase the first block and the Bootloader too.

It's possible to load only the bootloader and the programme after by serial interface or ethernet ?
I see you say it's possible but i don't find how to do it ?

Thank's a lot Mark

26
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader question
« on: June 04, 2008, 01:27:57 PM »
Hello have you try to build the bootloader with CW 7.0 ?

If i build the bootloader with CW 7.0 I have a lot of error about size_t.

If I build it with CW 6.4 i teld my that OSCCLK is undefined .

Do you have any idea about that ?

Thank's

27
NXPTM M522XX, KINETIS and i.MX RT / Re: Bootloader question
« on: June 03, 2008, 04:06:29 PM »
Hello

I have many error message with the original bootloader :

did i need to merge the bootloader and the demo project ?

I'm sorry but i don't really understand how that work's

Thank's
 

28
NXPTM M522XX, KINETIS and i.MX RT / Bootloader question
« on: June 03, 2008, 03:28:06 PM »
Hi mark

I read the entire forum but i don't find a answer.

I have personalise the demo for my personal board and they work's fine, now i want to use the softeware udpate feature.

Right now when i building the project i use the M52235EVB_ROM target and it work the boot loader is not include.

If i want to use the bootloader i have juste to choose the bar_min_app_rom right ?

Or i need to do something else ?

Thank's

29
NXPTM M522XX, KINETIS and i.MX RT / Re: SP7 and ADC
« on: June 03, 2008, 03:19:07 PM »
They work's fine thank's a lot mark

30
NXPTM M522XX, KINETIS and i.MX RT / Re: SP7 and ADC
« on: May 30, 2008, 12:48:58 PM »
Thank's oki
in fact in my personal board AN0 TO AN3 are analogique input AN4 to AN6 are digital input and AN7 is an analogique inupt.

When i try to use AN7 alone the soft crash, may be if i configure the all analog input they will work i will try it .

Thank's again

Pages: 1 [2] 3