Re: Issues with PIC32

The patch for the context switching works perfectly, thanks! I do now have it working on the actual hardware as well, so I can start messing around with some stuff. -Robert Middleton

Re: Issues with PIC32

On Sun, Feb 21, 2021 at 5:08 PM Robert Middleton wrote: > > > I don't have an actual Microchip Explorer16/32 which it sounds like > > you are working on, but if you were to put a draft PR up or point me > > at a branch I would be happy to try to run this against the simulator > > and see if we can

Re: Issues with PIC32

I was able to run nuttx on this board . Had to change some fuses to get it working with pinguino. Ethernet was up, but crashed after receiving a few pings. On Sun, Feb 21, 2021 at 10:08 PM Robert Middleton wrote: > > I don't have an actual Microch

Re: Issues with PIC32

> I don't have an actual Microchip Explorer16/32 which it sounds like > you are working on, but if you were to put a draft PR up or point me > at a branch I would be happy to try to run this against the simulator > and see if we can get a little further. > > This is the simulator I was using https:

Re: Issues with PIC32

A breakpoint on up_assert should catch any early crashes as you describe. There is a cool debug tip here if you hit the breakpoint: *https://nuttx.events/wp-content/uploads/2019/11/DSidrane_nx2019.pdf* Unfortunately that appears to be a broken link now. Speaking of nuttx.events... Is there a

Re: Issues with PIC32

PIC32are MPS and do not have hardfaults.  That is a Cortex-M thing.  So DSidranes tip does not apply and up_hardfault should not exist for PIC32.  I spend too much time with ARMs and a forget about the rest of the world. So nevermind... sorry. On 2/21/2021 5:11 PM, Nathan Hartman wrote: On S

Re: Issues with PIC32

On Sun, Feb 21, 2021 at 6:13 PM Brennan Ashton wrote: > > On Sun, Feb 21, 2021 at 3:11 PM Nathan Hartman > wrote: > > > > On Sun, Feb 21, 2021 at 11:18 AM Gregory Nutt wrote: > > > A breakpoint on up_assert should catch any early crashes as you > > > describe. There is a cool debug tip here if

Re: Issues with PIC32

On Sun, Feb 21, 2021 at 3:11 PM Nathan Hartman wrote: > > On Sun, Feb 21, 2021 at 11:18 AM Gregory Nutt wrote: > > A breakpoint on up_assert should catch any early crashes as you > > describe. There is a cool debug tip here if you hit the breakpoint: > > *https://nuttx.events/wp-content/uploads/

Re: Issues with PIC32

On Sun, Feb 21, 2021 at 11:18 AM Gregory Nutt wrote: > A breakpoint on up_assert should catch any early crashes as you > describe. There is a cool debug tip here if you hit the breakpoint: > *https://nuttx.events/wp-content/uploads/2019/11/DSidrane_nx2019.pdf* Unfortunately that appears to be a

Re: Issues with PIC32

On Sun, Feb 21, 2021 at 11:25 AM Gregory Nutt wrote: > > > > ... Using > > the pinguino toolchain, 2 LEDs now light up, and the debugger at least > > thinks that we're in the up_idle function, so that looks promising. > > After switching the serial console to UART2(for the explorer16), I do > > n

Re: Issues with PIC32

... Using the pinguino toolchain, 2 LEDs now light up, and the debugger at least thinks that we're in the up_idle function, so that looks promising. After switching the serial console to UART2(for the explorer16), I do now get data out of the serial port! The last message that I see is "nx_st

Re: Issues with PIC32

I had been using the pinguino toolchain earlier, but nothing was happening, hence my switching of compilers to see if anything worked. With the other compilers, I only got one LED lit up, and at least according to the MPLABX debugger we were stuck in mm_addregion. Using the pinguino toolchain, 2

Re: Issues with PIC32

* What can I do to debug early boot problems? You can at first try enabling debug output. (make menuconfig --> Build Setup --> Debug Options --> Enable Debug Features). You should have some information regarding what's going on. Another option is to enable DEBUG_SYMBOLS and debug the startup

Re: Issues with PIC32

Hi, I personally haven't used the PIC32 port in a while, but left it working. At least the PIC32MZ one. > Are my assumptions that I should just be able to build and run NuttX on the explorer16/max32 incorrect? This could work. However, you have to verify that the configurations in board.h mat