Are you using the latest code in Git, or the 1.5.1 code on linuxwimax.org? I believe this is already fixed in Git, but didn't make it into 1.5.1.
There are actually a whole pile of structure alignment issues in 1.5.1, so I would strongly recommend pulling the wimax network service code from Git before continuing. On Wed, Jan 05, 2011 at 08:30:14AM -0800, Doug Kehn wrote: > Hi All, > > I figured out that the ChannelInfo_t structure was misaligned. The channel > plan, ChannelPlan_t, contains an array of ChannelInfo_t > (ChannelPlan_t::channels). ChannelInfo_t::preambleBitmap is a 15-byte > character array. Channels after ChannelPlan_t::channels[0] fell on > un-aligned addresses. > > I didn't go back and look but I suspect somewhere in the structure > declarations there is a 'packed' attributed. This would explain why the > compiler didn't pad ChannelInfo_t::preambleBitmap. > > To keep moving forward, I simply changed (wmxSDK_Nds_Cmn.h): > typedef UINT8 wmx_Preambles_t[PREAMBLES_LENGTH], *wmx_pPreambles_t; > to > typedef UINT8 wmx_Preambles_t[PREAMBLES_SIZE], *wmx_pPreambles_t; > and added > #define PREAMBLES_SIZE 16 > > After doing this the scan parameters sent to the device look correct and > WiMAX_DB.bin is no longer updated/altered with BW and FFTSize set to -1. > > > ... on to the next problem. I noticed that only half the channel plan is > sent to the device. This causes the device to hang in scanning. This may be > a topic for another thread. I wanted to post my findings to complete this > thread. > > > Regards, > ...doug > > > --- On Mon, 1/3/11, Doug Kehn <[email protected]> wrote: > > > From: Doug Kehn <[email protected]> > > Subject: Re: L3L4_RESPONSE_STATUS_ERROR_BAD_STATE > > To: [email protected] > > Date: Monday, January 3, 2011, 12:40 PM > > Sorry...I misspoke. The > > ChannelPlan gets modified as a result of starting wimaxd not > > executing 'wimaxcu scan'. > > > > > > ...doug > > > > --- On Mon, 1/3/11, Doug Kehn <[email protected]> > > wrote: > > > > > From: Doug Kehn <[email protected]> > > > Subject: Re: L3L4_RESPONSE_STATUS_ERROR_BAD_STATE > > > To: [email protected] > > > Date: Monday, January 3, 2011, 12:29 PM > > > Hi All, > > > > > > From the last post, if I go ahead and execute > > 'wimaxcu > > > ron', the device transitions to READY with both HW/SW > > radios > > > ON. Executing 'wimaxcu scan' reproduces the > > > observations from the initial post. I did notice > > that > > > the ChannelPlan gets altered as a result of executing > > > 'wimaxcu scan'. I've attached WiMAX_DB.bin from > > before > > > and after the scan was executed. > > > > > > Why does the channel plan get altered? Could this, > > > ultimately, be causing the scan to fail? > > > > > > Thanks, > > > ...doug > > > > > > > > > --- On Thu, 12/30/10, Doug Kehn <[email protected]> > > > wrote: > > > > > > > From: Doug Kehn <[email protected]> > > > > Subject: Re: > > L3L4_RESPONSE_STATUS_ERROR_BAD_STATE > > > > To: [email protected] > > > > Date: Thursday, December 30, 2010, 4:34 PM > > > > It appears that the problem may when > > > > wimaxd is starting up or possibly something in > > the > > > > driver. I compared wimaxd messages between an > > Intel > > > > (little-endian) laptop and may ARM (big-endian) > > > > target. (Note that the laptop is running > > wimax-1.5 > > > and > > > > I'm using wimax-1.5.1.) I've attached the > > > > output. The wimaxd messages between the two > > systems > > > > track until just after L4_L3_OPCODE_CMD_INIT is > > > sent. > > > > The response to L4_L3_OPCODE_CMD_INIT is > > > > L3L4_RESPONSE_STATUS_SUCCESS_IN_PROCESS on both > > > > systems. A L4_L3_OPCODE_GET_STATE is sent > > next. > > > > The Intel platform returns E_SYSTEM_STATE_CONFIG; > > the > > > ARM-be > > > > platform returns E_SYSTEM_STATE_INIT. After > > this > > > the > > > > messages diverge. The Intel platform > > eventually > > > > progresses to E_SYSTEM_STATE_READY; the ARM-be > > > platform > > > > progresses to E_SYSTEM_STATE_RF_OFF. > > > > > > > > I'll keep digging... > > > > > > > > Regards, > > > > ...doug > > > > > > > > > > > > > > > > --- On Wed, 12/29/10, Doug Kehn <[email protected]> > > > > wrote: > > > > > > > > > From: Doug Kehn <[email protected]> > > > > > Subject: > > L3L4_RESPONSE_STATUS_ERROR_BAD_STATE > > > > > To: [email protected] > > > > > Date: Wednesday, December 29, 2010, 10:57 > > AM > > > > > Hi All, > > > > > > > > > > I'm attempting to get wimax running on > > > big-endian > > > > ARM... > > > > > > > > > > wimaxcu returns 'Operation Failed.' when > > > attempting > > > > to > > > > > scan. I see wimaxd is getting > > > > > L3L4_RESPONSE_STATUS_ERROR_BAD_STATE in > > response > > > to > > > > > L4_L3_OPCODE_CMD_RF_CONTROL. > > > > > > > > > > I'm trying to determine what state the radio > > is > > > in and > > > > why > > > > > it is a bad state when the scan is > > executed. > > > I'm > > > > sure > > > > > the problem is related to endian-ness but I > > > haven't > > > > been > > > > > able to track it down yet. Any assistance > > would > > > be > > > > > greatly appreciated. Below is a message > > dump > > > from > > > > > wimaxd. > > > > > > > > > > Thanks, > > > > > ...doug > > > > > > > > > > > > > > > >>> [MSG 0x5205][12] > > > > > 05 52 00 00 42 02 00 00 00 00 00 10 > > > > > .R..B....... > > > > > <<< [RSP 0x5205][36] > > > > > 05 52 18 00 42 02 00 00 00 00 00 00 8d 00 > > 04 > > > 00 > > > > > .R..B........... > > > > > 03 00 00 00 a3 00 04 00 01 01 00 00 96 00 > > 04 > > > 00 > > > > > ................ > > > > > 01 00 00 00 > > > > > > > > > > .... > > > > > >>> [MSG 0x5205][12] > > > > > 05 52 00 00 42 02 00 00 00 00 00 10 > > > > > .R..B....... > > > > > <<< [RSP 0x5205][36] > > > > > 05 52 18 00 42 02 00 00 00 00 00 00 8d 00 > > 04 > > > 00 > > > > > .R..B........... > > > > > 03 00 00 00 a3 00 04 00 01 01 00 00 96 00 > > 04 > > > 00 > > > > > ................ > > > > > 01 00 00 00 > > > > > > > > > > .... > > > > > >>> [MSG 0x5205][12] > > > > > 05 52 00 00 42 02 00 00 00 00 00 10 > > > > > .R..B....... > > > > > <<< [RSP 0x5205][36] > > > > > 05 52 18 00 42 02 00 00 00 00 00 00 8d 00 > > 04 > > > 00 > > > > > .R..B........... > > > > > 03 00 00 00 a3 00 04 00 01 01 00 00 96 00 > > 04 > > > 00 > > > > > ................ > > > > > 01 00 00 00 > > > > > > > > > > .... > > > > > >>> [MSG 0x4402][244] > > > > > 02 44 e8 00 42 02 00 00 00 00 94 38 b5 00 > > 18 > > > 00 > > > > > .D..B......8.... > > > > > d4 46 26 00 00 00 05 02 ff ff ff ff ff ff > > ff > > > ff > > > > > .F&............. > > > > > ff ff ff ff ff ff ff 00 b5 00 18 00 e4 6d > > 26 > > > 00 > > > > > .............m&. > > > > > 01 00 05 02 ff ff ff ff ff ff ff ff ff ff > > ff > > > ff > > > > > ................ > > > > > ff ff ff 00 b5 00 18 00 f4 94 26 00 02 00 > > 05 > > > 02 > > > > > ..........&..... > > > > > ff ff ff ff ff ff ff ff ff ff ff ff ff ff > > ff > > > 00 > > > > > ................ > > > > > b5 00 18 00 bc c7 26 00 03 00 00 ff ff ff > > ff > > > ff > > > > > ......&......... > > > > > ff ff ff ff ff ff ff ff ff ff ff 00 b5 00 > > 18 > > > 00 > > > > > ................ > > > > > 64 23 28 00 04 00 00 ff ff ff ff ff ff ff > > ff > > > ff > > > > > d#(............. > > > > > ff ff ff ff ff ff ff 00 b5 00 18 00 4c a4 > > 28 > > > 00 > > > > > ............L.(. > > > > > 05 00 00 ff ff ff ff ff ff ff ff ff ff ff > > ff > > > ff > > > > > ................ > > > > > ff ff ff 00 b5 00 18 00 4c cb 28 00 06 00 > > 00 > > > ff > > > > > ........L.(..... > > > > > ff ff ff ff ff ff ff ff ff ff ff ff ff ff > > ff > > > 00 > > > > > ................ > > > > > b5 00 18 00 4c f2 28 00 07 00 00 ff ff ff > > ff > > > ff > > > > > ....L.(......... > > > > > ff ff ff ff ff ff ff ff ff ff ff 00 b7 00 > > 04 > > > 00 > > > > > ................ > > > > > 02 00 00 00 > > > > > > > > > > .... > > > > > <<< [RSP 0x4402][12] > > > > > 02 44 00 00 28 79 c9 00 04 00 94 38 > > > > > .D..(y.....8 > > > > > >>> [MSG 0x5205][12] > > > > > 05 52 00 00 42 02 00 00 00 00 94 38 > > > > > .R..B......8 > > > > > <<< [RSP 0x5205][36] > > > > > 05 52 18 00 42 02 00 00 00 00 ff ff 8d 00 > > 04 > > > 00 > > > > > .R..B........... > > > > > 03 00 00 00 a3 00 04 00 01 01 00 00 96 00 > > 04 > > > 00 > > > > > ................ > > > > > 01 00 00 00 > > > > > > > > > > .... > > > > > >>> [MSG 0x4602][20] > > > > > 02 46 08 00 42 02 00 00 00 00 00 00 a2 00 > > 04 > > > 00 > > > > > .F..B........... > > > > > 01 00 00 00 > > > > > > > > > > .... > > > > > <<< [IND 0xd005][12] > > > > > 05 d0 00 00 40 79 c9 00 00 00 21 00 > > > > > ....@y....!. > > > > > <<< [RSP 0x4602][12] > > > > > 02 46 00 00 28 79 c9 00 03 00 00 00 > > > > > .F..(y...... > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > wimax mailing list > > > > > [email protected] > > > > > http://lists.linuxwimax.org/listinfo/wimax > > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > > > _______________________________________________ > > > > wimax mailing list > > > > [email protected] > > > > http://lists.linuxwimax.org/listinfo/wimax > > > > > > > > > > > > -----Inline Attachment Follows----- > > > > > > _______________________________________________ > > > wimax mailing list > > > [email protected] > > > http://lists.linuxwimax.org/listinfo/wimax > > > > > > > > _______________________________________________ > > wimax mailing list > > [email protected] > > http://lists.linuxwimax.org/listinfo/wimax > > > > > > _______________________________________________ > wimax mailing list > [email protected] > http://lists.linuxwimax.org/listinfo/wimax > _______________________________________________ wimax mailing list [email protected] http://lists.linuxwimax.org/listinfo/wimax
