• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 51 subscribers
  • Views 953 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.

BSC_Initialize error -4 TM4C123GH6PM CC2564MODA

RedRat
Prodigy 140 points

Other Parts Discussed in Thread: TM4C123GH6PM, CC2564MODA, CODECOMPOSER

Hello,

We're using a custom board with a TM4C123GH6PM  and a CC2564MODA. The ports and pins used between the 2 are identical to the TM4C123G Development Board.

I'm attempting to get the HIDDemo  to run (with CodeComposer v5) on it however the BSC_Initialize function fails and returns error -4 INITIALIZATION_ERROR .

I've checked that the device is powering up correctly, tried with and with out __SUPPORT_CC256XB_PATCH__ defined.

I'm stumped as to what next to try.


Thanks,

Red.

  • 0
    TI__Guru* 85400 points
    Hi Red,

    Can you please confirm how you're verifying device power up.
    It should be as per: processors.wiki.ti.com/.../CC256x_Testing_Guide

    If it's true, then it must be a host UART driver issue.

    Can you please share the BT logger logs so I can confirm if device is powering up and if some commands are being sent by the host.
    Please refer to: processors.wiki.ti.com/.../CC256x_Logger_User_Guide for the logger logs.

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Prodigy 140 points

    Hi Gigi,

    Yes, that's the guide I used to test it's powering up properly.

    We've ordered that cable and I'll provide the logs once it's arrived.


    Thanks,
    Red

  • 0 in reply to RedRat
    Prodigy 140 points

    Hi Gigi,

    Here are the logs(I used TIInit_6.7.16.ili) :

    Fullscreen RedRatBtLogs.txt Download 
    1	2	13:07:51.979   +0:00:00.000	BT Logger 1			uart_hci parameters: UartDIV=4, OS=17, SP=63, MoB=7
2	2	13:07:51.979   +0:00:00.000	BT Logger 1			temperature sensing: temp 23, read 0x23, vbe 0x299597d, slope 0x1edb6
3	2	13:07:51.979   +0:00:00.000	BT Logger 1			Temperature region = 6
4	3	13:07:51.979   +0:00:00.000	BT Logger 1			In lc_rf_init_periodic_calibration
5	5	13:07:51.979   +0:00:00.000	BT Logger 1			synch event REG received, module RF_CALIBRATION, msi 0
6	5	13:07:51.979   +0:00:00.000	BT Logger 1			synch cmd start instance, module RF_CALIBRATION, msi: 0
7	5	13:07:51.979   +0:00:00.000	BT Logger 1			synch cmd return event STARTED,module RF_CALIBRATION
8	2	13:07:51.979   +0:00:00.000	BT Logger 1			ORCA Platform
9	2	13:07:51.979   +0:00:00.000	BT Logger 1			Process type: Nominal
10	2	13:07:51.979   +0:00:00.000	BT Logger 1			Chip revision: 6
11	2	13:07:51.979   +0:00:00.000	BT Logger 1			Detected Clock = 38400000 Hz
12	2	13:07:51.979   +0:00:00.000	BT Logger 1			Ref Clock = 38400000 Hz
13	2	13:07:51.979   +0:00:00.000	BT Logger 1			XTAL wakeup mode  is disabled
14	2	13:07:51.979   +0:00:00.000	BT Logger 1			Ref Clock is valid for PLL
15	2	13:07:51.979   +0:00:00.000	BT Logger 1			PLL Clock Output is OK
16	2	13:07:51.979   +0:00:00.000	BT Logger 1			PLL Clock Out = 40000000 Hz
17	2	13:07:51.979   +0:00:00.000	BT Logger 1			Clock Working mode: PLL Mode
18	2	13:07:51.979   +0:00:00.000	BT Logger 1			ARM Clock = 40000000 Hz, Slow Clock: External
19	2	13:07:51.979   +0:00:00.000	BT Logger 1			OCP Clock = 8000000 Hz
20	4	13:07:51.979   +0:00:00.000	BT Logger 1			UART HCI baudrate = 116363
21	2	13:07:51.979   +0:00:00.000	BT Logger 1			Gemini type Soft Gemini
22	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_get_local_features
23	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_set_brcst_retran
24	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_self_test_run_init_tests
25	2	13:07:51.979   +0:00:00.000	BT Logger 1			Self Test passed
26	4	13:07:51.979   +0:00:00.000	BT Logger 1			I2C doesn't exist !
27	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_get_local_bd_addr
28	3	13:07:51.979   +0:00:00.000	BT Logger 1			Software version - 7.0.16
29	2	13:07:51.979   +0:00:00.000	BT Logger 1			Deactivating timer: init
30	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_rf_periodic_calibration
31	2	13:07:51.979   +0:00:00.000	BT Logger 1			Calibration started. Vector=0x1, 0x0
32	2	13:07:51.979   +0:00:00.000	BT Logger 1			PHY FW Version 3.27
33	2	13:07:51.979   +0:00:00.000	BT Logger 1			random 0x3517 0x64fb
34	2	13:07:51.979   +0:00:00.000	BT Logger 1			random 0x8845 0x3663
35	2	13:07:51.979   +0:00:00.000	BT Logger 1			random 0xde36 0xa7b
36	2	13:07:51.979   +0:00:00.000	BT Logger 1			random 0x8d7e 0x37a0
37	2	13:07:51.979   +0:00:00.000	BT Logger 1			random 0xa1a3 0x5413
38	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_generate_rand
39	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_generate_rand
40	5	13:07:51.979   +0:00:00.000	BT Logger 1			synch event FINISH received, module RF_CALIBRATION, msi 0
41	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_generate_rand
42	3	13:07:51.979   +0:00:00.000	BT Logger 1			lm_lc_generate_rand
43	4	13:07:52.276   +0:00:00.297	BT Logger 1			Transport detection: UART detected
44	3	13:07:52.276   +0:00:00.297	BT Logger 1			first byte recevied 1
45	3	13:07:52.276   +0:00:00.297	BT Logger 1			Disable FLIGHT MODE - Enable TX calibration
46	4	13:07:52.276   +0:00:00.297	BT Logger 1			Uart Active Protocol: H4 PROTOCOL
47	4	13:07:52.276   +0:00:00.297	BT Logger 1			hcic_process_hci_commands: HCI_RESET (Group 3 Opcode 0x3)
48	3	13:07:52.276   +0:00:00.297	BT Logger 1			lm_lc_gemini_coex_notify_scan_status
49	2	13:07:52.276   +0:00:00.297	BT Logger 1			HCI_Reset Completed
50	4	13:07:52.276   +0:00:00.297	BT Logger 1			hcic_get_num_of_host_commands. Total free = 3, Reported to host = 1
51	4	13:07:52.276   +0:00:00.297	BT Logger 1			HCI Send Event: HCI_COMMAND_COMPLETE_EVT

    Since it seems to halt on the Event send I assume this implies the host tm4c isn't receiving that event correctly?

    Thanks,

    Red.

  • 0 in reply to RedRat
    TI__Guru* 85400 points
    Hi Red,

    Yes, the host sends HCI_RESET to device and the device sends a command complete (HCI_COMMAND_COMPLETE_EVT) to the host. But it looks like the host is not receiving this.

    I think you need to further debug the host uart.

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Prodigy 140 points
    Thanks Gigi.

    As far as I can see a return uart signal is reaching the pin.

    Where would a good break point placement be, and what variables should I be inspecting? I've put one in RxInterrupt() in HCITRANS.c and it does seem to be reading in a single byte (0).

    I've also noticed a peculiarity with the voltages; our 1.8v rail jumps to 2-2.4 when it fails.

    Thanks,
    Red
  • 0 in reply to RedRat
    Prodigy 140 points
    Hi again,

    We've solved the issue.
    Our rx wasn't being pulled high properly.

    Thanks for your help, Gigi.

    Red.