CCS/AWR1642BOOST: Modify the size of gSwUserBuffer in SRR demo(TIDEP-0092)

Note: my comments below are based on oob demo, I am assuming that the LVDS part of oob demo was carried in the SRR demo. [I do not officially support SRR demo]

#1, #2: The CBUFF unit dictates the maximum size which is 0x3FFF CBUFF units. 1 cbuff unit = 2 bytes. So maximum user buffer size you can transmit (including header sizes) is 32766 bytes. The division by 2 is to convert bytes (sizeof()) to CBUFF units. Your uint16_t x[8192] will be a size of 16384 bytes or 8192 CBUFF units which is below the limit so should not have given any problems, we have not tried this large size ourselves, so you will have to spend some time to debug why you see COM port failure. The COM port failure does not make sense, perhaps the large buffer is producing is exposing some problem due to memory map shift [this is pure speculation at this point]. You express your intent of sending 32KB = 32768 bytes [uint16_t x[16384]) which exceeds the CBUFF limit, so if you attempted to do this, the CBUFF driver will give you an error [see code CBUFF_validateBufferCfg in cbuff driver]. Assuming application code is acting on error (i.e not ignoring it), you will see that violation reported by your application.

If you want to send more than CBUFF limit, you can a) Add another user buffer [max number of user buffers supported is 3 in the driver] and give half your buffer in one user buffer and half in the other one [assuming each half obeys the limit] or b) you can terminate and re-create s/w session (in each frame) to send the big buffer in parts. We have ourselves not tried any of these so we cannot say for certain you will not hit any issues but you can give it a try.