Re: Question about ESP32 PC address.

On Tue, Sep 6, 2022 at 8:12 PM Gregory Nutt wrote: > Might be a corrupted address; 0x7278 is ASCII "rx". Could be stack > overflow corrupting the address. Interesting! I hadn't considered to check what the ASCII values of the pointer address might be. This will be a valuable addition to my

Re: Question about ESP32 PC address.

Might be a corrupted address; 0x7278 is ASCII "rx". Could be stack overflow corrupting the address. On Tue, Sep 6, 2022 at 5:37 PM Nathan Hartman wrote: > On Tue, Sep 6, 2022 at 6:35 PM Victor Benso wrote: > > Besides all the SMP related issues that most likely I failed to figure > out, > > I

Re: Question about ESP32 PC address.

On Tue, Sep 6, 2022 at 6:35 PM Victor Benso wrote: > Besides all the SMP related issues that most likely I failed to figure out, > I would really like to know what kind of address is this at the APP CPU > 0x7278b09a > Addr2line failed to decode that address. The most similar address that I >

Question about ESP32 PC address.

Hi, I'm dealing with an interesting situation regarding a WDT lock in the esp32-devkitc board. Some details: -SPI3 has 2x MCP2515 under heavy canbus traffic. -SPI2 has an SDCard in SPIMode. -TWAI is also receiving a reasonable CAN traffic. -Wifi is connected to an AP sending data from the SDCard

Re: Driver for combined battery charger and regulator

Battery driver is a special one because the framework doesn't define any ioctl to enable/disable the device, which means you have to enable it in register. On Tue, Sep 6, 2022 at 10:18 PM TimH wrote: > Thanks! > > I think I will take the following approach: > > - Use Kconfig to determine the

Re: Driver for combined battery charger and regulator

Hi Tim, You are welcome! That is a good idea, defining the initial voltage for each channel on Kconfig will make user life easier. BR, Alan On 9/6/22, TimH wrote: > Thanks! > > I think I will take the following approach: > > - Use Kconfig to determine the default setup (which regulators are

RE: Driver for combined battery charger and regulator

Thanks! I think I will take the following approach: - Use Kconfig to determine the default setup (which regulators are enabled, and their voltage). If another user wants to do this manually it can be achieved by disabling them in Kconfig and using ioctl to set them manually - have first

Re: Driver for combined battery charger and regulator

Hi Tim, I think you can implement a register and a initialization as separated functions, if you search you will find some drivers implemented that way. I remember a developer that complained about the fact the some sensors are initialized automatically during the register phase and it was bad

Re: Crash in ostest prioinherit?

On Tue, Sep 6, 2022 at 5:36 AM Fotis Panagiotopoulos wrote: > Priority inheritance has a known bug, and it is not working correctly. > See issue #6310: https://github.com/apache/incubator-nuttx/issues/6310 > > I had to disable it in our application, as it causes lots of problems. Thanks for

RE: Driver for combined battery charger and regulator

Oh - OK! Thanks Alan. Makes my life easier (for now) as I'm not using the battery charger element on this board iteration so I can leave it for later. Any thoughts on my mental tussles regarding registering vs. initialising? >-Original Message- >From: Alan Carvalho de Assis >Sent: 06

Re: Driver for combined battery charger and regulator

Hi Tim, AFAIK we don't have a PMIC with battery regulator in the mainline yet. So you don't have a reference to base on it. You don't need to create a single file with all functions on it, you can create separated file for each specific function. This is how MC13892 is implemented on Linux

Driver for combined battery charger and regulator

I'm writing a driver for the Quorvo ACT8945A device. This is a combined 7-output programmable regulator AND Li-ion battery charger, all in one. I see there are existing "regulator.h" and "battery_charger.h" driver templates. Would my best approach to be to create a driver using a new

Re: Crash in ostest prioinherit?

Hello, Priority inheritance has a known bug, and it is not working correctly. See issue #6310: https://github.com/apache/incubator-nuttx/issues/6310 I had to disable it in our application, as it causes lots of problems. As I see, there are a couple of propositions on fixing this, but none of

[VOTE] Apache NuttX 11.0.0 (incubating) RC1 release

Hello all, Apache NuttX (Incubating) 11.0.0 RC1 has been staged under [1] and it's time to vote on accepting it for release. If approved we will seek final release approval from the IPMC. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are