• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 21 subscribers
  • Views 901 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CDCE6214: Questions about TICS Pro Ver1.7.7.1(the latest version).

Kazuya Nakai59
Guru 21845 points
Part Number: CDCE6214


Hello guys,

One of my customers is evaluating CDCE6214 using TICS Pro for their next products.

At this moment, they have the following questions.
Could you please give me your reply?

Q.
They are using TICS Pro Ver1.7.7.1(the latest version).
They save the setting data to file with clicking "Read EEPROM to File" button 
after setting data writing to EEPROM with TICS Pro.

In the previous version(Ver 1.7.6.2) of TICS Pro case, "EEPROM file saved" was shown then.
But in the latest version, the warning message was shown as the follow.

[Warning]:Error in Flex script
‘ascii’codec can’t encode character ‘\u706B’ in position 59
Python Error:
‘ascii’codec can’t encode character ‘\u706B’ in position 59
[Python]:BTN_EEP_DIR_READ2FILE_Update in C:\ProgramData\Texas Instruments\TICS Pro\Configurations\Devices\Clock Generator-Jitter Cleaner (Single Loop)\CDCE6214-Q1\EEPROM.py:124,System. Object Run1[Python Function,Object](Iron Python. Runtime. Python Function)
USBANY device “USB\VIDE_2047&PID_0301\95F0884608002600” removed.

Also 0 Byte file is output then. (It seems that the writing was failed.)  

1. Why is the warning pupped up?
2. Is their any way to avoid the warning?
3. Is the warning popped up on the latest version only?
4. If the answer to 3 is yes, do you have any plan to fix the warning message?

Your reply would be much appreciated.

Best regards.
Kazuya. 

  • 0
    TI__Mastermind 23330 points

    Kazuya,

    I do not get this issue on my side, which is likely why this issue was not detected (from a fresh installation):

    Are you trying to overwrite an existing file, or save a completely new file?

    Are you using a character (example: 火) in the file name that cannot be properly encoded in UTF-8 format? This is what the ‘\u706B’ character appears to encode to, which may be the cause of the issue.

    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    Guru 21845 points

    Hello Kadeem,

    Thank you very much for your reply.

    The customer tried to save the data to existed and new file. But both saving were failed.
    Also they didn't use file name that cannot be properly encoded in UTF-8 format. (They used "test.hxt" as the file name.)

    The followings are procedures they took.
    Before Jan/2024: They used ver 1.7.5.15 without any problem.
    Jan/30th/2024   : They installed ver 1.7.7.1 to the same PC and then this data writing trouble was happened.
                                After that, they installed ver 1.7.6.2 to the same PC and then this data writing trouble was solved.
                                After that, they installed ver 1.7.7.1 to the same PC again and then the writing trouble was happened again.
                                After that, they installed ver 1.7.6.2 to the same PC again and then this data writing trouble was solved.
                                At this moment, ver 1.7.6.2 has been installed to their PC. (OS of the PC is Windows10 Pro 22H2)

    And they are going to try to install ver 1.7.7.1 on a PC which had never been installed the TICS Pro tools program before.
    I will inform you as soon as I get the result.

    Thank you again and best regards,
    Kazuya.

  • 0 in reply to Kazuya Nakai59
    Guru 21845 points

    Hello Kadeem,

    Thank you very much for your support.

    Could I ask you the following question?

    Q.
    If the customer created the file using Read EEPROM to file of Ver 1.7.6.2,
    is the warning occurred when they use Write File to EEPROM of Ver 1.7.7.1?

    Thank you again and best regards,
    Kazuya.

  • 0 in reply to Kazuya Nakai59
    TI__Mastermind 23330 points

    Kazuya,

    It is possible that this is the issue. There may be an issue with a BOM requirement for the file (UTF vs UTF with BOM). The type used by TICS Pro changed between 1.7.6.2 and 1.7.7.1.
    Can you send the file to me to try, either here or via email?
    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    Guru 21845 points

    Hello Kadeem,

    Thank you very much for your support.

    I got their data generated by Ver 1.7.6.2. and I attached it.
    (I changed extension from .hxt to .txt because the .hxt file can not be attached to this thread.
     So please change the file extension back to .hxt.)
    But the data is default value. 
    They generated the data with the procedure.

    1. Install TICS Pro Ver 1.7.6.2..
    2. Select CDCE6214-Q1.
    3. Set 「EVM Default」.
    4. Execute "EEPROM->Read EEPROM to  File"

    They confirmed that No error was occurred with Ver 1.7.6.2 and Error was occurred with 1.7.7.1
    when they executed 「Write File to EEPROM」 using the attached data.

    Could you please try to write the attached data on your side?

    Thank you again and best regards,
    Kazuya. 

     

    Fullscreen test2.txt Download 
    ----- CDCE6214-Q1 EEPROM HEX TEXT FILE ------
Header Info	Tue Feb 06 16:39:09 2024
nvmbusy	0x0000
nvmcrcerr	0x0000
nvm_wr_error	0x0000
nvm_rd_error	0x0000
nvmlcrc	0xc02d
nvmscrc	0xc02d
nvm_rd_addr	0x0000
nvm_rd_data	0x7000
nvm_wr_addr	0x0000
nvm_wr_data	0x0000

----- BASE   PAGE 0 ------
00	0x7000	28672
01	0x487f	18559
02	0x1b12	6930
03	0x0000	0
04	0x38e0	14560
05	0x4d1e	19742
06	0x1f00	7936
07	0x6680	26240
08	0x82c0	33472
09	0x4200	16896
10	0x0418	1048
11	0x0c20	3104
12	0x1002	4098
13	0x0106	262
14	0x0004	4
15	0x0100	256

----- CONFIG PAGE 0 ------
16	0x2020	8224
17	0x0246	582
18	0x4c00	19456
19	0x0004	4
20	0x0201	513
21	0x00c0	192
22	0x0000	0
23	0x0000	0
24	0x0000	0
25	0x0a22	2594
26	0x1800	6144
27	0x00d8	216
28	0x8000	32768
29	0x0c00	3072
30	0x0000	0
31	0x0c08	3080
32	0x0000	0
33	0x0c08	3080
34	0x0000	0
35	0x0008	8
36	0x0020	32
37	0x0000	0
38	0x0000	0
39	0x1000	4096

----- CONFIG PAGE 1 ------
40	0x2020	8224
41	0x0246	582
42	0x4c00	19456
43	0x0004	4
44	0x0201	513
45	0x00c0	192
46	0x0000	0
47	0x0000	0
48	0x0000	0
49	0x0a22	2594
50	0x1800	6144
51	0x00d8	216
52	0x8000	32768
53	0x0c00	3072
54	0x0000	0
55	0x0c08	3080
56	0x0000	0
57	0x0c08	3080
58	0x0000	0
59	0x0008	8
60	0x0020	32
61	0x0000	0
62	0x0000	0
63	0xc02d	49197
----- END EEPROM HEX TEXT FILE ------

  • 0 in reply to Kazuya Nakai59
    TI__Mastermind 23330 points

    Kazuya,

    When I change my regional format from English (United States) to Japanese (Japan), I am able to reproduce the error:

    I installed the latest TICS Pro version (1.7.7.2) from the web, and now no longer have this issue. Please have the customer install the latest version of the software.

    Thanks,

    Kadeem