On 2/8/2024 2:50 PM, Alan C. Assis wrote:
Thank you for clarifying Greg, but I think PIC32 is using little
endian, at least I can't see CONFIG_ENDIAN_BIG defined to them at boards/
You are right. MIPS is traditionally big-endian or powers up
big-endian, but Microchip opted to force little end
Dear Alan, Dear NuttX community, greetings!
> Nice to see they added JTAG support to avrdude, but only few AVR8
> has JTAG support (i.e. Atmega128 has).
I trust you're all doing so well. I revisited the NuttX codebase today. I
created a sample at32uc3b0256 (avr32dev1) Microchip Studio project to
Nice to see they added JTAG support to avrdude, but only few AVR8 has
JTAG support (i.e. Atmega128 has).
BR,
Alan
On 11/24/23, Tomek CEDRO wrote:
> On Fri, Nov 24, 2023 at 5:32 PM Alan C. Assis wrote:
>> Thank you Tomek,
>> I searched in the source code and didn't find AVR32 support, it is
>> s
On Fri, Nov 24, 2023 at 5:32 PM Alan C. Assis wrote:
> Thank you Tomek,
> I searched in the source code and didn't find AVR32 support, it is
> strange because I remember of seeing "at32uc3b512" is the avrdude
> command line (our board uses at32uc3b256).
Quick search shows example list of supported
Thank you Tomek,
I searched in the source code and didn't find AVR32 support, it is
strange because I remember of seeing "at32uc3b512" is the avrdude
command line (our board uses at32uc3b256).
BR,
Alan
On 11/24/23, Tomek CEDRO wrote:
> On Fri, Nov 24, 2023 at 4:35 PM Alan C. Assis wrote:
>> Un
On Fri, Nov 24, 2023 at 4:35 PM Alan C. Assis wrote:
> Unfortunately in this case OpenOCD also is not helping, because the
> AVR32 support it very limited (AFAIK there is no support to flash
> AVR32 chips) and because I don't have the original Atmel JTAGICE MkII
> I cannot use their avr32program as
Hi Raman,
Thank you very much for this detailed update! I'm really impressed by
your hard work to get it working. I think AVR32 itself is very
challenging now on Linux because Atmel original code is rusting
(unfortunately not in the Rust way hehehe).
So or later this old tools will stop to work o
Dear Alan, Greetings!
I re-installed my GNU/Linux. I am running Ubuntu 23.10. Atleast,
things are working as expected. All my problems with /dev are
solved. My Atmel ICE device is getting enumerated fine. Here is my
version.
raman@foo:~$ lsb_release -a
No LSB modules are available.
Distributor ID
Dear Alan, Greetings!
About the CMake files: Despite installing Kconfiglib (for Python3) I get
errors
like these:
raman@foo:~/Skullets/nuttxspace/nuttx$ cmake -B build
-DBOARD_CONFIG=avr32dev1:nsh -GNinja
CMake Error at CMakeLists.txt:82 (message):
Kconfig environment depends on kconfiglib, Pleas
Dear Greg, Greetings,
> It is likely that you could create a pure Windows native build (using a
> Windows native toolchain) or a pure Cygwin build (using a tool chain built
> under Cygwin) with CMake.
This can involve hacking the recipe files for crosstool-NG for AVR32 [1].
`wget'
(within the bui
But again, I think we can avoid this tortuous path and fix the CMake or
Makefile to build on Windows.
Fully understand.
It is likely that you could create a pure Windows native build (using a
Windows native toolchain) or a pure Cygwin build (using a tool chain
built under Cygwin) with CMake.
Dear Alan,
> But again, I think we can avoid this tortuous path and fix the CMake or
> Makefile to build on Windows.
Fully understand.
> BTW, could you please submit a PR with yours CMakefiles to AVR32? I want
to
> test it here too.
For sure. May I send them to you tomorrow? I wrote them on Win
> Do you have a logic analyzer? That strange character could be something,
case
> the clock is incorrect.
This is an awesome idea! :) I will get my logic analyser to check if I can
see
anything at all.
R
On Mon, 20 Nov 2023 at 18:45, Alan C. Assis wrote:
> Hi Raman,
>
> On 11/20/23, Raman Gopa
Hi Raman,
On 11/20/23, Raman Gopalan wrote:
> Dear Alan,
>
> I confirm the following settings from the NuttX make menuconfig. RX: PA24,
> alternate function 0. TX: PA23, alternate function 0. So, this is correct.
> Greg's user manual helped. I just grepped for the definitions.
>
> I see that the
Hi Raman,
On 11/20/23, Raman Gopalan wrote:
> Dear Alan, Greetings!
>
> Many thanks for your suggestions.
>
>> Note that I already adapted it to use your Atmel ICE Device S/N. I just
> use: $
>> sudo openocd -f openocd.cfg
>
> Thank you Alan. I just pasted your openocd configuration and invoked
>
Dear Alan,
I confirm the following settings from the NuttX make menuconfig. RX: PA24,
alternate function 0. TX: PA23, alternate function 0. So, this is correct.
Greg's user manual helped. I just grepped for the definitions.
I see that the MCUZone's AT32UC3B isn't very different from the AVR32DEV1
Dear Alan, Greetings!
Many thanks for your suggestions.
> Note that I already adapted it to use your Atmel ICE Device S/N. I just
use: $
> sudo openocd -f openocd.cfg
Thank you Alan. I just pasted your openocd configuration and invoked openocd
just like you suggested. Unfortunately, I still see
Dear Alan,
> Did you setup your serial console terminal to 57600 ? Normally NuttX uses
> 115200, but for avr32dev1 the default is this value.
Yes, for sure. I checked .config. It was exactly 57600. Also on `minicom'.
> Do you have the AVR32DEV1 schematic? I didn't find it.
This has been a probl
Hi Raman,
Did you setup your serial console terminal to 57600 ?
Normally NuttX uses 115200, but for avr32dev1 the default is this value.
Do you have the AVR32DEV1 schematic? I didn't find it.
Looking the NuttX source code, the console is using USART1 PA24 as RXD
and PA17 as TXD.
Best Regards,
> Question: did you cloned nuttx-apps as apps/ in the same directory you
have
> cloned nuttx ?
For sure Alan. This is exactly how it is on both my machines.
> NuttX "depends on" apps/ to compile (it doesn't depend, but the build
system
> depends/expects to find it there).
Fully understand. Yes,
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 i
Hi Greg,
AFAIK, Mr. Zou (CC here) fixed the Windows/Cygwin build few months ago.
We just need to add it in our CI to avoid it breaks again in the feature.
Brennan/Petro/Xiang, do you have a machine to add the Windows CI ?
Best Regards,
Alan
On 11/18/23, Gregory Nutt wrote:
> AFAIK, the Cygwi
Hi Raman,
On 11/19/23, Raman Gopalan 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 AVR
Hi Raman,
On 11/19/23, Raman Gopalan wrote:
> Dear All,
>
> I just plugged in the Atmel ICE programmer. I am currently working with my
> Ubuntu GNU/Linux machine. Here are the version details:
>
> raman@foo:~/Skullets$ uname -a
> Linux foo 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC M
Dear All,
>> I read [2]. It wasn't very helpful in my case. Could the problem with
ICE be
>> about [2]?
Sorry, just an observation: I just plugged-in my FTDI breakout. It works
fine. So,
I conclude [2] works fine. Here is the log of dmesg.
[16504.718633] ftdi_sio 1-2.3:1.0: FTDI USB Serial Devic
Dear All,
I just plugged in the Atmel ICE programmer. I am currently working with my
Ubuntu GNU/Linux machine. Here are the version details:
raman@foo:~/Skullets$ uname -a
Linux foo 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 9
15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I
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
AFAIK, the Cygwin build using a windows native tool chain has been
broken for years. There is no advice anyone can give that that is just
going to make it work. It is broken and no one has interest in fixing
that which they have broken. People make many changes to the build
system but never tes
Hi Raman,
I'm CC Kevin Liu, he integrated NuttX into Microchip Studio in the
past (although I thing he used the "make export" and imported the
library on it).
On 11/18/23, Raman Gopalan wrote:
> Dear Alan, Greetings!
>
> Many thanks for your message. I am sorry about the slight delay in
> respon
Dear Alan, Greetings!
Many thanks for your message. I am sorry about the slight delay in
response.
> Thank you for reviving this discussing (I'm CC NuttX mailing list
> because it could interest one person or two).
Perfect!
> $ ./tools/configure.sh avr32dev1:nsh
I encountered the same problems
Hi Raman,
Thank you for reviving this discussing (I'm CC NuttX mailing list
because it could interest one person or two).
On 11/14/23, Raman Gopalan wrote:
> Dear Alan, Greetings!
>
> I trust you're doing so well. I am so sorry about the long pause. I
> revisited NuttX again a couple of days ago
31 matches
Mail list logo
