Re: official nuttx-ci-linux image
> > > > > > https://github.community/t/docker-pull-from-public-github-package-registry-fail-with-no-basic-auth-credentials-error/16358 > > heh. i may add my complaint there. > > now, i have a variation of my original suggestion. > in addition to github packages, how about pushing the image to a less > broken public registry as well? eg. docker hub > I can open a ticket with infrastructure to at least see what the options are. Before it was harder because we don't have control of the secret store on the project so they would have to add the API token for docker hub to it. There are other projects using it for storing their CI images so it seems possible. I did not expect that restriction when we first set it up. Why would they not allow you to use there own Container Registry with there Actions product correctly... I had hoped it was and oversight and they would fix it quickly, but it seems to be by design. --Brennan >
Re: official nuttx-ci-linux image
On Fri, Aug 7, 2020 at 9:38 AM Brennan Ashton wrote: > > On Thu, Aug 6, 2020, 4:35 PM Takashi Yamamoto > wrote: > > > On Thu, Aug 6, 2020 at 11:57 PM Brennan Ashton > > wrote: > > > > > > On Thu, Aug 6, 2020, 4:03 AM Takashi Yamamoto > > > > > wrote: > > > > > > > hi, > > > > > > > > the docker image used by the CI (nuttx-ci-linux) is useful for other > > > > purposes. > > > > but as far as i know, it isn't pullable publicly. > > > > > > > > right now, i'm building and pushing it to docker hub for my own > > > > consumption. > > > > https://hub.docker.com/repository/docker/yamt/nuttx-ci-linux > > > > i think it's worth to provide an equivalent officially as a project. > > > > > > > > how do you think? > > > > > > > > > > The image is already publicly available. This is how the CI system uses > > it > > > including Jenkins > > > > > > https://github.com/apache/incubator-nuttx-testing/packages/159581 > > > > spacetanuki% docker pull > > docker.pkg.github.com/apache/incubator-nuttx-testing/nuttx-ci-linux:latest > > Error response from daemon: Get > > > > https://docker.pkg.github.com/v2/apache/incubator-nuttx-testing/nuttx-ci-linux/manifests/latest > > : > > no basic auth credentials > > spacetanuki% > > > > what credential should i use for public consumption? > > > > > You have to use your GitHub credentials or token even for public ones > unfortunately. > > https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages > > There is a long ticket of people complaining about this restriction. It's > also why we have the extra login step in our CI run. a token with read:packages worked. thank you. > > https://github.community/t/docker-pull-from-public-github-package-registry-fail-with-no-basic-auth-credentials-error/16358 heh. i may add my complaint there. now, i have a variation of my original suggestion. in addition to github packages, how about pushing the image to a less broken public registry as well? eg. docker hub > > --Brennan
Re: official nuttx-ci-linux image
On Thu, Aug 6, 2020, 4:35 PM Takashi Yamamoto wrote: > On Thu, Aug 6, 2020 at 11:57 PM Brennan Ashton > wrote: > > > > On Thu, Aug 6, 2020, 4:03 AM Takashi Yamamoto > > > wrote: > > > > > hi, > > > > > > the docker image used by the CI (nuttx-ci-linux) is useful for other > > > purposes. > > > but as far as i know, it isn't pullable publicly. > > > > > > right now, i'm building and pushing it to docker hub for my own > > > consumption. > > > https://hub.docker.com/repository/docker/yamt/nuttx-ci-linux > > > i think it's worth to provide an equivalent officially as a project. > > > > > > how do you think? > > > > > > > The image is already publicly available. This is how the CI system uses > it > > including Jenkins > > > > https://github.com/apache/incubator-nuttx-testing/packages/159581 > > spacetanuki% docker pull > docker.pkg.github.com/apache/incubator-nuttx-testing/nuttx-ci-linux:latest > Error response from daemon: Get > > https://docker.pkg.github.com/v2/apache/incubator-nuttx-testing/nuttx-ci-linux/manifests/latest > : > no basic auth credentials > spacetanuki% > > what credential should i use for public consumption? > You have to use your GitHub credentials or token even for public ones unfortunately. https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages There is a long ticket of people complaining about this restriction. It's also why we have the extra login step in our CI run. https://github.community/t/docker-pull-from-public-github-package-registry-fail-with-no-basic-auth-credentials-error/16358 --Brennan
Re: official nuttx-ci-linux image
On Thu, Aug 6, 2020 at 11:57 PM Brennan Ashton wrote: > > On Thu, Aug 6, 2020, 4:03 AM Takashi Yamamoto > wrote: > > > hi, > > > > the docker image used by the CI (nuttx-ci-linux) is useful for other > > purposes. > > but as far as i know, it isn't pullable publicly. > > > > right now, i'm building and pushing it to docker hub for my own > > consumption. > > https://hub.docker.com/repository/docker/yamt/nuttx-ci-linux > > i think it's worth to provide an equivalent officially as a project. > > > > how do you think? > > > > The image is already publicly available. This is how the CI system uses it > including Jenkins > > https://github.com/apache/incubator-nuttx-testing/packages/159581 spacetanuki% docker pull docker.pkg.github.com/apache/incubator-nuttx-testing/nuttx-ci-linux:latest Error response from daemon: Get https://docker.pkg.github.com/v2/apache/incubator-nuttx-testing/nuttx-ci-linux/manifests/latest: no basic auth credentials spacetanuki% what credential should i use for public consumption? > > --Brennan > > >
Re: official nuttx-ci-linux image
HI, > This is a build environment we use for CI, it does not contain any NuttX > release code. Thanks for that perhaps make that clearer by adding a description? Thanks, Justin
Re: official nuttx-ci-linux image
This is a build environment we use for CI, it does not contain any NuttX release code. On Thu, Aug 6, 2020, 3:44 PM Justin Mclean wrote: > Hi, > > This is a little bit of a concern.[1] "Projects MUST direct outsiders > towards official releases rather than raw source repositories, nightly > builds, snapshots, release candidates, or any other similar packages” > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html#publication
Re: official nuttx-ci-linux image
Hi, This is a little bit of a concern.[1] "Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages” Thanks, Justin 1. http://www.apache.org/legal/release-policy.html#publication
Re: USB host mass storage class automount.
Would it be acceptable that the automount handler is called from usbhost_storage.c, from a modularity point of view? Because that way it would be only a notification towards the work queue, using a mechanism that is already in place. I don't like the idea to have another kthread that does only wait for a notification/event and then schedules itself the automount work on the queue. Absolutely not. Please do not consider this. It would be permissible to broadcast a notification but must not under any imaginable circumstances violate the modular architecture by calling across module boundaries. That is the single highest and single most importaent architectural principle of the OS. See https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139629399 . We must not allow the OS to be degraded in that way. That is the direct route to spaghetti code. See also the top-level INVIOLABLES.txt: Modular Architecture o The internal modular architecture of the OS must be maintained. o This means formalizing and documenting all internal interfaces (in the porting guide), minimal use of global variables at the interface, and only well defined functional interfaces. That kind of hack you suggest is most strictly forbidden and shows a profound lack of understanding of the OS architecture.
Re: USB host mass storage class automount.
Would it be acceptable that the automount handler is called from usbhost_storage.c, from a modularity point of view? Because that way it would be only a notification towards the work queue, using a mechanism that is already in place. I don't like the idea to have another kthread that does only wait for a notification/event and then schedules itself the automount work on the queue. Absolutely not. Please do not consider this. It would be permissible to broadcast a notification but must not under any imaginable circumstances violate the modular architecture by calling across module boundaries. That is the single highest and single most importaent architectural principle of the OS. See https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139629399 . We must not allow the OS to be degraded in that way. That is the direct route to spaghetti code.
Re: USB host mass storage class automount.
Would it be acceptable that the automount handler is called from usbhost_storage.c, from a modularity point of view? Because that way it would be only a notification towards the work queue, using a mechanism that is already in place. I don't like the idea to have another kthread that does only wait for a notification/event and then schedules itself the automount work on the queue. Johannes > -Original Message- > From: Gregory Nutt [mailto:spudan...@gmail.com] > > > But: I haven't yet found a way to determine if I enumerated really a mass > storage class device. So with only activating mass storage it seems rather > clean, but if I have multiple class drivers active, it gets complicated. > > Can you give a hint how to retrieve the type of driver bound to the > currently enumerated device? > That precise information is not available unless you add a notifier. > Bu you should be able to just use nx_stat() to see of the block driver > was created at /dev/sd* >
Re: ADC Examples error?
Very nice Nii! On 8/6/20, Nii Jyeni wrote: > This board is made by myself, the MCU model is STM32F429IIT6, and the > configuration file refers to the STM32F429i-disco board. > At present, LAN, FLASH, SDRAM, and GPIO have all passed the test, and other > functions are still being tested. >> 2020年8月6日 下午7:32，Alan Carvalho de Assis 写道： >> >> Hi Nii, >> >> What board are you using? It appears like an incorrect ADC board >> configuration. >> >> The analog value for channels 4 and 5 are changing a little bit from >> each sampling, but they appear to make sense. >> >> Try to isolate the issue, you can start with a single channel, start >> without DMA, etc. >> >> Also enabling the DEBUG ADC could give you some hints. >> >> BR, >> >> Alan >> >> On 8/6/20, Nii Jyeni wrote: >>> I found a strange problem when using the latest source code to test the >>> ADC >>> example. The analog value can be obtained when the ADC example is run >>> for >>> the first time. When the ADC example is run again, it is blocked and it >>> looks like it is dead. But send Ctrl+C to the console can terminate it. >>> >>> OS:MacOS >>> Nuttx:nightly >>> MCU:stm32f429iit6 >>> Board:customize >>> >>> NuttShell (NSH) NuttX-9.1.0 >>> nsh> adc -n 2 >>> adc_main: g_adcstate.count: 2 >>> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 >>> Sample: >>> 1: channel: 4 value: 3091 >>> 2: channel: 5 value: 3782 >>> Sample: >>> 1: channel: 4 value: 3192 >>> 2: channel: 5 value: 3612 >>> nsh> adc -n 2 >>> adc_main: g_adcstate.count: 2 >>> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— >>> terminated by send ctrl + c >>> nsh> adc -n 2 >>> adc_main: g_adcstate.count: 2 >>> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— >>> terminated by send ctrl + c >>> nsh> >>> >>> This is the configuration information about ADC that I am using: >>> CONFIG_STM32_ADC1=y >>> CONFIG_STM32_ADC1_DMA=y >>> CONFIG_STM32_TIM1=y >>> CONFIG_STM32_TIM1_ADC=y >>> CONFIG_EXAMPLES_ADC=y >>> CONFIG_EXAMPLES_ADC_GROUPSIZE=3 >>> CONFIG_ADC=y >>> >>> Does anyone know what is going on? and how to solve this problem. > >
Re: ADC Examples error?
This board is made by myself, the MCU model is STM32F429IIT6, and the configuration file refers to the STM32F429i-disco board. At present, LAN, FLASH, SDRAM, and GPIO have all passed the test, and other functions are still being tested. > 2020年8月6日 下午7:32，Alan Carvalho de Assis 写道： > > Hi Nii, > > What board are you using? It appears like an incorrect ADC board > configuration. > > The analog value for channels 4 and 5 are changing a little bit from > each sampling, but they appear to make sense. > > Try to isolate the issue, you can start with a single channel, start > without DMA, etc. > > Also enabling the DEBUG ADC could give you some hints. > > BR, > > Alan > > On 8/6/20, Nii Jyeni wrote: >> I found a strange problem when using the latest source code to test the ADC >> example. The analog value can be obtained when the ADC example is run for >> the first time. When the ADC example is run again, it is blocked and it >> looks like it is dead. But send Ctrl+C to the console can terminate it. >> >> OS:MacOS >> Nuttx:nightly >> MCU:stm32f429iit6 >> Board:customize >> >> NuttShell (NSH) NuttX-9.1.0 >> nsh> adc -n 2 >> adc_main: g_adcstate.count: 2 >> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 >> Sample: >> 1: channel: 4 value: 3091 >> 2: channel: 5 value: 3782 >> Sample: >> 1: channel: 4 value: 3192 >> 2: channel: 5 value: 3612 >> nsh> adc -n 2 >> adc_main: g_adcstate.count: 2 >> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— >> terminated by send ctrl + c >> nsh> adc -n 2 >> adc_main: g_adcstate.count: 2 >> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— >> terminated by send ctrl + c >> nsh> >> >> This is the configuration information about ADC that I am using: >> CONFIG_STM32_ADC1=y >> CONFIG_STM32_ADC1_DMA=y >> CONFIG_STM32_TIM1=y >> CONFIG_STM32_TIM1_ADC=y >> CONFIG_EXAMPLES_ADC=y >> CONFIG_EXAMPLES_ADC_GROUPSIZE=3 >> CONFIG_ADC=y >> >> Does anyone know what is going on? and how to solve this problem.
Re: ADC Examples error?
Thank you very much, this patch is effective for me. Now it is possible to run the ADC example multiple times to read the analog value > 2020年8月6日 下午8:28，raiden00pl 写道： > > Hi, > there seems to be a bug in the ADC setup logic and adc_reset() is only > called when the ADC driver is first opened. > You can fix it with the patch below, but I need to verify if it doesn't > break the ADC for STM32F3. If it works, I prepare a PR > > diff --git a/arch/arm/src/stm32/stm32_adc.c b/arch/arm/src/stm32/stm32_adc.c >> index b9f615fc7d..4dffd6637b 100644 >> --- a/arch/arm/src/stm32/stm32_adc.c >> +++ b/arch/arm/src/stm32/stm32_adc.c >> @@ -2886,8 +2886,6 @@ static int adc_setup(FAR struct adc_dev_s *dev) >> return OK; >> } >> >> - priv->initialized += 1; >> - >> /* Attach the ADC interrupt */ >> >> #ifndef CONFIG_STM32_ADC_NOIRQ >> @@ -2960,6 +2958,10 @@ static int adc_setup(FAR struct adc_dev_s *dev) >> adccmn_lock(priv, false); >> #endif >> >> + /* The ADC device is ready */ >> + >> + priv->initialized += 1; >> + >> return ret; >> } >> > > czw., 6 sie 2020 o 13:32 Alan Carvalho de Assis > napisał(a): > >> Hi Nii, >> >> What board are you using? It appears like an incorrect ADC board >> configuration. >> >> The analog value for channels 4 and 5 are changing a little bit from >> each sampling, but they appear to make sense. >> >> Try to isolate the issue, you can start with a single channel, start >> without DMA, etc. >> >> Also enabling the DEBUG ADC could give you some hints. >> >> BR, >> >> Alan >> >> On 8/6/20, Nii Jyeni wrote: >>> I found a strange problem when using the latest source code to test the >> ADC >>> example. The analog value can be obtained when the ADC example is run for >>> the first time. When the ADC example is run again, it is blocked and it >>> looks like it is dead. But send Ctrl+C to the console can terminate it. >>> >>> OS:MacOS >>> Nuttx:nightly >>> MCU:stm32f429iit6 >>> Board:customize >>> >>> NuttShell (NSH) NuttX-9.1.0 >>> nsh> adc -n 2 >>> adc_main: g_adcstate.count: 2 >>> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 >>> Sample: >>> 1: channel: 4 value: 3091 >>> 2: channel: 5 value: 3782 >>> Sample: >>> 1: channel: 4 value: 3192 >>> 2: channel: 5 value: 3612 >>> nsh> adc -n 2 >>> adc_main: g_adcstate.count: 2 >>> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— >>> terminated by send ctrl + c >>> nsh> adc -n 2 >>> adc_main: g_adcstate.count: 2 >>> adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— >>> terminated by send ctrl + c >>> nsh> >>> >>> This is the configuration information about ADC that I am using: >>> CONFIG_STM32_ADC1=y >>> CONFIG_STM32_ADC1_DMA=y >>> CONFIG_STM32_TIM1=y >>> CONFIG_STM32_TIM1_ADC=y >>> CONFIG_EXAMPLES_ADC=y >>> CONFIG_EXAMPLES_ADC_GROUPSIZE=3 >>> CONFIG_ADC=y >>> >>> Does anyone know what is going on? and how to solve this problem. >>
Re: official nuttx-ci-linux image
On Thu, Aug 6, 2020, 4:03 AM Takashi Yamamoto wrote: > hi, > > the docker image used by the CI (nuttx-ci-linux) is useful for other > purposes. > but as far as i know, it isn't pullable publicly. > > right now, i'm building and pushing it to docker hub for my own > consumption. > https://hub.docker.com/repository/docker/yamt/nuttx-ci-linux > i think it's worth to provide an equivalent officially as a project. > > how do you think? > The image is already publicly available. This is how the CI system uses it including Jenkins https://github.com/apache/incubator-nuttx-testing/packages/159581 --Brennan >
Re: USB host mass storage class automount.
But: I haven't yet found a way to determine if I enumerated really a mass storage class device. So with only activating mass storage it seems rather clean, but if I have multiple class drivers active, it gets complicated. Can you give a hint how to retrieve the type of driver bound to the currently enumerated device? That precise information is not available unless you add a notifier. Bu you should be able to just use nx_stat() to see of the block driver was created at /dev/sd*
Re: USB host mass storage class automount.
Hi Johannes, You cannot do it because it will not work for KERNEL and PROTECTED mode. We need to create a hotplug/udev for NuttX (just joking)... Well, you can use some signal to notify mount/umount that the USB Thumb driver was inserted/removed. BR, Alan On 8/6/20, Schock, Johannes - NIVUS GmbH wrote: > Hello, > just a short question: I'd like to have my USB stick attached to USB high > speed host automounted as vfat. > Would it be acceptable to call mount/umount directly in the > usbhost_storage.c where the blockdriver is registered/unregistered? > For sure switchable with Kconfig options. > I tried to setup a fs_automount instance, but I lack an > IRQ/callback/connectionstate from host or msc I could use. > > Thanks, Johannes > >
USB host mass storage class automount.
Hello, just a short question: I'd like to have my USB stick attached to USB high speed host automounted as vfat. Would it be acceptable to call mount/umount directly in the usbhost_storage.c where the blockdriver is registered/unregistered? For sure switchable with Kconfig options. I tried to setup a fs_automount instance, but I lack an IRQ/callback/connectionstate from host or msc I could use. Thanks, Johannes
Re: ADC Examples error?
Hi Nii, What board are you using? It appears like an incorrect ADC board configuration. The analog value for channels 4 and 5 are changing a little bit from each sampling, but they appear to make sense. Try to isolate the issue, you can start with a single channel, start without DMA, etc. Also enabling the DEBUG ADC could give you some hints. BR, Alan On 8/6/20, Nii Jyeni wrote: > I found a strange problem when using the latest source code to test the ADC > example. The analog value can be obtained when the ADC example is run for > the first time. When the ADC example is run again, it is blocked and it > looks like it is dead. But send Ctrl+C to the console can terminate it. > > OS:MacOS > Nuttx:nightly > MCU:stm32f429iit6 > Board:customize > > NuttShell (NSH) NuttX-9.1.0 > nsh> adc -n 2 > adc_main: g_adcstate.count: 2 > adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 > Sample: > 1: channel: 4 value: 3091 > 2: channel: 5 value: 3782 > Sample: > 1: channel: 4 value: 3192 > 2: channel: 5 value: 3612 > nsh> adc -n 2 > adc_main: g_adcstate.count: 2 > adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— > terminated by send ctrl + c > nsh> adc -n 2 > adc_main: g_adcstate.count: 2 > adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— > terminated by send ctrl + c > nsh> > > This is the configuration information about ADC that I am using: > CONFIG_STM32_ADC1=y > CONFIG_STM32_ADC1_DMA=y > CONFIG_STM32_TIM1=y > CONFIG_STM32_TIM1_ADC=y > CONFIG_EXAMPLES_ADC=y > CONFIG_EXAMPLES_ADC_GROUPSIZE=3 > CONFIG_ADC=y > > Does anyone know what is going on? and how to solve this problem.
RE: official nuttx-ci-linux image
Love it! -Original Message- From: Takashi Yamamoto [mailto:yamam...@midokura.com.INVALID] Sent: Thursday, August 06, 2020 4:03 AM To: dev@nuttx.apache.org Subject: official nuttx-ci-linux image hi, the docker image used by the CI (nuttx-ci-linux) is useful for other purposes. but as far as i know, it isn't pullable publicly. right now, i'm building and pushing it to docker hub for my own consumption. https://hub.docker.com/repository/docker/yamt/nuttx-ci-linux i think it's worth to provide an equivalent officially as a project. how do you think?
official nuttx-ci-linux image
hi, the docker image used by the CI (nuttx-ci-linux) is useful for other purposes. but as far as i know, it isn't pullable publicly. right now, i'm building and pushing it to docker hub for my own consumption. https://hub.docker.com/repository/docker/yamt/nuttx-ci-linux i think it's worth to provide an equivalent officially as a project. how do you think?
ADC Examples error?
I found a strange problem when using the latest source code to test the ADC example. The analog value can be obtained when the ADC example is run for the first time. When the ADC example is run again, it is blocked and it looks like it is dead. But send Ctrl+C to the console can terminate it. OS:MacOS Nuttx:nightly MCU:stm32f429iit6 Board:customize NuttShell (NSH) NuttX-9.1.0 nsh> adc -n 2 adc_main: g_adcstate.count: 2 adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 Sample: 1: channel: 4 value: 3091 2: channel: 5 value: 3782 Sample: 1: channel: 4 value: 3192 2: channel: 5 value: 3612 nsh> adc -n 2 adc_main: g_adcstate.count: 2 adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— terminated by send ctrl + c nsh> adc -n 2 adc_main: g_adcstate.count: 2 adc_main: Hardware initialized. Opening the ADC device: /dev/adc0 <— terminated by send ctrl + c nsh> This is the configuration information about ADC that I am using: CONFIG_STM32_ADC1=y CONFIG_STM32_ADC1_DMA=y CONFIG_STM32_TIM1=y CONFIG_STM32_TIM1_ADC=y CONFIG_EXAMPLES_ADC=y CONFIG_EXAMPLES_ADC_GROUPSIZE=3 CONFIG_ADC=y Does anyone know what is going on? and how to solve this problem.
Re: Nuttx was found to be a strange error compiling on Macos
Thanks Alan, I re-downloaded the source code and the problem was solved.It's a bit strange. > 2020年8月3日 下午10:04，Nii Jyeni 写道： > > OS:MacOS > Nuttx:nightly > Arm-none-eabi-gcc:7.3.1 > > … > arning: /Library/Developer/CommandLineTools/usr/bin/ranlib: warning for > library: libbinfmt.a the table of contents is empty (no object file members > in the library define global symbols) > IN: binfmt/libbinfmt.a -> staging/libbinfmt.a > CC: board/stm32_boot.c > CC: board/stm32_bringup.c > CC: board/stm32_spi.c > CC: board/stm32_userleds.c > CC: board/stm32_appinit.c > CC: board/stm32_extmem.c > CC: board/stm32_lcd.c > CC: board/stm32_adc.c > ar rcs libboard.a stm32_boot.o stm32_bringup.o stm32_spi.o > stm32_userleds.o stm32_appinit.o stm32_extmem.o stm32_lcd.o stm32_adc.o > warning: /Library/Developer/CommandLineTools/usr/bin/ranlib: warning for > library: libboard.a the table of contents is empty (no object file members in > the library define global symbols) > LD: nuttx > arm-none-eabi-ld: warning: cannot find entry symbol __start; defaulting to > 0800 > > Does anybody know what's going on? > > > Enjoy your life! > - > Nii Jyeni > > 13880639629 > niijy...@hotmail.com > www.niijyeni.org > [https://a.gfx.ms/emoji_1F680.png]Sent from Outlook.com
