we are working with two EVAL-ADF7242-PMDZ boards.
One device should be configured in IEEE802.15.4-2006 sport mode TX and one in IEEE802.15.4.2006 sport mode RX.
The RX-board is working and verified, though we cant get the TX board working.
We tried to setup the TX as described in figure 9 of the data sheet:
-) Invoke the adf7242 device in RC_TX state, data clocked in on falling edge of clock.
(Also tried, data clocked in on rising edge of clock -> no difference)
-) Set up a test-frame to transmit:
x"00",x"00",x"00",x"00", -- Preamblex"A7", -- SFDx"10", -- PHY headerx"01",x"A8", -- Frame control fieldx"99",x"AA",x"AA",x"BB",x"BB",x"DD",x"DD",x"EE",x"EE", -- Addressing fields x"C0",x"FF",x"EE", -- Payloadx"90",x"A9" -- FCS
-) Do the symbol to chip mapping:
-) Put the data synchronized with TRCLK_CKO_GP3(faling edge f clock) , out on DT_GP1:
Start of the transmission:
setup-time: The data changes on on the rising edge of the TRCLK_CKO_GP3 clock -> t33 is 250ns.
hold-time: The hold time t34 is set to 100ns.
Unfortunately, we cant get any data output on the RX adf7242 device.
Any help would be appreciated.
PS: There is some inconsistent in the data sheet, regarding the sportmode-RX configuration,you might want to fix:
Thanks for your query. I have some clarifications on your test-frame:
SFD - I would expect this to be 16bits long
PHY Header - Not sure what settings you wish to set but I would expect to see 0x01, 0x98 corresponding to your Addressing, Payload and FCS fields
Can you clarify these settings please?
thanks for answer.
The SFD is copied out of the IEEE802.15.4-2006 standard and is defined as 8-bits, see screen shot from the standard below:
The PHY-Header (PHR) only contains the length of the PDSU in octets.
In my case the PSDU is 16 octets long, so i set it to 0x10.
Hi,Sorry, I meant to reference the Frame Control Field, rather than the PHY Header Field. For the PHY Header field, 0x10 looks correct to me. However for the Frame Control field I would like some more clarification. Not sure what settings you wish to set but I would expect to see 0x01, 0x98 corresponding to your Addressing, Payload and FCS fields.
no problem, I rechecked the Frame Control field and you are right, it was wrong.
Thanks for pointing out!
I messed up the bit order of the Frame Version subfield.
Now I get the same results as you expected:
However, Iam not sure how this actually has influence on the radio transmission.
Thanks for your help!
Can you clarify what your FCS value is now after the correction to the the Frame Control Field?