I writing a bootloader for myself and wanted access to 4 rom based functions.
They appear in the NON-OS SDK file eagle.rom.addr.v6.ld:
The functions are: ets_printf, ets_putc, SPIRead, and SPIWrite.
The last two are very important since they are required for bootloader operation. The two "ets_" functions are for exporting debug data during the boot process.
I don't use the NON-OS SDK since I prefer the RTOS version.
To my surprise, those functions don't exist in the RTOS SDK.
Can someone tell me the equivalent function names in the RTOS_SDK?
Why would common low-level functions be in one SDK and not the other?
Thanks.
Why RTOS SDK have less Rom Pointers than the Non-OS SDK
-
- Posts: 5
- Joined: Tue Jun 13, 2017 11:40 am
Re: Why RTOS SDK have less Rom Pointers than the Non-OS SDK
Postby donghengqaz » Wed Jul 11, 2018 6:02 pm
These APIs are not multi-thread safe or source including mutex, so at RTOS version they are dropped. You can also use them but just "using"
in case that you add them to LD file.

Who is online
Users browsing this forum: No registered users and 293 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.