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.

TIC12400-Q1: TIC12400

Part Number: TIC12400-Q1
Other Parts Discussed in Thread: TIC12400

Dear Sir or Madam,
I used to work with chip tic12400. That is a magnificent SPI chip!
I can write a utility tool to interpret raw the tic12400 47x registers values blob to human readable *.txt configuration report according the tic12400 datasheet.
As a example I sent a data in ->data out for tja1101 (just as an example).
I can also write register values blob parsers for any TIs smart chips with internal registers.
May TI company reward for this kind of work?
Warm regards,
Alex Bar
Embedded SW engineer

out_tja1101_confuguration.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
Basic control register [0h] regVal: [0x2100] [0b_0010_0001_0000_0000]
bit 15: RW normal operation
bit 14: RW normal operation
bit 13: RW 100 Mbit/s if SPEED_SELECT (MSB) = 0 reserved if SPEED_SELECT (MSB) = 1
bit 12: RW Auto negotiation not supported; always 0; a write access is ignored
bit 11:RW normal operation (clearing this bit automatically triggers a transition to Normal mode, provided control bits POWER_MODE are set to 0011 Normal mode, see Table 18)
bit 10: RW normal operation
bit 9: RW Auto negotiation not supported; always 0; a write access is ignored.
bit 8: RW only full duplex supported; always 1; a write access is ignored
bit 7: RW COL signal test not supported; always 0; a write access is ignored
bit 6: RW 10 Mbit/s if SPEED_SELECT (LSB) = 0 100 Mbit/s if SPEED_SELECT (LSB) = 1
bit 5: RW enable transmit from MII only when the PHY has determined that a valid link has been established
Basic status register [1h] regVal: [0x01e1] [0b_0000_0001_1110_0001]
bit 15: PHY not able to perform 100BASE-T4
bit 14: PHY not able to perform 100BASE-X full-duplex
bit 13: PHY not able to perform 100BASE-X half-duplex
bit 12: PHY not able to perform 10 Mbit/s full-duplex
bit 11: PHY not able to perform 10 Mbit/s half-duplex
bit 10: PHY not able to perform 100BASE-T2 full-duplex
bit 9: PHY not able to perform 100BASE-T2 half-duplex
bit 8: extended status information in register 15h
bit 7: PHY able to transmit from MII regardless of whether the PHY has determined that a valid link has been established
bit 6: PHY will accept management frames with preamble suppressed
bit 5: Autonegotiation process completed
bit 4: no remote fault condition detected
bit 3: PHY not able to perform Autonegotiation
bit 2: link is down
bit 1: no jabber condition detected
bit 0: extended register capabilities
PHY identifier register 1 [2h] regVal: [0x0180] [0b_0000_0001_1000_0000]
bit 15..0: Organizationally Unique Identifier 0x0180
PHY identifier register 2 [3h] regVal: [0xdd01] [0b_1101_1101_0000_0001]
bit 15..10: phyId 0x37 (19 to 24 of the OUI)
bit 9..4: manufacturer type number 0x10
bit 3..0: manufacturer revision number 0x01
Extended status register [15] regVal: [0x0080] [0b_0000_0000_1000_0000]
bit 15: PHY not able to perform 1000BASE-X full-duplex
bit 14: PHY not able to perform 1000BASE-X half-duplex
bit 13: PHY not able to perform 1000BASE-T full-duplex
bit 12: PHY not able to perform 1000BASE-T half-duplex
bit 7: PHY able to 1-pair 100BASE-T1 100 Mbit/s
bit 6: PHY not able to support RTPGE
PHY identifier register 3 [16] regVal: [0x0079] [0b_0000_0000_0111_1001]
Lack of detalisation in datasheet
Extended control register [17] regVal: [0x6000] [0b_0110_0000_0000_0000]
bit 15: link control disabled
bit 14..11: Standby mode (command)
bit 10: disable Slave jitter test
bit 9: halts the training phase
bit 8..6: R/W test mode selection: no test mode
bit 5: stops TDR-based cable test
bit 4..3: R/W internal loopback
bit 2: configuration register access disabled
Configuration register 1 [18] regVal: [0x5c05] [0b_0101_1100_0000_0101]
bit 15: rw PHY configured as Slave
bit 14: rw wake-up event forwarded locally
bit 11: rw PHY reacts to a remote wake-up
bit 14: rw PHY reacts to a local wake-up
bit 9:8: RW MII mode enabled
bit 7: MII output driver standard strength
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
in_tja1101_reg_map_blob.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
0x00 0x2100
0x01 0x01E1
0x02 0x0180
0x03 0xDD01
0x04 0x0000
0x05 0x0000
0x06 0x0000
0x07 0x0000
0x08 0x0000
0x09 0x0000
0x0a 0x0000
0x0b 0x0000
0x0c 0x0000
0x0d 0x0000
0x0e 0x0000
0x0f 0x0080
0x10 0x0079
0x11 0x6000
0x12 0x5C05
0x13 0x3245
0x14 0x0000
0x15 0x8000
0x16 0x8000
0x17 0x0000
0x18 0x0200
0x19 0x0000
0x1a 0x0000
0x1b 0x0020
0x1c 0x0001
0x1d 0x0000
0x1e 0x0000
0x1f 0x2100
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • Hello Aleksandr,

     

    Thanks for reaching out on E2E™ and we appreciate your business.  Unfortunately, TI does not compensate for community or customer related application software.  However, if you would like to help other TI customers using our devices you can share your code in our E2E™ support forums.

     

    Additionally sharing code/SW/knowledge with others on E2E™ is okay however E2E™ should not be used to solicit business opportunities.

    Thanks and best regards,

    Nic

    E2E™ Product Manager