Why RTOS SDK have less Rom Pointers than the Non-OS SDK

jhinkle
Posts: 32
Joined: Tue Apr 19, 2016 12:09 am

Why RTOS SDK have less Rom Pointers than the Non-OS SDK

Postby jhinkle » Wed Jun 13, 2018 6:42 pm

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.

donghengqaz
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" :D in case that you add them to LD file.

jhinkle
Posts: 32
Joined: Tue Apr 19, 2016 12:09 am

Re: Why RTOS SDK have less Rom Pointers than the Non-OS SDK

Postby jhinkle » Wed Jul 11, 2018 8:02 pm

Thanks - that makes sense.

Who is online

Users browsing this forum: No registered users and 9 guests