RE: Project "code name" PostScript 011

COMPACT — Mon, 16 Jul 2012 22:07:40 GMT

Hi DAB,

The buffer issues are only related to the CC3000 Buffer allocated and within the MSP430 used in the Basic Wi-Fi Demo and not the additional FRAM Buffer.

What I have worked out thus far is the buffer needs to larger than the original value 5 and no greater than 256.

I've been getting everything else working and have not had the opportunity to look further into the reasons why.

I just looked up TI e2e forum and it mentions that the minimum buffer size for the current driver is 119 bytes.

With a bit of effort I think I will be able to find the cause and expand the buffer as necessary up to Wi-FI's MTU of 7981 bytes.

(I didn't realise Wi-Fi datagrams could be so big!)

Cheers

Very Compact

RE: Project "code name" PostScript 011

DAB — Mon, 16 Jul 2012 20:33:07 GMT

If you get some time, I think you can decouple these events to get a better control and a smoother transition between the various tasks.

The MSP430 provides a great set of independently operable timers and event triggered ISR options. By using the full device capabilities, you can decouple the events into a cleaner structure, which might also alleviate some of your buffer issues.

Just a thought,

DAB