SCIB on the 28069

Hi VB,

According to the case described above, this seems to be an initialization error or lack of initialization variables. Please attach a sample modified code and init files for locating the bug.

Regards,

Gautam Iyer

Thanks for the quick response.

But it works if I change the mux to use Pins 9 and 11 (change only in the InitScibGPIO function). If the problem is in my code, how is this possible?

Vaidi.

Sorry Gautam, I used GPIO9 and GPIO11 (not pins 9,11 on the device)

Hi VB,

So has this solved you issue ???

Regards,

Gautam

Gautam,

Fixed the problem. There is a bug in Example2806xSci_FFDLB project, F2806x_sci.c in the function InitScibGPIO():

All entries choosing pins GPIO22 and GPIO23 are set as 2 - they must be 3. Since for other pins, the mux position is 10(binary) for enable sci functionality on the pin, but for these pins, the mux should be set to 11(b) i.e. 3.

We changed the code and now scib is working for us on GPIO22 and GPIO23!

Do I get extra points for finding out this bug?

Vaidi.

Good VB, finally it was an initialization error as i had proposed :)

Vaidi,

Did you use controlSUITE to find this examples?  If so, what version of device_support\f2806x did you use which shows the error? 

I do not see the issue that you've described in the current version of f2806x device_support.


Thank you,
Brett

Dear Brett,

I am slightly confused: I have control suite installed on 2 computers - in one of them the file F2806x_sci.c under V100 folder has got all registers set to 2, and in the other it is proper. In the V130 folder, all are proper.

The sequence was: we tested our board on 1 pc with SCIA. We then copied our project folder to the new PC and then imported it. We modifed to use SCIB, we came across this issue. Since we were already using some other examples from V100, we continued with V100 on the new PC.

The control suite installation was from the same zip file (Jan 2011 release).

What could be the issue? Did we do anything wrong?

Regards,

Vaidi.

Vaidi,

I cannot explain this.  In my opinion is that, on the computer with the bad code, your source got mistakenly edited or got corrupted from a project that also uses the same copy of the F2806x_Sci.c file.

When able and you have the ability to test your software, I might recommend using/updating your project to use the most up-to-date version of device_support (we are now on f2806x device_support v136).  Bugs similar to this are exactly what makes up the majority of fixes from version to version.

Good luck on your project!


Thank you,
Brett

Brett,

looks like the control suite code got edited some time in the past.

Yesterday, one more issue surfaced:

The situation is like this: We have a 28069 board with MODBUS running on SCIA through RS485. This code when downloaded from one PC with CCS 4.2 and V100 control suite, works properly.

I copy the project into the other PC with CCSV5.3 then downloaded, the MODBUS does not work - when stepped thorugh we just get 1 byte after that all bytes are either 0's or FFs.

I suspected baudrate issue, so I changed the code to just reflect bytes on the serial port, connected to a PC (through an RS485 converter), and it works properly with a terminal emulator (Hyperterminal).

Any ideas as to where I can look for the problem?

Vaidi.

Vaidi,

I would recommend starting a new thread at this point.

-----

Assuming the MODBUS code is your own code, I would recommend making several smaller jumps (as opposed to one big jump) to get your code to the other computer.
PC1; CCS4.2; V100 controlSUITE->  PC2; CCS5.3; unknown cSUITE

I would recommend installing CCS5.3 onto PC1 and then trying it there.  Next make sure the cSUITE version is the same on PC1 as what will be on PC2. This will reduce the scope of your problem and hopefully lead you to the resolution.


Thank you,
Brett