NetBurner Community Forum

Hello, I have switched from MOD5234 to MOD54415. It becomes not clear to me, if the Adress/Data Pins are directly connected to the CPU or they are latched. If the reference manual is the following statement: "An address bus latch is included on the MOD54415 so you do not need to add an external...

Hello,
does anybody have a pinout / functional description of the 26pin unused header of the MOD54415 Board?
Maybe some of the pins can be used for more I/O to the processor.

Kind regards

Reinhard

I have tested the behaviour with the development board and pull down resistors. The first RTS is activated 1.3ms after power up, the second one is activated about 500us later. I have checked it with an oscilloscope.

I think the default pin configuration is for use with the serial ports. This is exactly the problem. From powerup, these lines should be GPIO (Freescale documentation). Then these lines are configured from the boot code as outputs in high state. Then the system wait 2 seconds until the start of my ...

Hello, according the MC5234 documentation, the U0RTS (Pin 38) and U1RTS (Pin 23) should be configured as GPIO Inputs. Unfortunately, these lines are driven high shortly after power up of the MOD 5234 and then they are enabling the driver of a RS485 Half-Duplex bus. As an result, the bus is blocked. ...

There is also an UDP-Task running at prio 35.
The task itself is running, because I can receive Data, but the breakpoints do not work.

Reinhard

Hello, The debugger will not recognize breakpoint in my initiated thread "TcpServerTask", (prio=49). I have tested the original TCP/IP-demo with breakpoints working within "TCPServerTask". Then I copied the code in my application, but within the thread "TcpServerTask", ...