Hello,
In a previous post (https://e2e.ti.com/support/sensors/f/1023/t/845372), I mentioned that I was interested in extracting the raw data mode with dca1000evm. and luckily I was able to reconstruct the frames using the HSI header. though, I'm not sure about the frame structure.
here is a snippet frame of length 18560 bytes in hex format:
dc0adc0a0000080ada0cda0c0000880a30040000000000000200000000008000840603020000020020000002000000000f0180040000802001
00000000000000000000000000200000000000000000000000000000008000000000000000800800000f0f0000800a00000f0f00008a080f0f0f0f
000088080f0f0f0f000088004301270100008200b9008b00000088002f0142010000a2008e00ae00000080007b016b010000a0007e00050000000
2003f0157010000aa00180049000000200032010f0100008800caffbbff00000800d6004a010000a200f7ff0f00000008004201f4000000a200a8ff6d
ff00002000cd0031010000a000bfffb1ff00000000d10054000000000052ff43ff000000007000d70000000200eeffd9ff000000008a00590000000000
29ff97ff000000008100950000008200d1ff55ff000028003d00feff0000800075ffa3ff000080001900810000008000ebffccff000002000d0041000000
0000bdff0e0000000a00a0005e000000ca0012006eff0000a2223d002f000000aa0aadff06000000aa0a570046000000aa0ae3ffaeff0000aa2a2b00
76000000ea2aeeff13000000ba2a780060000000aa2ab9ff97ff00008aaa1a0031000000aaaac5fffcff0000aaaa5d0003000000aaaaacfff4ff0000aa0
20600c1000000abaa600039000000a8aa9a0078000000a8a8c6ffb4ff00008aa07800ab0000008002fbffe4ff00008200630031000000800079ffe3ff
000000007100d100000080003700baff000000008f0069000000200054ff91ff000000008900950000008000c7ff54ff00000a004800f7ff000000004
2ffcfff000000004b007e0000000000c4ff57ff00000200360039000000000086ff99ff0000080059002d00000080007bff10ff00000000bcffd4ff00000a
007bffa1ff000000001e00d9ff0000880094ff8bff00008200dfff2d000000a800e3fffcff0000a2807e0009000000882ac7ff9fff00008a22feff56000000a
a2ae9ffe9ff0000a0227a0005000000aaaac1ffddff00008aa05000f0000000a88033000d000000a808d7008d0000008882b5ff62ff000002009100a
e0000008000caffb4ff0000020288004a00000000084effccff0000a8088b00e4000000a0000300b0ff00000000bf003e000000000058ff83ff000080
00af0081000000800099ff3bff0000a00033004e000000a8027affc2ff0000aa0096009f0000008800d1ff58ff0000a80a3f0053000000ea2a69ff9aff0
0008a0a84003c000000aa0a87ff1fff00008a2adaff1f000000aa006cffbcff0000aa2a740035000000aa0288ff2cff0000aa021c0058000000a802a2ff
88ff0000882a7700e8ff0000a82a3aff18ff0000a8aacfff130000008aa24aff4dff0000aa280c00c1ff00008a0220ff08ff000088a09dff0b00000000008
eff34ff00000200d6ff49ff0000000014ff21ff0000000080ffa4ff000000006aff7dff0000200042ff4eff0000a0005effb1ff00000000c3ffbeff00000020fdff
aaff00000000a3ff67ff0000000067ff7aff0000000098ff76ff00002000c8ff4dff000000003bff49ff00002000e9ff1d0000000800c7ffb9ff00008000ecffe
8ff000020008cff89ff00008820f3ffdaff00008882c3ff5eff0000a82accffe4ff0000a22045ff9eff00008a80490055000000aa2ad8ffe4ff0000a2aa5100
14000000aa2ad0ff0d000000880a2d0041000000aa020000b2ff00008a801c00eaff0000a228e5ff41000000a00284003a00000028804f0048000
000a80009005900000000004c007100000000001500d8ff000008008a004b0000000000c0ffd2ff000000007d00a00000000000d7ffb1ff0000000
09c009100000080009bff6aff00000000be00ad000000000063fff7fe0000020043002b0000000000c8fed8fe000000003500d1ff0000000003ffc0f
e00000000e3ff9aff0000000093fe32ff00002a009dff9fff00000802d6febefe0000200061ff1eff00000800c1fe12ff00008a0223ffe2fe0000a028f8fef
9fe00000882c8feaefe0000aaa283ffafff0000aa222ffffbfe0000aa2294ffc1ff0000abaaccfe08ff0000a8a892ffcfff00008a2afffe88fe00008820d2ffd
4ff0000aa00bdfefdfe000008a05400a8000000800021ff10ff0000880036004c000000200022ff95ff00000a009a0098000000800053ff0fff000080
2033007d0000002000c1ffd0ff00000000da00c400000080000300e0ff000000004d005f000000200055003400000000006100ccff00000200bbf
fe1ff0000aa00d2ff000000008280f7ffeeff000000a0e4ffe4ff00002200d7ffb9ff0000a880a8ffcaff0000aa020e00a6ff00008220a5ff5cff0000aa207...
1) I noticed that from chapter 3.3.2 in the mmwave sdk user manual that the underlined data doesn't correspond to the data format of the HSI header and wanted to ask you about its origins
Also based on my config file:
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 5 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 77 40 7 57.14 0 0 70 1 576 11721 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 16 0 50 1 0
lowPower 0 0
guiMonitor -1 1 1 0 0 0 1
cfarCfg -1 0 2 8 4 3 0 15 1
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 1 0.5
clutterRemoval -1 0
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
lvdsStreamCfg -1 1 1 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
CQRxSatMonitor 0 3 5 121 0
CQSigImgMonitor 0 113 10
analogMonitor 0 0
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 20.09
cfarFovCfg -1 1 -5.01 5.01
sensorStart
I wanted to ask about the size of the raw data
if raw data size = (2 components) * (2 Bytes) * (# ADC samples) * (# antennas) * (# chirps) * (# frames)
2) than raw data size = 2*2*576*4*16*1 = 73728 bytes ?
Sorry for the long post and thank you for your support,
Best regards,
Amine