MSP430FR6989: FLOWESI + MSP-EXP430FR6989 + HID UART

Hi,

Could you help to check the lanuchpad driver, if there are run normal, you are able to see thr below COMx port in device manager of PC:

Thanks!

Best Regards

Johnson

Yes, I can see these two. I also changed the Com13 to com1 but no lack. is it possible that it can't connect because of the java version?

Hi,

This GUI need Jdk v1.6 or higher, do you have install the correct Jdk?

And I would like tto confirm with you that if you can download the code via CCS or IAR.

Thanks!

Best Regards

Johnson

JDK is already installed, because of Android programming. But I download and install JDK ver 15.0.2

The procedure I do is 1) I set up FlowESI with the custom board and all tabs are checked with default parameters.

I check on all output options,
In CCS10 I also alter the LCD.c  and I can see the 0 on the LCD Also I can run the code correctly on the launchpad IF I  DONT CHECK THE UART

2) Code generation tab -> Full CCS project

3) Fron CCS10 file->import

4)Load, also I used the Debug option, to run the code on the launchpad my launchpad is ver 1.1

5) I switch to FlowEsi and I click connect

Going throw the code, In while(1) {.....}  that the launchpad is waiting to get something in the Uart to start

The error above means that FlowEsi can't find the Com port, is that right?

Laptop, the station at home, the station at workoffice  shows the same error

Hi,

This is need USB HID, I think is not the COMx.

I don't have your board, but I know the CapTIvate board, If I don't connect the CAPTIVATE-PGMR board or a bad CAPTIVATE-PGMR board, the similar issue will occur.

When the normal USB HID connected the PC, there are the below port show in Device Manager:

Do you have another board?

Thanks!

Best Regards

Johnson

I look for another USB or hid driver into the TI but there is no such thing. As you see in 1st reply the windows manager reports the same driver as in my picture.

Also, I set an FTDI module (Com10) and I can see the LEDs blinks. I set the application to debug mode and I can receive and transmit.

as you can see in the picture below the MSP Application UART1 has parameters like a legacy com windows port

but the FDTI has complex parameters

Are my Vid and PID numbers correct for the hid driver?

Is there something new about my problem?

Is it possible that Pid and VID numbers at my launchpad to be wrong?

Hi Minas,

I think those FDTI shoud be normal default, and do you change the PC and test again?

Thanks!

Best Regards

Johnson

I test with the laptop and the Pc at my office. Totally 3 different computers have the same behavior. All computers are for programming with visual studio, embedded C, android platform and all updates are installed

Examining the flowesi directory I can see that there is a hid dll inside it.

Also with CCS terminal, I can send a string to the launchpad and catch the input with a breakpoint at the code.

So, the problem is with the hid driver (???) As I can see the VID is 2047 and the Pid 0013 Is the hid driver look for these numbers?

I can think that the author uses the hid driver because it does not need to point which com port to use! Is it possible to ask the author of this program to alter the program to use a common Com port? OR for a new version? as told before I am a "new" at the Ti platform especially with the ESI interface and flowEsi is  "everything I need" to test my newbie code.

Hi Minas,

It looks strange， I will try to test in my PC and get back soon.

Thanks!

Best Regards

Johnson

I'm waiting for the results of your test.

Hi Minas,

I test in my PC, and seems normal:

PS : I also use CAPTIVATE-PGMR, thus I think your driver have some issue about this tools.

Thanks!

Best Regards

Johnson

Do you use MSP-exp430FR6989 ver 1.1 Launchpad for the test above?

As I can see I have a different VID NUMBER, your VID is 8263

Into youtube, there is a video advertising the capabilities of FlowEsi and there I can see that the device in the video has the same  VID as yours.

Do you know a utility to change my VID, PID, and if this is possible for my Launchpad?

Hi Minasmuch，

This VID shoud is the USB-Bridge, not the MSP-EXP430FR6989, I just connect CAPTIVATE-PGMR to PC, and then can connect successful.

I don't change any parameter.

Thanks!

Best Regards

Johnson

You can't change your VID,PID numbers They are embedded into the code. My question was:  If my numbers are eligible to be recognized by the FlowESI HID driver.  Your device has the same numbers as those in a Youtube video.

As I said above FlowEsi is a useful application for me, as I am a new one at Ti Msp430. As you can see in the picture below the downloaded version is 1_01_00_04 from the year 2014. with a black start icon. I don't know how happened but inside my C:\ti\msp430ware_3_80_13_03\flowesi\FlowMeter  I found a FlowEsi utility version 1.20 from the year 2021 with a red-white start icon. I tried this version but I face a new problem with ESI_clearInterrupt declaration. Why ????  it does not recognize the function ESI_clearInterrupt(ESI_INTERRUPT_FLAG_ESICNT0_COUNT_INTERVAL), and it does not compile. I bypass this line with ESIINT2 &= ~(ESI_INTERRUPT_FLAG_ESICNT0_COUNT_INTERVAL), and I try to connect my launchpad. The message was the same. Now, I use the code from old versions 1.01. I don't know (if there is deference in ESI code) what is the difference between the new version and the old one. I can see that the new version includes HID for MAC and Linux  -- At the office, I have a Lenovo ThinkCentre with Mint 19 Linux, and tomorrow I give it a try and I tell here If I have success

I'm wondering why TI instructs the users to download the old version from the official site.

//*******version 1.20***************************************/

I spend a working day trying the code between these two different versions trying to connect to FlowESI

Because I need the DAC values at some instances at my application and especially the DAC values with supply voltages 3V3  3V0  2V8 because ESI will count for a month into winter (Greece) and will count again the next year, I will write my application to connect my device with Comx port. It will be much helpful if the author do the connection with Comx port.

Hi Minasmuch,

Got your feedback, I will send out this problem(old version) to related team.

Does this problem is resolved? do you need other support?

Thanks!

Best Regards

Johnson

The problem is not resolved. But I have no other idea about it. I will write some code in VisualStudio for the com port to attack the launchpad.

I must mention that with ver 1.20 I could not compile the project because of the ESI_clearInterrupt(... .
SO I USE VER 1.0

I'm new at Ti MS430 but below there are some problems that I face. Please tell TI about them

a) when I got my launchpad from mouser I read the instructions and entered the site to download the appropriate code. There is a Detect my Launchpad option and I was very happy when I saw it because I thought that it will lead me to proper software. Unfortunately, the site includes software that is not for my MSP430FR6989 I spent a couple of days about them.

b) Grace - the graphic utility. Into the CCS ->preferences ->CCS->Grace -> Enable grace developer future.
O!!! wow !!! it is clearly here, where is it? how does it start? After some days I post a question to the forum. It is not supported!!! So why this dialog is there? CCS is at ver 10 Why support team does not put a menu option greyed to say "Your Device is not supported"

c) into the launchpad box there is a guide with the pinout of the launchpad NOT ALL the headers The ESI header (which is the reason I came to Ti controller) is not there. Into the datasheet says that I must go to another launchpad to find the pinout and must be careful because it is upsidedown Why ? is a small piece of paper so expensive?

d) As of ver 10.3 of the CCS released I download and attempt to compile another example importing it from the Resource explorer (I have, already, open an issue for this) and I got this error

>> Compilation failure
fram-utilities/ctpl/subdir_rules.mk:16: recipe for target 'fram-utilities/ctpl/ctpl_low_level.obj' failed
"../fram-utilities/ctpl/ctpl_low_level.asm", ERROR!   at EOF: [E0300] The following symbols are undefined:
  DMA0CTL_L

this DMA0CTL_L is not declared into the .h file but it is used in the code. I found a solution in this forum but other compilation problems came to the light. I suppose that is from an older example version and the new libraries are not implemented ????? in a proper ???? way within driverlib or compiler ver 20.4. The error is known many months ago and Ti HAS THE CODE WITH THE ERROR IN THE SITE (Resource explorer online)

another point  (but I don't remember which example is to mention) is that in GPIO Function to set up the port pin as output was using  3 parameters - the third was to say that the pin is normal pin  But in MSP430 DriverLib for MSP430F5xx_6xx Devices  2.91.13.01 all GPIO functions are with 2 params. As I wanted only the main idea, I bypass it. I remember that it was working normally and I upload it to launchpad

Hi Minas,

 Got your feedback, We will improve web & E2E answer to provide better support.

Thanks!

Best Regards

Johnson