• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 931 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.

AWR1843: Exception when porting HWA+DSP demo (IWR6843 OOB) to AWR1843

Chris Meng
Mastermind 37846 points
Part Number: AWR1843
Other Parts Discussed in Thread: IWR6843,

Hi,

In latest mmWave SDK 3.2, the oob demo of AWR1843 still only uses HWA to do all FFT/CFAR operation. But the oob demo of IWR6843 uses HWA for 1D FFT and DSP for other process. So I tried to port IWR6843 OOB demo to AWR1843. But I met excpetion error. I steped into the code and found it happend when calling rlRfSetCalMonTimeUnitConfig API. Pls find detail exception info below. Can you get some clue on below info?

Exception occurred in ThreadType_Hwi.

Hwi handle: 0x0.

Hwi stack base: 0x800ea10.

Hwi stack size: 0x800.

R0 = 0x080002c8 R8 = 0x00020df8

R1 = 0x000c011f R9 = 0x000c011f

R2 = 0x0800cc94 R10 = 0x00020df0

R3 = 0x00000003 R11 = 0x00020df4

R4 = 0x00000000 R12 = 0x0800f1dc

R5 = 0xe59ff018 SP(R13) = 0x0800f130

R6 = 0x00000001 LR(R14) = 0x0000dec9

R7 = 0x08000394 PC(R15) = 0x00017fe2

PSR = 0x200c019f

DFSR = 0x0000080d IFSR = 0x00000000

DFAR = 0xe59ff018 IFAR = 0x00000000

{module#43}: line 205: error {id:0x1a0000, args:[0x17fe2, 0xdec9]}

xdc.runtime.Error.raise: terminating execution

  • 0
    TI__Guru*** 149164 points
    Hi Chris,

    What code changes have you performed?

    thank you
    Cesar
  • 0
    TI__Mastermind 21025 points

    Perhaps the calling arguments to rlRfSetCalMonTimeUnitConfig are different between the two devices.  But it should return an error, not throw an exception.  Perhaps there's a device difference that needs to be accounted for - like the pinmux, or available events/event mapping....

     -dave

  • 0 in reply to db_woodall
    TI__Mastermind 21025 points

    Hi Chris,

    Let's close the thread if there is nothing else.

    Thanks, dave

  • 0
    Prodigy 185 points

    Can you provide your code for 1d FFT with hwa to me ?

    I have some troubles when I configure the hwa to perform the 1d fft use the function

    in mmwave_sdk_03_02_00_04\packages\ti\datapath\dpu\rangeproc\src\rangeprochwa.c.

    Thank you !

  • 0 in reply to user5943549
    TI__Mastermind 37846 points

    user5943549 said:

    Can you provide your code for 1d FFT with hwa to me ?

    I have some troubles when I configure the hwa to perform the 1d fft use the function

    in mmwave_sdk_03_02_00_04\packages\ti\datapath\dpu\rangeproc\src\rangeprochwa.c.

    Thank you !

    Hi,

    Pls refer to the mmw demo code for xWR6843. It uses HWA for 1DFFT.

  • 0 in reply to db_woodall
    TI__Mastermind 37846 points

    db_woodall said:

    Perhaps the calling arguments to rlRfSetCalMonTimeUnitConfig are different between the two devices.  But it should return an error, not throw an exception.  Perhaps there's a device difference that needs to be accounted for - like the pinmux, or available events/event mapping....

     -dave

    Dave,

    I have changd the pinmux for 1843. What events/event mapping do you refer to?

  • 0 in reply to Chris Meng
    TI__Mastermind 21025 points

    >What events/event mapping do you refer to?

    Mainly, the event caused by this HWI.  I suppose the thing to do is to try to determine if the HWI is caused by BSS processing of rlRfSetCalMonTimeUnitConfig, or some other rl API that executed prior to it. This is called prior to the starting of chirps, so the only thing happening at this point is calibration - correct?  Is the configuration of calibration correct for 1843?

      -dave