Date   

Re: Draws image

Cowan Bowman
 

Rufus works very well on windows 10 to create bootable image on the SD card.


Cowan
N5QDH

On Sat, Sep 28, 2019 at 7:02 AM rhclinton <rhclinton@...> wrote:
The problem is an incompatibility between Etcher and Windows 10.  Reference to the Etcher forum revealed that a number of others had suffered the same problem (not in relation to Draws).  I rescusitated a Windows 8.1 machine and installed Etcher and was able to flash the SD with the Draws image.  It booted correctly in a RPi 3.  I tried three diffeent Win10 machines and had the same problem.  All three were running Bitdefender but turning off the Bitdefender firewall and other services that are often implicated in blocked applications had no effect in this case.  One of the posts on the Etcher forum indicated a suspicion of Windows Defender, so perhaps it is related to virus/firewall software.

One of the posts by an Etcher support guy said something to the effect that they were "looking into a mitigation", but that was quite some time ago.  The message is, then, that if you want to flash images to an SD on a Windows machine, then hang on to a pre-Win10 machine.

Bob  G0BUX


Re: DRAWS and Buster distro

Basil Gunn
 

As suggested I moved driver lines to [all] section.
However this did not help.
Later on today look for a new RPi image that should fix your problem.
However adding those 3 lines to the bottom of the latest Raspbian images
should work. I don't have enough visibility into your system to
understand why it doesn't.

I performed a RaspBerry Pi firmware + kernel update using rpi-update
upgrading to kernel is 4.19.75-v7+
Since the kernel you get from doing this is bleeding edge I have not
tested it and do NOT support it. For others reading this post please do
NOT run rpi-update as that will install an unsupported kernel.

Interestingly there are now two errors messages displayed when running show-udrc.sh

chk1: snd-soc-tlv320aic32x4-i2c.ko exists, Driver CONFLICT
chk2: snd-soc-tlv320aic32x4.ko exists, Driver CONFLICT
You are seeing these messages because that script you are running hasn't
been updated for compatibility with Linux buster. If you update the
scripts from my repository you will get a version that handles buster
properly.

cd
cd n7nix
git pull

/Basil


Re: Draws image

Mitch Winkle
 

I have done multiple Etcher images lately on a Win10 machine that is at level 1809 IIRC.  Maybe it's something in 1903.  I do not allow Defender or any Firewalls to be running as it is largely an air-gapped PC.

On 9/28/2019 09:02, rhclinton wrote:
The problem is an incompatibility between Etcher and Windows 10.  ...

One of the posts by an Etcher support guy said something to the effect that they were "looking into a mitigation", but that was quite some time ago.  The message is, then, that if you want to flash images to an SD on a Windows machine, then hang on to a pre-Win10 machine.

Bob  G0BUX
_._,_._


Re: Draws image

August Johnson KG7BZ
 

I use Win32DiskImager on Windows 10, works just fine.

August KG7BZ


Re: Draws image

rhclinton <rhclinton@...>
 

The problem is an incompatibility between Etcher and Windows 10.  Reference to the Etcher forum revealed that a number of others had suffered the same problem (not in relation to Draws).  I rescusitated a Windows 8.1 machine and installed Etcher and was able to flash the SD with the Draws image.  It booted correctly in a RPi 3.  I tried three diffeent Win10 machines and had the same problem.  All three were running Bitdefender but turning off the Bitdefender firewall and other services that are often implicated in blocked applications had no effect in this case.  One of the posts on the Etcher forum indicated a suspicion of Windows Defender, so perhaps it is related to virus/firewall software.

One of the posts by an Etcher support guy said something to the effect that they were "looking into a mitigation", but that was quite some time ago.  The message is, then, that if you want to flash images to an SD on a Windows machine, then hang on to a pre-Win10 machine.

Bob  G0BUX


Re: DRAWS and Buster distro

Bernard Pidoux
 

Adding lsmod dump could help ?


Re: DRAWS and Buster distro

Bernard Pidoux
 

As suggested I moved driver lines to [all] section.
However this did not help.

I performed a RaspBerry Pi firmware + kernel update using rpi-update
upgrading to kernel is 4.19.75-v7+ 

Interestingly there are now two errors messages displayed when running show-udrc.sh 

chk1: snd-soc-tlv320aic32x4-i2c.ko exists, Driver CONFLICT
chk2: snd-soc-tlv320aic32x4.ko exists, Driver CONFLICT
==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
 Pi 3 Model B Mfg by Sony UK
 Has WiFi
==== udrc Ver ====
Found a UDRC II
 
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        ea0d20c1-38fd-4dc4-a633-5ea145700e79
Vendor:      NW Digital Radio
....

Bernard


Re: DRAWS and Buster distro

Basil Gunn
 

The problem is Anna's driver patches for the tlv320aic sound codec
didn't ALL make it into the Linux mainline kernel when Raspbian first
released Buster. There have been 3 or more kernel updates in Raspbian
since June. The current kernel used by Raspbian, 4.19.66-v7+ has all of
Anna's patches & works fine.

Since the kernel you are currently using may have changed since you
modified your /boot/config.txt file try commenting out the dtoverlay=
line and running 'aplay -l'

Did the design of Draws boards change with respect to the eprom?
The overlay file required by the NW Digital Radio hats (UDRC, UDRC II &
DRAWS) grew too large to fit into the eeprom and is now loaded from the
boot file system. Also the Linux overlay code changed the names of some
of the overlay variables making any of the previous hat overlays that
are loaded from eeprom not work. Those hats require that the dtoverlay=
be used.

I would like to find out which NW Digital Radio hat you have:
udrcver.sh
and what version of the kernel you are running:
uname -r
and if you comment out the dtoverlay= line whether you still see the
problem of the hat not being enumerated.
aplay -l

/Basil

Jonathan Magee <jmagee@...> writes:

That is not what I have found in practice. I created a clean sd card from
the official image for buster and to get the Draws Hat to be recognised I
had to add in the dtoverlay= line
When I did investigate it was trying to load in a device tree from the HAT
and failed. Did the design of Draws boards change with respect to the
eprom?

Regards
Jonathan

On Fri, 27 Sep 2019 at 16:19, Basil Gunn <@basil860> wrote:


Basil's advice IS totally correct. If you have a DRAWS hat, NOT a UDRC
or UDRC II then you do NOT need to include the overlay flush line
dtoverlay=. It doesn't hurt anything to include the line but since the
overlay does NOT exist in eeprom for the DRAWS hat as it does for the
UDR & some of the UDRC II hats it really doesn't actually do anything.

If you have a DRAWS hat and find that you need to use dtoverlay= to get
the DRAWS driver to load and recognize the hat then you have other
problems, like the kernel you are using doesn't have all of Anna'a
patches or your upgrade path has left a bunch of stale overlays in
/boot/overlays directory.

On a new install using Raspbian with kernel version 4.19.66 or newer you
will not have that problem.
/Basil

Jonathan Magee <jmagee@...> writes:

Hi Bernard
Basil's advice isn't totally correct, for some Draw Hats you need to
include in /boot/config.txt the line:
dtoverlay=
as well as the other lines. So the extra lines are (as per UDRC & UDRC II
hats )

dtoverlay=
dtoverlay=draws,alsaname=udrc
force_turbo=1

That is what I had to do with my Draws Hat
Regards
Jonathan GI7KMC

On Thu, 26 Sep 2019 at 12:09, Bernard Pidoux <bernard.f6bvp@...>
wrote:

Hi Basil,
Unfortunately /boot/config.txt modifications does not work.
aplay -l does not display card1: udrc
Here is the screen dump :


I suspect a conflict with forced sound through HDMI1 display.

Regards,

Bernard



Re: Draws image

rhclinton <rhclinton@...>
 

On 2019-09-27 17:41, John D Hays - K7VE wrote:
This appears to be a problem on your Windows box.
Possibly - will try it on another machine

As the error > message indicates, the Etcher team is the place to get support on
Etcher.
Yes, but I feel that it is not a problem with Etcher. I have just downloaded the
latest version. In any case, I get a similar problem when I try to write the
image with Win32diskimager.


BTW, modern versions of Etcher allow you to simply point it at the
zip file and Etcher will take care of the unzipping as it writes the
image to the SD card.
Tried that - no effect.
Also, make sure you have a clean zip file.
Do you mean a clean SD card? I tried both a 16 and a 32 card; both were
clean.


Links:
------
[1] https://nw-digital-radio.groups.io/g/udrc/message/4017
[2] https://groups.io/mt/30840179/229317
[3] https://nw-digital-radio.groups.io/g/udrc/post
[4] https://nw-digital-radio.groups.io/g/udrc/editsub/229317
[5] https://nw-digital-radio.groups.io/g/udrc/leave/defanged


Re: Draws image

rhclinton <rhclinton@...>
 

On 2019-09-27 17:46, Basil Gunn wrote:
What size of SD Card are you using?
Either 16 or 32 gb

Describe in more detail " All with the same result"
With all combinations using Etcher, I got the same error message
I sent to the forum. When I used Win32 diskimager I got a similar
indication that the operation had failed.

Did you follow the instructions from this link?
https://www.raspberrypi.org/documentation/installation/installing-images/windows.md
Yes

What file name are you using for the "image file"?
draws_beta13.img

Did you search for "Etcher" on this forum for possible solutions to your
problem?
No
/Basil
rhclinton <rhclinton@...> writes:

I am trying to write the image to an SD card on a Win10 machine. I have downloaded the current zip file, unpacked it and tried writing it with Etcher; Result:
I have tried different SD cards and two different SD drives. I have also tried using win32diskimager. All with the same result.
Bob G0BUX


Re: DRAWS and Buster distro

Jonathan Magee
 

That is not what I have found in practice. I created a clean sd card from the official image for buster and to get the Draws Hat to be recognised I had to add in the  dtoverlay= line
When I did investigate it was trying to load in a device tree from the HAT and failed. Did the design of Draws boards change with respect to the eprom?  

Regards
Jonathan


On Fri, 27 Sep 2019 at 16:19, Basil Gunn <basil@...> wrote:

Basil's advice IS totally correct. If you have a DRAWS hat, NOT a UDRC
or UDRC II then you do NOT need to include the overlay flush line
dtoverlay=. It doesn't hurt anything to include the line but since the
overlay does NOT exist in eeprom for the DRAWS hat as it does for the
UDR & some of the UDRC II hats it really doesn't actually do anything.

If you have a DRAWS hat and find that you need to use dtoverlay= to get
the DRAWS driver to load and recognize the hat then you have other
problems, like the kernel you are using doesn't have all of Anna'a
patches or your upgrade path has left a bunch of stale overlays in
/boot/overlays directory.

On a new install using Raspbian with kernel version 4.19.66 or newer you
will not have that problem.
/Basil

Jonathan Magee <jmagee@...> writes:

> Hi Bernard
> Basil's advice isn't totally correct, for some Draw Hats you need to
> include in /boot/config.txt the line:
> dtoverlay=
> as well as the other lines. So the extra lines are (as per UDRC & UDRC II
> hats )
>
> dtoverlay=
> dtoverlay=draws,alsaname=udrc
> force_turbo=1
>
> That is what I had to do with my Draws Hat
> Regards
> Jonathan GI7KMC
>
> On Thu, 26 Sep 2019 at 12:09, Bernard Pidoux <bernard.f6bvp@...>
> wrote:
>
>> Hi Basil,
>> Unfortunately /boot/config.txt modifications does not work.
>> aplay -l does not display card1: udrc
>> Here is the screen dump :
>>
>>
>> I suspect a conflict with forced sound through HDMI1 display.
>>
>> Regards,
>>
>> Bernard




Re: Draws image

Basil Gunn
 

What size of SD Card are you using?
Describe in more detail " All with the same result"
Did you follow the instructions from this link?
https://www.raspberrypi.org/documentation/installation/installing-images/windows.md
What file name are you using for the "image file"?
Did you search for "Etcher" on this forum for possible solutions to your
problem?

/Basil

rhclinton <rhclinton@...> writes:

I am trying to write the image to an SD card on a Win10 machine. I have downloaded the current zip file, unpacked it and tried writing it with Etcher; Result:

I have tried different SD cards and two different SD drives. I have also tried using win32diskimager. All with the same result.
Bob G0BUX


Re: Draws image

 

This appears to be a problem on your Windows box.  As the error message indicates, the Etcher team is the place to get support on Etcher.

BTW, modern versions of Etcher allow you to simply point it at the zip file and Etcher will take care of the unzipping as it writes the image to the SD card.

Also, make sure you have a clean zip file.


Re: Draws image

rhclinton <rhclinton@...>
 

I am trying to write the image to an SD card on a Win10 machine.  I have downloaded the current zip file, unpacked it and tried writing it with Etcher;  Result:



I have tried different SD cards and two different SD drives.  I have also tried using win32diskimager.  All with the same result.
Bob  G0BUX


Re: DRAWS and Buster distro

Basil Gunn
 

Basil's advice IS totally correct. If you have a DRAWS hat, NOT a UDRC
or UDRC II then you do NOT need to include the overlay flush line
dtoverlay=. It doesn't hurt anything to include the line but since the
overlay does NOT exist in eeprom for the DRAWS hat as it does for the
UDR & some of the UDRC II hats it really doesn't actually do anything.

If you have a DRAWS hat and find that you need to use dtoverlay= to get
the DRAWS driver to load and recognize the hat then you have other
problems, like the kernel you are using doesn't have all of Anna'a
patches or your upgrade path has left a bunch of stale overlays in
/boot/overlays directory.

On a new install using Raspbian with kernel version 4.19.66 or newer you
will not have that problem.
/Basil

Jonathan Magee <jmagee@...> writes:

Hi Bernard
Basil's advice isn't totally correct, for some Draw Hats you need to
include in /boot/config.txt the line:
dtoverlay=
as well as the other lines. So the extra lines are (as per UDRC & UDRC II
hats )

dtoverlay=
dtoverlay=draws,alsaname=udrc
force_turbo=1

That is what I had to do with my Draws Hat
Regards
Jonathan GI7KMC

On Thu, 26 Sep 2019 at 12:09, Bernard Pidoux <bernard.f6bvp@...>
wrote:

Hi Basil,
Unfortunately /boot/config.txt modifications does not work.
aplay -l does not display card1: udrc
Here is the screen dump :


I suspect a conflict with forced sound through HDMI1 display.

Regards,

Bernard


Re: DRAWS and Buster distro

Basil Gunn
 

You are not using an RPi 4 yet your configuration is in the [Pi4]
section in config.txt. Take the udrc configuration:

dtoverlay=
dtoverlay=draws,alsaname=udrc
force_turbo=1

and move it to the end of the config.txt file under the [all] section.
Since you have a UDRC II it is a requirement that you use dtoverlay= to
flush the broken overlay before loading a good overlay.

Thanks for providing your config.txt file and the output of showudrc.sh.
/Basil


Bernard Pidoux <bernard.f6bvp@...> writes:

Please fin attached config.txt and show-udrc output message.



# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=35

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable UDRC driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
dtoverlay=
dtoverlay=draws,alsaname=udrc

force_turbo=1

max_framebuffers=2

[all]
#dtoverlay=udrc

==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
Pi 3 Model B Mfg by Sony UK
Has WiFi
==== udrc Ver ====
Found a UDRC II

HAT ID EEPROM
Name: hat
Product: Universal Digital Radio Controller II
Product ID: 0x0003
Product ver: 0x0001
UUID: ea0d20c1-38fd-4dc4-a633-5ea145700e79
Vendor: NW Digital Radio


Re: DRAWS and Buster distro

Bernard Pidoux
 

Please fin attached config.txt and show-udrc output message.


Re: DRAWS and Buster distro

Bernard Pidoux
 

Hi John,
No change after removal of space character and reboot with udrcII hat.
I did not try yet on other device with DRAWS.
What can I do or send you for help ?

Bernard


Re: DRAWS and Buster distro

 

Try removing the space before alsaname

# Enable UDRC driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
dtoverlay=
dtoverlay=draws, alsaname=udrc

dtoverlay=draws,alsaname=udrc

On Thu, Sep 26, 2019 at 10:18 AM Bernard Pidoux <bernard.f6bvp@...> wrote:
Here is what n7nix show-udrc.sh script diaplays.
It may help.

Bernard



--
John D. Hays
Kingston, WA
K7VE

 


Re: DRAWS and Buster distro

Bernard Pidoux
 

Here is what n7nix show-udrc.sh script diaplays.
It may help.

Bernard