Solved it.
Bit 3 of register 198 was set to default value 0, which selects an external clock for P3 RMII clock. Because we use the internal clock, it needed to be set to 1. This solved our problem.
Search found 16 matches
- Tue Nov 05, 2019 2:04 pm
- Forum: ESP-IDF
- Topic: KSZ8863RLL Switch & ESP-32
- Replies: 2
- Views: 6027
- Mon Nov 04, 2019 1:53 pm
- Forum: ESP-IDF
- Topic: Support for Serial Management Interface (SMI)
- Replies: 2
- Views: 6238
Re: Support for Serial Management Interface (SMI)
Hi vjacobs, Thank you for your reply. Yes, after digging around in the esp32 technical reference manual, I arrived at the same conclusion. I switched over to I2C and now I have access to all the registers. However, the reason I created this topic was that I am unable to obtain an IP with the esp32. ...
- Thu Oct 31, 2019 2:44 pm
- Forum: ESP-IDF
- Topic: Building with CLion IDE problems
- Replies: 1
- Views: 3231
Re: Building with CLion IDE problems
Hi.
Yes, I use CLion without any issues. What exactly is the problem? Is your project cmake based? Which step fails? Do you have some log output to share?
Yes, I use CLion without any issues. What exactly is the problem? Is your project cmake based? Which step fails? Do you have some log output to share?
- Thu Oct 31, 2019 2:39 pm
- Forum: ESP-IDF
- Topic: Support for Serial Management Interface (SMI)
- Replies: 2
- Views: 6238
Support for Serial Management Interface (SMI)
Hi, The ethernet switch KSZ8863RLL(http://ww1.microchip.com/downloads/en/DeviceDoc/00002335B.pdf) requires a non standard SMI interface to have full access to all control/status registers. This differs from the standard MDIO interface supported by ESP32 by 2 parameters: the Read/Write OP Code and PH...
- Thu Oct 31, 2019 1:27 pm
- Forum: ESP-IDF
- Topic: KSZ8863RLL Switch & ESP-32
- Replies: 2
- Views: 6027
KSZ8863RLL Switch & ESP-32
Hi, I have a PCB with a 3-port ethernet switch KSZ8863RLL (http://ww1.microchip.com/downloads/en/DeviceDoc/00002335B.pdf) and an esp32 WROVER connected to it via RMII and MDIO interface, and I need to establish an internet connection with the esp. The switching itself is working by default. By conne...
- Wed Oct 03, 2018 12:26 pm
- Forum: ESP-IDF
- Topic: WiFi not allocated from SPIRAM
- Replies: 0
- Views: 3145
WiFi not allocated from SPIRAM
I'm experimenting with WROVER Kit and I'm trying to force all of WiFi memory usage into SPIRAM but so far I've had no success. My code is as follows: int spiram_available = heap_caps_get_free_size(MALLOC_CAP_SPIRAM); int internal_available = heap_caps_get_free_size(MALLOC_CAP_INTERNAL); tcpip_adapte...
- Fri Sep 14, 2018 12:57 pm
- Forum: ESP-IDF
- Topic: SPIRAM disappears randomly
- Replies: 1
- Views: 4049
SPIRAM disappears randomly
So we recently started developing code for the WROVER module that has 4MB of SPIRAM. I enable the SPIRAM in menuconfig and I check the available size of it at the very beginning of my application using heap_caps_get_free_size(MALLOC_CAP_SPIRAM), and it returns the expected size of 4MB. BUT, when I s...
- Wed Jul 18, 2018 1:30 pm
- Forum: ESP-IDF
- Topic: IO pulled low when entering light sleep
- Replies: 1
- Views: 4512
IO pulled low when entering light sleep
Hi, I've come across a situation where using timer as a wakeup source causes a GPIO to be pulled low upon entering light sleep. The GPIO is GPIO17 and it's configured as basic output without pullup/pulldown resistors. I have full control over it outside of sleep, but if esp_sleep_enable_timer_wakeup...
- Sun Nov 12, 2017 4:26 pm
- Forum: General Discussion
- Topic: Wrong wake up reason
- Replies: 3
- Views: 7317
Re: Wrong wake up reason
Hi,
just wanted to say that I've noticed the same problem.
just wanted to say that I've noticed the same problem.
- Mon Aug 07, 2017 11:52 am
- Forum: ESP-IDF
- Topic: Can't create a second xTaskCreatePinnedToCore()
- Replies: 2
- Views: 8042
Re: Can't create a second xTaskCreatePinnedToCore()
Hi, FreeRTOS uses void task(void* param) as the function's signature. Any other function signature breaks ABI. To work around this, pass the pointer to your data as a void pointer and cast and assign it to the preferred type of variable on function entry, like so: const char* data = (const char*) pa...