Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connecting wifi gives unhandled debug exception in phy_chip_v7 #299

Closed
lollizze opened this issue Jan 25, 2017 · 4 comments
Closed

connecting wifi gives unhandled debug exception in phy_chip_v7 #299

lollizze opened this issue Jan 25, 2017 · 4 comments

Comments

@lollizze
Copy link

Simplified my application does as follows
Through the uart i can configure the wifi settings and then enabling it to connect to an AP
When i try to connect to an AP it sometimes gives an exception. It seems random, because i can't reproduce it every time and I can't see the what is on line 1708 in phy_chip_v7 to try and find a solution.
Could it be some timing issue, whatever ppTask does it gets interfered by wifi API calls?

Heres the backtrace:
#0 spur_cal (freq=, BW_h=,
spur_freq_cfg=32767, spur_freq_cfg_div=0 '\000') at phy_chip_v7.c:1708
#1 0x40087c51 in spur_cal (spur_freq_cfg_div=1 '\001',
spur_freq_cfg=, BW_h=, freq=2417)
at phy_chip_v7.c:1701
#2 ram_spur_coef_cfg (channel=2 '\002', freq=2417,
sub_chan_cfg=) at phy_chip_v7.c:1739
#3 0x40087360 in chip_v7_set_chan (channel=,
sub_chan_cfg=) at phy_chip_v7_ana.c:653
#4 0x40088d38 in set_chanfreq (chanFreq=2417, sub_chan_cfg=0 '\000')
at phy_chip_v7.c:1850
#5 0x400856e4 in phy_change_channel (chanFreq=2417, bHomeChan=1 '\001',
pBReset=0 '\000', sub_chan_cfg=0 '\000') at phy.c:13
#6 0x400ddc4e in chm_set_current_channel ()
#7 0x400ddc81 in ?? ()
#8 0x400ddce6 in chm_start_op ()
#9 0x400dc150 in ?? ()
#10 0x400dc16e in scan_enter_oper_channel_process ()
#11 0x400dd9a8 in ?? ()
#12 0x400dda31 in ieee80211_timer_do_process ()
#13 0x40098179 in ppTask ()

@negativekelvin
Copy link
Contributor

Are you sure is not weak power supply issue?

@lollizze
Copy link
Author

100% sure no, but i figured it would show up more frequently if it where that

@projectgus
Copy link
Contributor

projectgus commented Jan 26, 2017

This feels like a power supply/decoupling issue to me, calibration tends to be a power consumption spike.

Do you have any details of the type of exception? If IllegalInstructionException then almost certainly a power issue. If something else then possibly.

EDIT: Sorry I just saw "unhandled debug exception" which is probably an assertion failure. This seems like it's probably either power, or something to do with the way the code you have is initializing wifi. Testing on the built-in examples will help narrow it down.

Do you get the problem running any of the examples bundled with esp-idf?

@lollizze
Copy link
Author

Tried to simplify it to pin point the problem, but with no luck. Maybe it is a power problem, but it is connected to an usb hub with external power so i thought that would be sufficient

@lollizze lollizze closed this as completed Mar 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants