Dear All, I just connected the FTDI to the MCUZone at32uc3b0256 breakout. Here are the connections: I used my Fluke 115 to trace out the lines. I am sure they work.
1) GND (FTDI) to GND (development board) 2) RX (FTDI) to J2, pin 10. 3) TX (FTDI) to J2, pin 7. I don't see the nsh shell yet. It is possible the pins are wrong. OR I suspect the alternate pin function configuration. I will attack this tomorrow. Many thanks again, R On Sun, 19 Nov 2023 at 20:11, Alan C. Assis <acas...@gmail.com> wrote: > Hi Raman, > > On 11/19/23, Raman Gopalan <ramangopa...@gmail.com> wrote: > > Dear Alan, Dear Gregory, Greetings! > > > > Hello Kevin and Zou Boan! > > > > Many thanks for your suggestions. I will write in detail in a bit but > > before, I was too excited about Alan's suggestion. > > > >> Other option could be extend the CMake support to AVR32 boards. > > > > I quickly glanced through boards/arm/stm32 to see how the CMake files > > work. I put in place the CMakeLists files (similar to stm32f103, Blue > > Pill) for avr32dev1. > > > > I then ran cmake seeking help from the instructions here [1]. It > > initially asked me to pip install kconfiglib. Here's the volley I had > > with the Cygwin terminal. > > > > raman@foobar ~/nuttxspace/nuttx > > $ cmake -B build -DBOARD_CONFIG=avr32dev1:nsh -GNinja > > CMake Error at CMakeLists.txt:82 (message): > > Kconfig environment depends on kconfiglib, Please install: > > > > $ pip install kconfiglib > > > > > > -- Configuring incomplete, errors occurred! > > > > raman@foobar ~/nuttxspace/nuttx > > $ pip install kconfiglib > > Collecting kconfiglib > > Using cached kconfiglib-14.1.0-py2.py3-none-any.whl (145 kB) > > Installing collected packages: kconfiglib > > Successfully installed kconfiglib-14.1.0 > > > > Post this, I ran into another CMake error: > > > > raman@foobar ~/nuttxspace/nuttx > > $ cmake -B build -DBOARD_CONFIG=avr32dev1:nsh -GNinja > > -- Initializing NuttX > > CMake Warning at CMakeLists.txt:348 (message): > > Kconfig Configuration Error: > > C:\Users\raman\anaconda3\Scripts\olddefconfig: > > arch/Kconfig:252: > '/home/raman/nuttxspace/nuttx/build/arch/dummy/Kconfig' > > not found (in 'source "$BINDIR/arch/dummy/Kconfig"'). Check that > > environment variables are set correctly (e.g. $srctree, which is unset > > or > > blank). Also note that unset environment variables expand to the empty > > string. > > > > > > CMake Error at CMakeLists.txt:353 (message): > > Failed to initialize Kconfig configuration: > > > > > > -- Configuring incomplete, errors occurred! > > > > I initially wanted to check if the case is the same for other > > targets. CMake throws the same response for stm32f103-minimum too. I > > checked what the programs olddefconfig and defconfig did. Simply > > invoking the programs olddefconfig.exe (OR defconfig) echo this for a > > response: > > > > raman@foobar ~/nuttxspace/nuttx > > $ oldconfig > > Kconfig:10: warning: APPSDIR has 'option env="APPSDIR"', but the > > environment variable APPSDIR is not set > > Kconfig:14: warning: APPSBINDIR has 'option env="APPSBINDIR"', but the > > environment variable APPSBINDIR is not set > > Kconfig:22: warning: BINDIR has 'option env="BINDIR"', but the > environment > > variable BINDIR is not set > > Kconfig:278: warning: the 'modules' option is not supported. Let me know > if > > this is a problem for you, as it wouldn't be that hard to implement. Note > > that modules are supported -- Kconfiglib just assumes the sy > > mbol name MODULES, like older versions of the C implementation did when > > 'option modules' wasn't used. > > C:\Users\raman\anaconda3\Scripts\oldconfig: arch/Kconfig:252: > > '$BINDIR/arch/dummy/Kconfig' not found (in 'source > > "$BINDIR/arch/dummy/Kconfig"'). Check that environment variables are set > > correctly (e.g. $srctree > > , which is unset or blank). Also note that unset environment variables > > expand to the empty string. > > > > Perhaps I am missing yet another terminal configuration? I will write > > back in a couple of hours with the results of the minicom session with > > AVR32DEV1. > > > > Many thanks. > > Question: did you cloned nuttx-apps as apps/ in the same directory you > have cloned nuttx ? > > NuttX "depends on" apps/ to compile (it doesn't depend, but the build > system depends/expects to find it there). > > So: > > nuttxspace: > ./apps > ./nuttx > > Best Regards, > > Alan >
