> That looks like a bug. Could you try and see if
> tcpborphserver2-2010-10-18-r3340-parsefix fixes that?
Yep. That fixed it. Thanks, Marc.
Sean
> Hi there
>
>> We recently upgraded to the newest version of tcpborphserver
>> (tcpborphserver-2.3304 2010-08-27) and have discovered that we can no
>> longer write to DRAM. Specifically, tcpborphserver crashes on the roach
>> when we try to use the Python KATCP command write('dram_memory', data).
>> We switched back to the previous version,
>> tcpborphserver2-2010-04-02-tgtap, and it works. Both versions also work
>> when writing to registers or BRAM.
>
> That looks like a bug. Could you try and see if
> tcpborphserver2-2010-10-18-r3340-parsefix fixes that ?
>
> Heads up: The format of the log and version messages has changed
> a bit - it now announces the mode ("raw") rather than poco (for POcket
> COrrelator). Apologies for the inconvenience.
>
> regards
>
> marc
>
