Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c
Hi, I am not working on my github account branch, I am working by downloading the Apache NuttX codebase on my local PC. I was thinking of checking it first on my local PC, and then merging it on github. I have also observed the following, related to the issue observed : 1. I also observed in the apps/examples/elf/tests/mksymtab.sh, it is mentioned that "If the toolchain does any kind of checking for function vs. data objects, then this could fail" 2. As per my understanding, it is possible that since in symtab.c, file all symbols are generated with "_(underscore)", eg: _fflush, _fopen, etc., but since the functions, _fflush, _fopen are not defined(Only fflush, fopen, etc are defined and not _fflush, _fopen), the undefined reference error is coming. 3. Also, In NuttX 8.2 version of code, just to confirm the cause of the issue, I was trying to edit the symtab.c(I understand that it is not right to edit symtab.c, but just to check the cause of the issue), and I replaced _fflush to fflush, and the error of undefined reference was not coming. So, I think, the issue of undefined reference is coming because _fflush, _fopen are actully not defined, only fopen, fflush is defined. So, I think when the compiler tries to map the symbols generated in symtab.c, are looked for Regards, Anjana From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 12:01 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** Hi, Can you tell us your github account and the branch in which you are currently having trouble so that we can reproduce the errors? Masayuki From: Anjana Sent: Thursday, June 18, 2020 15:23 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Yes, I have added CELFFLAGS, CELFFLAGS, LDELFFLAGS in Make.defs file From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 11:33 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** Hi Anjana, Did you add some flags (i.e. CELFFLAGS, CXXELFFLAGS and LDELFFLAGS) to scripts/Make.defs? The flags are needed to build elf modules. Regards, Masayuki 差出人: Anjana 送信日時: 2020年6月18日 14:38 宛先: dev@nuttx.apache.org 件名: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Hello Team, I have added ELF Binary Loader support for RX65N target. I am currently testing my implementation using the apps/examples/elf/ example . When I enable the apps/examples/elf/ example application, and compile, I am getting the below error in symtab.c (Symbol Table) C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x14): undefined reference to `_fflush' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x1c): undefined reference to `_fopen' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x24): undefined reference to `_fprintf' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x2c): undefined reference to `_getpid' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x34): undefined reference to `_kill' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x3c): undefined reference to `_longjmp' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x44): undefined reference to `_memset' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a
RE: NXView
Agree that we don't need provide two drivers to collect the similar information. It's better to incorporate the new feature and ftrace format into the current driver. The change may break the binary format combability but I think it's acceptable to get the more feature and clean implementation. -Original Message- From: Gregory Nutt Sent: Wednesday, June 17, 2020 10:13 AM To: dev@nuttx.apache.org Subject: Re: NXView > The major differences are: > > - Different trace data format between the accumulated data in the memory and > /dev/tracer output >It is because to reduce the trace data size in the memory. The accumulated > data contains packed (not aligned) values and >task is recorded by its PID, not the name. The correspondence between PID > and task name string is hold in the separated task name buffer. >On the other hand, the output from /dev/tracer contains aligned words and > contains the task name string for each trace entries. >It is because easy to handle the data by the application code (nsh trace > command). That is a trivial difference and there are some misconceptions. The structures can be packed by simply adding the packed attribute to the structures. That does not justify a redesign. The current implementation does *not* use the task name, it uses the pid. The task name is provided only when the task is created. The provides the associated between pid and name. Thereafter only the pid is uses. Your implementation has two much overlap and should not come upstream as a separate implementation. Extensions and improvements to the existing implementation are welcome, however. Greg
Re: QuickLogic Open Source MCU + FPGA
It looks like a promising platform, but the shipping cost to the EU is unbelievable. :). I want to support porting efforts, but let's see first if I can receive it via a freight-forwarder service. Erdem
Re: The new Apache NuttX Logo
I wanted to revive this discussion. As I stated before, I and a friend of mine (a graphical artist.) will start working on this. But, - What's the deadline for this? (A deadline is a powerful force for motivation.) - We are planning to come up with a logo with a mascot. As stated above, a mascot should convey how we feel about this RTOS. So, may I ask for you guys to share your opinions on NuttX? How do you feel and what do you think about NuttX? Why do you use it? Which property of it makes it a useful tool for you? If you had to describe it with two or three words, which words would you choose? I appreciate your opinions in advance. Thanks. BR, Erdem Erdem MEYDANLI , 28 May 2020 Per, 19:57 tarihinde şunu yazdı: > Glad to hear that. A mascot like Linux penguin would make the brand name > more recollective. No matter the community wouldn't like any of the > proposals, at least, it's worth trying, I think. Well, if Zephyr weren't > using that logo, it would be one of my suggestions. (Don't ask me why. Lol) > > I don't think that many people are aware of this new logo initiative. > Making a new official announcement and setting a 'deadline for > participation' would also be helpful. Announcing the contest in social > media might create some traction and could help us to reach some 'unknown' > talented guys. > > If there is enough time to brainstorm on this, I am willing to open up > this subject to a friend of mine (a graphics guy.) who could help me to > portray ideas. > > BR, > Erdem > > Gregory Nutt , 27 May 2020 Çar, 17:55 tarihinde şunu > yazdı: > >> >> > I want to ask a question based on the draft proposals. Are we allowed to >> > think broader? :) For instance, I wonder what the community would think >> > about using a mascot. >> >> I am open to that idea myself.. like Linux' penguin? Such a mascot >> would need to have wide appeal and acceptance, I think a higher level of >> acceptance than a simple logo change. After all, such a mascot would >> have to represent how we feel as a project. >> >> That might be hard to accomplish here. People here are very diverse. >> >> I, for one, am open to all sorts of creative ideas. For example, I >> always like Zephyr's kite logo. What does a kite have to do with the >> RTOS? Nothing, but it conveys a certain feeling about how they feel >> about the RTOS. I think it would be nice to have a graphic or a mascot >> that conveys how we feel about this RTOS as well. >> >> >>
Re: The new Apache NuttX Logo
On Thu, Jun 18, 2020 at 7:43 AM Erdem MEYDANLI wrote: > I wanted to revive this discussion. As I stated before, I and a friend of > mine (a graphical artist.) will start working on this. But, > > - What's the deadline for this? (A deadline is a powerful force for > motivation.) Feel free to propose a logo anytime! Previously there was a discussion about having some sort of logo contest. If we go that route, we need a team of volunteers from the community who wish to administer the contest and be the judges (or choose judges). But, we don't have to have a contest. If someone proposes a logo and the community likes it, then we can just vote to adopt it. If we have a contest, it needs a deadline. If we don't have a contest and someone wants to propose a new logo, then the deadline is: do it ASAP so that someone else won't beat you to it!! I'm okay with either path, contest or not. More below... - We are planning to come up with a logo with a mascot. As stated above, a > mascot should convey how we feel about this RTOS. So, may I ask for you > guys to share your opinions on NuttX? How do you feel and what do you think > about NuttX? Why do you use it? Which property of it makes it a useful tool > for you? If you had to describe it with two or three words, which words > would you choose? I appreciate your opinions in advance. I think NuttX is a very friendly community and I enjoy contributing here. I use NuttX because of its commitment to standards support and runs on many MCU types from different vendors, so you don't have to rewrite all your code when you switch MCU vendors. You can choose the best MCU for each project. NuttX is a very international project. The sun never sets on NuttX developers. We are on every continent (except perhaps Antarctica). So if the mascot is an animal, I think we don't want something indigenous to only one place. But I don't know what to suggest here... Those are my thoughts for now. Thanks for reviving this conversation! Cheers, Nathan
Re: nrf51822 and BLE
I've been looking a bit more into how Zephyr code handles the NRF chips and how the Bluetooth stack is organized, see here: https://github.com/zephyrproject-rtos/zephyr/tree/master/subsys/bluetooth/controller From what I understand, they can either talk to a controller via HCI UART/SPI or directly to the chip's radio peripheral via vendor HAL. There's a link-layer (ll_sw directory) which I understand is their abstract interface into on-chip radio peripherals such as Nordic. The Nordic specific part is really thin, the HAL mostly sets registers directly and doesn't have much logic to it. I also looked at how NuttX is organized and it would appear that the host-level stack assumes a controller stack based on HCI interface commands. From what I've read, for on-chip radio peripheral there isn't a standardized interface proposed. So, this could be either handled by creating a fake HCI wrapper to on-chip radio peripheral to satisfy what NuttX's host-level stack expects (may be inefficient) or extend this part to support talking to the controller via HCI or a NuttX defined interface for on-chip peripherals. As I mentioned, I don't really know about Bluetooth internals but it would appear that lower-level part missing should not be that difficult to implement since the host-level stack is already implemented in NuttX. Also, the RADIO section of the nRF51 reference manual is pretty straightforward. Best, Matias On Thu, Jun 18, 2020, at 02:28, raiden00pl . wrote: > I agree that access to low-level radio with documented registers is a big > plus for Nordic. > I hope other vendors will follow the same path (if not then we always have > reverse engineering :P). > For this reason, we should have a standardized interface for BLE > single-chip solutions in Nuttx. > A non-standardized BLE stack probably won't have much value in commercial > products, but for amateur projects it would be a great tool. > > śr., 17 cze 2020 o 17:00 Matias N. napisał(a): > > > I saw that option recently and I don't really like it. It seems a > > debugging nightmare. > > What I actually like about Nordic is that at least it is possible to have > > an open-source low-level radio stack, which is not the case for Espressif > > since this is still closed source and undocumented. So I think the best > > path is to get proper support for this part in NuttX. > > > > But yes, maybe it is not really a porting effort but writing something > > from scratch. But even in that case it is good to have a working reference > > such as Zephyr. IMHO it would really be worth the effort. Support for > > Nordic/Espressif radio is what is attractive in other RTOSs, such as > > Zephyr. > > > > Best, > > Matias > > > > On Wed, Jun 17, 2020, at 04:06, raiden00pl . wrote: > > > You can use Nordic's priorpiate BLE stack (SoftDevice) and after a few > > > hacks even Nordic SDK can be integrated with Nuttx. > > > This gives you a certified BLE stack but it has a huge disadvantage - it > > is > > > a closed source. Looking for bugs in such an environment is a nightmare. > > > > > > Some time ago I started working on the BLE stack for NRF52 integrated > > with > > > Nuttx, but I don't have much done at the moment. > > > I don't think there is an easy way to port the Zephyr BLE stack to > > Nuttx. It > > > looks just as much work as writing it from scratch. > > > > > > śr., 17 cze 2020 o 03:32 Matias N. napisał(a): > > > > > > > Not sure what you mean by "slave" in this case. What I'm referring to > > is > > > > the access to the low-level Bluetooth hardware (register based access > > to > > > > radio peripheral). I didn't meant NuttX's BLE stack would only support > > HCI > > > > UART, I mean that there's no support for NRF radio (link-level layer) > > on > > > > NuttX yet. > > > > > > > > In other words, using Zephyr figures from their docs, the idea would > > be to > > > > support this scenario (replace Zephyr with NuttX): > > > > https://docs.zephyrproject.org/latest/_images/ble_cfg_single.png > > > > > > > > Whereas NuttX currently supports the scenario on the left of this > > figure: > > > > https://docs.zephyrproject.org/latest/_images/ble_cfg_dual.png > > > > > > > > As you mention, this requires code which interfaces the upper bluetooth > > > > stack with the low-level radio hardware. This is the code that is > > available > > > > un Zephyr under Apache 2.0 license. > > > > > > > > Best, > > > > Matias > > > > > > > > On Tue, Jun 16, 2020, at 22:24, Gregory Nutt wrote: > > > > > > > > > > > AFAIK NuttX supports the Host level API and at most HCI UART > > > > interface. I'm referring to the link-level code which interfaces > > directly > > > > with NRF51822 so that you can run NuttX in the board itself (and not > > as an > > > > external module via UART). > > > > > It supports both host and slave and uses a driver defined by and > > > > > interface. HCI UART is *not* assumed or required. I don't know that > > it > > > > > is compatible with the
Re: nrf51822 and BLE
Hi Matias, On 6/18/20, Matias N. wrote: > I've been looking a bit more into how Zephyr code handles the NRF chips and > how the Bluetooth stack is organized, see here: > https://github.com/zephyrproject-rtos/zephyr/tree/master/subsys/bluetooth/controller > > From what I understand, they can either talk to a controller via HCI > UART/SPI or directly to the chip's radio peripheral via vendor HAL. There's > a link-layer (ll_sw directory) which I understand is their abstract > interface into on-chip radio peripherals such as Nordic. The Nordic specific > part is really thin, the HAL mostly sets registers directly and doesn't have > much logic to it. > > I also looked at how NuttX is organized and it would appear that the > host-level stack assumes a controller stack based on HCI interface commands. > From what I've read, for on-chip radio peripheral there isn't a standardized > interface proposed. So, this could be either handled by creating a fake HCI > wrapper to on-chip radio peripheral to satisfy what NuttX's host-level stack > expects (may be inefficient) or extend this part to support talking to the > controller via HCI or a NuttX defined interface for on-chip peripherals. > Exactly, and if you see their two approach diagram the refer to "HCI" in RAM communicating with the chip registers. So probably this layer is just a "fake" HCI implementation. > As I mentioned, I don't really know about Bluetooth internals but it would > appear that lower-level part missing should not be that difficult to > implement since the host-level stack is already implemented in NuttX. Also, > the RADIO section of the nRF51 reference manual is pretty straightforward. > Yes, it should be a nice improvement to have it! BR, Alan
Re: QuickLogic Open Source MCU + FPGA
- 80 MHz ARM Cortex M4-F - UART only, no USB - FPGA has 2400 logic cells - Open Source software for development It's pretty low-power, but that last part is amazing– it would be great to have an RTOS+FPGA that was programmable by all open source software. I will have to think of something I can do with it. My next project will probably have an largish FPGA on it... this one is too small for that. -adam On Thu, Jun 18, 2020 at 2:11 AM Erdem MEYDANLI wrote: > It looks like a promising platform, but the shipping cost to the EU is > unbelievable. :). I want to support porting efforts, but let's see first if > I can receive it via a freight-forwarder service. > > Erdem > -- Adam Feuer
Re: NuttX config browser
They released today mentioned IDE https://os.mbed.com/blog/entry/mbed-studio-1-release It is literally vscode with few plugins. We could go the same way and do NuttX Studio :) For the beginning I could just provide instructions on how to use vscode with NuttX both for local and remote development. I was already using vscode for NuttX development, for some time, and it has good C/C++ support in comparison to other IDEs. With such instructions, we can identify what are the main issues and try to address them. Also PlatformIO and Mbed Studio plugins might be open-source, then we could just recommend them if they work or try to fork. Am Mo., 1. Juni 2020 um 13:46 Uhr schrieb Xiang Xiao < xiaoxiang781...@gmail.com>: > vscode may a good choice here: > https://code.visualstudio.com/ > It is totally free, open source and run on macOS/Linux/Windows > Many 3rd party tool build around vscode(e.g. PlatformIO): > https://platformio.org/platformio-ide > And github announce a new IDE base on vscode recently: > > https://github.com/features/codespaces/?utm_source=announcement&utm_medium=blog&utm_campaign=satellite-product-recap > The best thing is that online version has the full feature as the local > version because vscode is built from JS, CSS, and HTML. > > > -Original Message- > > From: Maciej Wójcik > > Sent: Monday, June 1, 2020 11:23 AM > > To: dev@nuttx.apache.org > > Subject: Re: NuttX config browser > > > > Hello Alan, > > > > A suggestion: when the user click on the option it should be nice to > > > see the Help for that option. > > > > > > Sure, I will add a side pane. > > > > Regarding online IDE. I was trying few times to switch to online > development. The problem is that to debug or even to connect to nsh, > > one still needs local software and local copy of entire project. Which > is against the basic reason why we would like to develop online. It > > is also a bit difficult to come up with own, custom online IDE. It is > simply a lot of work, for a team of people. > > > > That being said I can easily imagine using existing online IDE to > develop NuttX project. It could be just described how to do it efficiently. > > For example git repository can be cloned to GitLab and opened with their > IDE. > > Then binary comes from pipeline which can be flashed to the > microcontroller. Some simple client can be created which automates > > flashing. Still the issue of debugging remains. > > > > I will take a look at MBED and see how did they solve the issue. > > > > Am So., 31. Mai 2020 um 22:09 Uhr schrieb Alan Carvalho de Assis < > > acas...@gmail.com>: > > > > > Hi Maciej, > > > > > > A suggestion: when the user click on the option it should be nice to > > > see the Help for that option. > > > > > > Do you think it could be possible to do it? > > > > > > Did you test MBED platform in the browser ever? They have an online > > > IDE where people can create an application, compile it and load the > > > firmware in the board. > > > > > > It should be nice if we could have a way to compile NuttX in the > > > browser, like MBED is doing for a long time (more than 8 years at > > > least). > > > > > > BR, > > > > > > Alan > > > > > > On 5/31/20, Maciej Wójcik wrote: > > > >> > > > >> Maciej's tool is much easier to use. Maciej has several other cool > > > >> NuttX tools. > > > > > > > > > > > > Thank you Greg for a good word. I will work on this configuration > > > > browser more and I am glad to contribute it if the community will > find it useful. > > > > Regarding the other tools, I had one more project but I > > > > overcomplicated > > > it > > > > and it ended up nowhere. I am still working on it from time to time, > > > > but > > > I > > > > can't promise it will ever be production ready. > > > > > > > > Am So., 31. Mai 2020 um 19:18 Uhr schrieb spudaneco > > > > > > >: > > > > > > > >> The configuration document he is referring to is not in the > repository. > > > >> I > > > >> used to create it only for releases using a custom tool at > > > >> tools/mkconfigvars.shMaciej's tool is much easier to use.Maciej has > > > >> several other cool NuttX tools. In a meritocracy, I think > > > >> contributing these to the project would score pretty high (hint, > > > >> hint, hint)Sent from Samsung tablet. > > > >> Original message From: Brennan Ashton < > > > >> bash...@brennanashton.com> Date: 5/31/20 11:04 AM (GMT-06:00) To: > > > >> dev@nuttx.apache.org Subject: Re: NuttX config browser On Sun, May > > > >> 31, 2020, 9:17 AM Maciej Wójcik wrote:> That > > > >> document is old, from NuttX 8.2 and needs to be updated.>>> Yes, > > > >> now I remember that there was some page with configuration options. > > > >> I> think it serves the purpose. It could be auto generated using > > > >> CI, then it> wouldn't be outdated. Still I thought it could be a > > > >> bit more interactive>It is built via CI on every build, but only > > > >> hosts the latest releaseversion not master.Maybe there is
RE: NuttX config browser
Yes, I switch from eclipse to vscode several month ago. The experience is much better than eclipse from many perspective(project, editor, search, debug, shell and git). It's a good idea to setup the new wiki page to describe how to setup vscode for NuttX development, so the community can try vscode and get the real feeling. Then we can get more idea how to improve vscode to simplify the setup and streamline the daily work experience. Maciej, could you create an initial vscode info at: https://cwiki.apache.org/confluence/display/NUTTX? So we can share the vscode tip there. Thanks Xiang > -Original Message- > From: Maciej Wójcik > Sent: Friday, June 19, 2020 7:14 AM > To: dev@nuttx.apache.org > Subject: Re: NuttX config browser > > They released today mentioned IDE > https://os.mbed.com/blog/entry/mbed-studio-1-release > > It is literally vscode with few plugins. We could go the same way and do > NuttX Studio :) > > For the beginning I could just provide instructions on how to use vscode with > NuttX both for local and remote development. > I was already using vscode for NuttX development, for some time, and it has > good C/C++ support in comparison to other IDEs. > > With such instructions, we can identify what are the main issues and try to > address them. > Also PlatformIO and Mbed Studio plugins might be open-source, then we could > just recommend them if they work or try to fork. > > Am Mo., 1. Juni 2020 um 13:46 Uhr schrieb Xiang Xiao < > xiaoxiang781...@gmail.com>: > > > vscode may a good choice here: > > https://code.visualstudio.com/ > > It is totally free, open source and run on macOS/Linux/Windows Many > > 3rd party tool build around vscode(e.g. PlatformIO): > > https://platformio.org/platformio-ide > > And github announce a new IDE base on vscode recently: > > > > https://github.com/features/codespaces/?utm_source=announcement&utm_me > > dium=blog&utm_campaign=satellite-product-recap > > The best thing is that online version has the full feature as the > > local version because vscode is built from JS, CSS, and HTML. > > > > > -Original Message- > > > From: Maciej Wójcik > > > Sent: Monday, June 1, 2020 11:23 AM > > > To: dev@nuttx.apache.org > > > Subject: Re: NuttX config browser > > > > > > Hello Alan, > > > > > > A suggestion: when the user click on the option it should be nice to > > > > see the Help for that option. > > > > > > > > > Sure, I will add a side pane. > > > > > > Regarding online IDE. I was trying few times to switch to online > > development. The problem is that to debug or even to connect to nsh, > > > one still needs local software and local copy of entire project. > > > Which > > is against the basic reason why we would like to develop online. It > > > is also a bit difficult to come up with own, custom online IDE. It > > > is > > simply a lot of work, for a team of people. > > > > > > That being said I can easily imagine using existing online IDE to > > develop NuttX project. It could be just described how to do it efficiently. > > > For example git repository can be cloned to GitLab and opened with > > > their > > IDE. > > > Then binary comes from pipeline which can be flashed to the > > microcontroller. Some simple client can be created which automates > > > flashing. Still the issue of debugging remains. > > > > > > I will take a look at MBED and see how did they solve the issue. > > > > > > Am So., 31. Mai 2020 um 22:09 Uhr schrieb Alan Carvalho de Assis < > > > acas...@gmail.com>: > > > > > > > Hi Maciej, > > > > > > > > A suggestion: when the user click on the option it should be nice > > > > to see the Help for that option. > > > > > > > > Do you think it could be possible to do it? > > > > > > > > Did you test MBED platform in the browser ever? They have an > > > > online IDE where people can create an application, compile it and > > > > load the firmware in the board. > > > > > > > > It should be nice if we could have a way to compile NuttX in the > > > > browser, like MBED is doing for a long time (more than 8 years at > > > > least). > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On 5/31/20, Maciej Wójcik wrote: > > > > >> > > > > >> Maciej's tool is much easier to use. Maciej has several other > > > > >> cool NuttX tools. > > > > > > > > > > > > > > > Thank you Greg for a good word. I will work on this > > > > > configuration browser more and I am glad to contribute it if the > > > > > community will > > find it useful. > > > > > Regarding the other tools, I had one more project but I > > > > > overcomplicated > > > > it > > > > > and it ended up nowhere. I am still working on it from time to > > > > > time, but > > > > I > > > > > can't promise it will ever be production ready. > > > > > > > > > > Am So., 31. Mai 2020 um 19:18 Uhr schrieb spudaneco > > > > > > > > >: > > > > > > > > > >> The configuration document he is referring to is not in the > > repository. > > > > >> I > > > > >> used to create it only for
Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c
Hi, Perhaps I understand what happened to the rx65n target. This might be a compiler issue that it generates external function symbols with an underscore. According to gcc document, it says that: === Warning: the ‘-fleading-underscore’ switch causes GCC to generate code that is not binary compatible with code generated without that switch. Use it to conform to a non-default application binary interface. Not all targets provide complete support for this switch === I think rx-elf-gcc generates external function symbols with an underscore by default. However, you can disable this by -fno-leading-underscore. Also, you need to change some assembler code where they call external C functions with an underscore. I hope this helps. Masayuki From: Anjana Sent: Thursday, June 18, 2020 17:47 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Hi, I am not working on my github account branch, I am working by downloading the Apache NuttX codebase on my local PC. I was thinking of checking it first on my local PC, and then merging it on github. I have also observed the following, related to the issue observed : 1. I also observed in the apps/examples/elf/tests/mksymtab.sh, it is mentioned that "If the toolchain does any kind of checking for function vs. data objects, then this could fail" 2. As per my understanding, it is possible that since in symtab.c, file all symbols are generated with "_(underscore)", eg: _fflush, _fopen, etc., but since the functions, _fflush, _fopen are not defined(Only fflush, fopen, etc are defined and not _fflush, _fopen), the undefined reference error is coming. 3. Also, In NuttX 8.2 version of code, just to confirm the cause of the issue, I was trying to edit the symtab.c(I understand that it is not right to edit symtab.c, but just to check the cause of the issue), and I replaced _fflush to fflush, and the error of undefined reference was not coming. So, I think, the issue of undefined reference is coming because _fflush, _fopen are actully not defined, only fopen, fflush is defined. So, I think when the compiler tries to map the symbols generated in symtab.c, are looked for Regards, Anjana From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 12:01 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** Hi, Can you tell us your github account and the branch in which you are currently having trouble so that we can reproduce the errors? Masayuki From: Anjana Sent: Thursday, June 18, 2020 15:23 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Yes, I have added CELFFLAGS, CELFFLAGS, LDELFFLAGS in Make.defs file From: Ishikawa, Masayuki (SHES) Sent: 18 June 2020 11:33 To: dev@nuttx.apache.org Subject: Re: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c **This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.** Hi Anjana, Did you add some flags (i.e. CELFFLAGS, CXXELFFLAGS and LDELFFLAGS) to scripts/Make.defs? The flags are needed to build elf modules. Regards, Masayuki 差出人: Anjana 送信日時: 2020年6月18日 14:38 宛先: dev@nuttx.apache.org 件名: ELF Application Example(apps/examples/elf) undefined references issue in symtab.c Hello Team, I have added ELF Binary Loader support for RX65N target. I am currently testing my implementation using the apps/examples/elf/ example . When I enable the apps/examples/elf/ example application, and compile, I am getting the below error in symtab.c (Symbol Table) C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x14): undefined reference to `_fflush' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x1c): undefined reference to `_fopen' C:\cygwin64\home\USER\PR_To_Apache\Binary_Loader\incubator-nuttx\staging\libapps.a(symtab.home.USER.PR_To_Apache.Binary_Loader.incubator-nuttx-apps.examples.elf.o):(.rodata.g_elf_exports+0x24): undefined reference to `_fprintf' C:\cygwin64\home\USER\PR_To_Apa
